Only because people kept writing horrible code and using Perl as an excuse. Perl is like C, your code is as readable and maintainable as you choose to make it. It's like that old saying about blaming your tools. Just stop writing crap code.
4,143 karma · joined August 6, 2019
Only because people kept writing horrible code and using Perl as an excuse. Perl is like C, your code is as readable and maintainable as you choose to make it. It's like that old saying about blaming your tools. Just stop writing crap code.
At this point we should just fork Firefox or focus on IceCat instead.
I'm from GenX. It can be done. We used to do it. Just stop playing their game. The only winning move is not to play.
“In 2021 these payments accounted for 83% of Mozilla’s revenue.”
OP just made one the best arguments in favor of breaking up Google's monopoly.
Because that's not how it works and companies like Meta know this when misleading it's users about their privacy.
Speech-to-text transcription is handled on your device. They never transmit the raw audio, there's no need to. A compressed text transcription of your conversation would only generate a few kilobytes of data. You would never notice it.
And the mic needs to be active in order to receive legitimate voice commands. If it can respond to your voice, the microphone is on and listening. That's the only way it can work.
I'll save everyone some time. In the year 2025, just assume any for profit corporation is stealing your data and you've waived all your rights as a consumer when you agreed to that ToS unless presented with compelling evidence to the contrary.
The main problem with DNT was the lack of legal and regulatory backing it received. Website owners could decide if they'd observe the DNT signal and there were no legal repercussions if they chose not to. This is where GPC is different.
....
What to do when receiving a GPC signal
It's up to the developer/business to decide how to treat the signal, for example, removing the user's details from third-party tracking or marketing, following a similar procedure as to when users opt out of sharing data for marketing purposes. If in CCPA jurisdiction, the signal must be observed to avoid legal repercussions.
So what's the difference? Without regulations, which is the real issue here, all this is meaningless just like DNT was. The system is solely based on trusting the site to comply. CCPA only applies in Europe. None of this would apply to users in the US but the article disingenuously implies it would:
At the time of writing, the Attorney General for California has recommended observation of GPC to comply with CCPA
That is not legally binding in any way. This is just DNT with extra step being sold as something it's not. I fail to see how this will benefit the user while making it harder for users to block trackers and advertisers. A site can't prevent you from blocking it's cookies because cookies are stored locally through the context of the browser. Site's can't prevent users from blocking, deleting or modifying cookies.
But GPC signals are sent via HTTP headers. Sites could prevent users from accessing the site by detecting if GPC is disabled by the user in the browser just by checking the HTTP headers, forcing users into sharing information with the site to be allowed to access the site.
Class warfare? Finally one of them says the quiet part out loud because that's what all this 'anti-woke' crap is actually about. Our rights are the 'woke' that they're waging their war against. The culture wars were artificially created to keep us from fighting a class war against our economic oppressors.