Shamar @Shamar@qoto.org

@dpwiz

To each his own: you find that article myopic and I find your comment hallucinated.

The issue with that article is that it still ignore the corporations behind LLM, does not clarify how they are responsible for the "decisions" "borrowed" by the corpus and how they should be held accountable for each of LLM outputs.

@gregeganSF

BTW, [SystemD's support of systemic surveillance](https://github.com/systemd/systemd/issues/34184) is one more reason to move to @jaromil's #Devuan

https://www.devuan.org/

I wonder if #Debian customized the defaults in the systemd packages. Maybe @dyne might distribute an ungoogled-systemd?

Ironically, the same #SystemD refuse to get rid of #Google #surveillance [in the default build](https://github.com/systemd/systemd/issues/34184) have a security bug bounty program sponsored by the [Sovereign Tech Fund](https://www.sovereigntechfund.de/about).

What's more #sovereign than leaking personal data to #Google by default?

@krakenbuerger @tarakiyee @polexa @mechko

@ed because, as explained in the issue, people (and corporations) compile and use open source software from source routinely, and even more in these years of supply chain attacks.

A failing build can be fixed in an hour (at most, if the build process is properly documented), but a personal data-leak can not be fixed at all after it occurred.

People who can't find DNS server more suited for their needs can happily use Google's one, but it must be a conscious decision not something they are not aware of.

As for it being a systemd responsibility, I think it is (they wrote that code and picked the worst possible defaults).
And frankly, they happily renamed the default branch from `master` to `main` to please US people who do not like to remember their #slavery heritage, why they shouldn't do a cheap fix here that benefit all the rest of the world?

Also note that **no actual distro build would be affected** as they already define the constants.

So why not?

@ed I proposed a simple solution as soon as the issue has been considered by the team (unfortunately, to close it without much reflection).

The solution is pretty simple: fail early.

Just make the build fail if the user didn't specify the required constants to `./configure`.

This way anybody can pick the desired values at compile time and won't get neither (pretty undetectable) personal data-leaks nor malfunctions.

#SystemD refuse to get rid of #Google #surveillance in the default build.

https://github.com/systemd/systemd/issues/34184

#Linux #OpenSource #FOSS #FreeSoftware #SurveillanceCapitalism

That moment when you realize the bug is not in the intrerpreter, but in the compiler...

#hacking

@anzu@livellosegreto.it

un anno prima di me!
(il primo account, su mastodon.social)

@GustavinoBevilacqua

Devono essere oggetti tangibili?

Poesie? Canzoni? Hack software?

@GustavinoBevilacqua

Ah ok... scusa avevo frainteso.

@ugone

@ugone

Ehm... non ho Facebook
Né WhatsApp, TikTok, Telegram, Instagram etc...

Il problema è come convincere persone che ne sono dipendenti, sorvegliate e manipolate per anni, a liberarsene.

È questo che chiedevo a @GustavinoBevilacqua

@GustavinoBevilacqua

Ti prego, spiegami come hai fatto!

Io tenni un corso alla dirigenza CGIL anni fa¹, ma Facebook e Google continuano a sorvegliare diversi loro canali di comunicazione.

¹ https://video.linuxtrent.it/w/p/ih87E19VKKsSTxAJYL6QhR

@ugone