google and their ilk want posting code on the internet to incur legal obligations for the author to maintain that code to their standards. it used to be that software companies bought the tools they used, but now they all sip from pools of poo water such as npm. so to bring up the standards of the software they voluntarily download and embed into their products, they want the authors to be legally obliged to maintain the software to some standard, and if they do not, then they want a name they can sue. this is why google is trying to get a foothold into open source projects, why there's such a big focus on so-called software bill of materials and "securing" the so-called supply chain, why the eu is trying to enshrine these kinds of obligations into law with the so-called cyber resilience act (the linux foundation speculates that accepting seemingly well-meaning donations from companies could make you a "software manufacturer" under the cra), and why these real name policies are a thing.
i think the more likely explanation is that all those ladies are named marc jacobs, and they all have bags with their name on so they know it's their's
None of those hold a candle to Reiser5, a currently developed filesystem they voluntarily named after a guy who murdered his wife, and which causes dismay among the anti-SJW crowd in the phoronix comments when people talk about that fact
This is the kind of thing that would make me close the issue tracker and open up a mailing list with the gnarliest designed for netscape 2.0 web interface imaginable
if that's done on the device itself, and the stuff you're typing isn't sent anywhere, i have no problem with that. besides, iOS likes to suggest i put å in front of every english word, so disabling the predictive row wouldn't be a big loss for me anyway.
when the app is educational in nature, i have a huge problem with being offered "AI" generated courses, as that's basically asking me to give them money so i can be misled.
emma wrote
Reply to Real name policies by Seirdy
my thoughts on this are:
google and their ilk want posting code on the internet to incur legal obligations for the author to maintain that code to their standards. it used to be that software companies bought the tools they used, but now they all sip from pools of poo water such as npm. so to bring up the standards of the software they voluntarily download and embed into their products, they want the authors to be legally obliged to maintain the software to some standard, and if they do not, then they want a name they can sue. this is why google is trying to get a foothold into open source projects, why there's such a big focus on so-called software bill of materials and "securing" the so-called supply chain, why the eu is trying to enshrine these kinds of obligations into law with the so-called cyber resilience act (the linux foundation speculates that accepting seemingly well-meaning donations from companies could make you a "software manufacturer" under the cra), and why these real name policies are a thing.