SoylentNews is people
SoylentNews
The Register spotted Ubuntu behaving badly again with respect to users' privacy. In their article "Ubuntu wants to slurp PCs' vital statistics – even location – with new desktop installs: Data harvest notice will be checked by default", they note that in addition to installing popcon and apport by default, Canonical seeks much deeper data mining (without using the word "telemetry"):
[...] "We want to be able to focus our engineering efforts on the things that matter most to our users, and in order to do that we need to get some more data about sort of setups our users have and which software they are running on it," explained Will Cooke, the director of Ubuntu Desktop at Canonical.
[...] Data Canonical seeks "would include" the following: Ubuntu Flavour, Ubuntu Version, Network connectivity or not, CPU family, RAM, Disk(s) size, Screen(s) resolution, GPU vendor and model, OEM Manufacturer, Location (based on the location selection made by the user at install). No IP information would be gathered, Installation duration (time taken), Auto login enabled or not, Disk layout selected, Third party software selected or not, Download updates during install or not, [and] LivePatch enabled or not.
The system plans to leverage the power of the default setting by making the choice opt-out, not opt-in as popcon has been in the past: Cooke explained to the ubuntu-devel audience that "Any user can simply opt out by unchecking the box, which triggers one simple POST stating, 'diagnostics=false'. There will be a corresponding checkbox in the Privacy panel of GNOME Settings to toggle the state of this."
El Reg also noted Ubuntu's plan to address user privacy concerns:
"The Ubuntu privacy policy would be updated to reflect this change."
This seems less egregious than Ubuntu's past invasions of privacy, but much more invasive and Windows 10-like.
(Score: 1, Interesting) by Anonymous Coward on Tuesday February 20 2018, @04:23PM
For desktops, I use PCLinuxOS, no systemd, and, on the whole, it just works™..
For servers, *BSDs I'm afraid (migrated from the last systemd-free Debian distro).
Firewall, I'm conflicted, I've a seriously 'fucked with' PCLinuxOS box doing the job at present (only the base packages, development and kernel are from the distro, the rest are compiled from source and local hackery) which is either going to be replaced with a Devuan box (the easy option) or another *BSD one.