3 ms·
As a native (British) English speaker, I was also unclear until reading the article. Personally, I believe s/change/modify would make more sense, but that's ju
by alias_neo 1y ago
As a native (British) English speaker, I was also unclear until reading the article.
Personally, I believe s/change/modify would make more sense, but that's just my opinion.
That aside, I'm a big fan of Debian, it has always "felt" quieter as a distro to me compared to others, which is something I care greatly about; and it's great to see that removing of calling home is a core principle.
All the more reason to have a more catchy/understandable title, because I believe the information in those short and sweet bullet points are quite impactful.
- pabs3 1y agoPatching out privacy issues isn't in Debian Policy, its just part of the culture of Debian, but there are still unfixed/unfound issues too, it is best to run opensnitch to mitigate some of those problems. https://wiki.debian.org/PrivacyIssues https://wiki.debian.org/PrivacyIssues
- alias_neo 1y agoThanks for the link, that'll come in very useful. > it is best to run opensnitch to mitigate some of those problems Opensnitch is a nice recommendation for someone concerned about protecting their workstation(s); for me, I'm more concerned about the tens of VMs and containers running hundreds of pieces of software that are always-on in my Homelab, a privacy conscious OS is a good foundation, and there are many more layers that I won't go into unsolicited.
- pabs3 1y agoHomelabs are usually running software not from a distro too, so potentially more privacy issues there too. Firewalling outgoing networking, along with a filtering SOCKS proxy like privoxy might be a good start.
- twic 1y agoI understood what it meant immediately, but i think only because i already knew that Debian are infamous for doing this.