Cocaine. Jesus fuck. I'm not particularly angry with you, OP, just at the trend of advertiser friendly self-censoring that's making its way into the fediverse.
cadekat
One critical benefit of the rubber duck is that it doesn't make things up.
You obviously haven't seen me rubber duck debug.
I don't believe it does, but I could be wrong!
If you want to be slightly fancier, you can use a btrfs subvolume and not have to worry about sizing partitions correctly.
Avoiding shorts is a feature IMO
I'm not claiming that it was "intuitive", just that the browser did tell the user exactly what the add-on was allowed to do. Sure, Chrome and Firefox deserve some blame for not making the warning more explicit/dire, but they did make an attempt. Overwriting cookies and rewriting affiliate links are subsets of "access your data".
Also, I'm not claiming that I knew exactly what Honey was doing, just that I suspected it was shady and recommended no one use it.
It wasn't "uncovered" though. This is their business model. I've told every person I know using Honey for years that it's a shady extension and they should stop using it. Unfortunately I don't have a huge following to offset Honey's massive ad spend.
I'm not calling anyone stupid, but stop treating this like it's new information. Your browser warned you this might happen when you installed the extension:
The fact that it must be collected at all is the problem. I have very little faith that the government will actually choose a privacy preserving solution, and even if they do, I doubt it'll be implemented perfectly.
I guess it was filibustered last time it came up. I'm hoping it will die as well, but I won't count on it.
That's "Chemical X" which is fine.