Maybe the main feature they are not telling anyone is that it slurps your valuable code bases faster in order to feed their AI? I guess usurping github ain't enough.
Except there were websites requiring you to install ActiveX and proprietary plugins to do anything meaningful as soon as 1995? Also banks requiring proprietary security modules to access your account, they were pretty ubiquitous in the early 2000s where I lived.
The difference now is that accessing services through the internet is a necessity rather than a luxury. I guess passing laws could fix this, but it's exceptionally hard to get anything done through the barrage of big tech lobbying.
A few years ago everyone said _Open_AI is the the most open labs. How did that turn out? Lots of coy, deceiving actions till the whole company was turned into whatever rent seeking amoral borg adjacent shell of it's former past it is now.
I'm sure this has already been answered somewhere in slashdot hundreds of years ago, but why not just go with "free as in freedom"? And perhaps use the word freedom insted of free when possible
But in all seriousness, "free as in freedom" seems fine to me but it is replacing the already unambiguous "free as in speech". You're still stuck with the sometimes-confusing "free as in beer" and they're still cumbersome compared to gratis/libre.
Use the unhook extension, ublock origin extension and firefox. Also don't hesitate to use the "Block element" feature for ublock. Get some control back from big tech :)
If you use the command line to do the update there is no need to reboot, however, the issues that the offline update is trying to solve still stands.
Some programs can crash when all their files are suddenly swapped for new ones. I've seen multiple linux systems bork themselves during an update because the update itself caused the desktop session to crash, which caused the update process to be interrupted just as it was modifying some crucial files, thus rendering the system unbootable.
>> If you use the command line to do the update there is no need to reboot
Completely untrue.
And before systemd, updating sshd or cron usually meant restarting that one daemon. With systemd, core updates can affect PID 1, logind, journald, udev, user managers, socket activation and cgroup state as one dependency graph.
Before, its was replace a library and restart the few daemons using it. Now the same library may be loaded by system services, user services and systemd components, making a clean partial restart harder to verify.
You are wrong. Just idea of having to use to remotes is unacceptable level of friction to most people. We should not hail separate device as excuse to allow this shitty behaviour by TV manufacturers.
I guess the lawmakers won't move a finger and we have wait for consumer network equipment manufacturers[1] to advertise build in pi-hole and ACR/TV ads blocking on firewall level.
[1] Let's just forget for a second they are famous for low quality software full of security bugs
reply