The problem with that would be that it would make switching to another linux ditribution very, very easy. They would have 99.99% compatibility so a lot of people would switch to another distro if they add stuff like recall.
They would also be opening the can of worms that is massive software support for linux (which is arguably already opening.)
I doubt the os switch is happening too, some will probably switch but that will be a small amount, either they get Linux or afaik all other “popular” options require new hardware anyways (Macos)
I think many will just stay on windows 10 if their hardware doesn’t support 11 but ehh
Difficult to say, that’s why I’m waiting on the EOL for headlines like “millions of pcs vulnerable due to missing updates” or “maybe we were a little hard on crowdstrike”
They moved to Switzerland due to the reasons listed here.
Linton said that last year the Australian Federal Police (AFP) visited a Session employee at their home in the country. “There was no warrant used or meeting organised, they just went into their apartment complex and knocked on their front door,” Linton said. The AFP asked about the Session app and company
But why
I’m just waiting for the EOL of window 10 to see which of the following will happen:
If it actually were FOSS instead of source available(do not copy), yes.
checkmate atheists
Use -B instead.
Sets Advanced Power Management feature. Possible values are between 1 and 255, low values mean more aggressive power management and higher values mean better performance. Values from 1 to 127 permit spin-down, whereas values from 128 to 254 do not. A value of 255 completely disables the feature.)
Define “sandboxed”
Application can only access a limited part of the system? = use flatpak or build a container/VM image using the nix pkgs.
Application can be uninstalled completely and has separate libraries? I prefer nix.
Something I don’t get is, why try to make all browser look the same when you can do the easier thing and just make each browser session have a new fingerprint?
A unique fingerprint doesn’t matter much if it’s only valid till I close that website, right? So why not change a lot of variables by some small amount to make the data useless?
Or encrypt it before uploading
Would this even cause a kernel panic? I think this just causes a userland “panic”
That’s fine as long as it can self reference.
You need a phone, tablet, or other device that’s been rooted.
Damit
And to calculate the offset needed to get them all synced up involves calculating time dilation, which involves knowing/assuming the speed of light. These synchronizations work just as well if the two way speed of light is different than the one way speed of light.
To know the speed of light you assume the speed of light is c, but you’re trying to calculate c so all those clocks aren’t verified synced.
Just read through the wiki or Harvard’s books if you’d like, this is an unsolved “problem” in physics for a reason or do you think no one cares about how fast c is?
See also This or, more accessibly “Synchronization conventions”
It is impossible to synchronize the clocks in such a way that you can actually measure the speed of light with it due to time dilation unless you define beforehand how fast the speed of light is to calculate that time dilation.
See also This or, more accessibly “Synchronization conventions”
The very accurate clock needed in this case is physically impossible as far as we know, there’s no way to measure it as far as our current understanding of physics goes.
Though if you can figure out a way you should publish a paper about it.
And further down:
Unfortunately, if the one-way speed of light is anisotropic, the correct time dilation factor becomes
, with the anisotropy parameter κ between -1 and +1.[17] This introduces a new linear term,
(here
), meaning time dilation can no longer be ignored at small velocities, and slow clock-transport will fail to detect this anisotropy. Thus it is equivalent to Einstein synchronization.
see systemd.unit(5), systemd.service(5), systemd.socket(5), systemd.device(5), systemd.mount(5), systemd.automount(5), systemd.swap(5), systemd.target(5), systemd.path(5), systemd.timer(5), systemd.slice(5), systemd.scope(5) systemd.link(5), systemd.netdev(5), systemd.network(5) and honorable mentions podman-systemd.unit .container, .volume, .network(…again), .kube, .image, .build and .pod