Post AcWAM4SCOtIg53rJ5M by blacklight@social.platypush.tech
 (DIR) More posts by blacklight@social.platypush.tech
 (DIR) Post #AcWAM4SCOtIg53rJ5M by blacklight@social.platypush.tech
       2023-12-05T08:14:36Z
       
       0 likes, 0 repeats
       
       User scripts on Chrome (which includes everything that runs on TamperMonkey, Greasemonkey, ViolentMonkey and all of their mutations) will require developer mode to be enabled.Of course, I'm very sure that this is because of non-technical people installing one of those extensions by mistake, copying and running some non-trusted JavaScript by mistake, and mistakenly getting their browser compromised.Not because Google has decided to throw all of its weight to break the browsing experience for all the power users, if that's what it takes to kill adblockers.This is just a little more pointless friction that Google is adding to discourage users from tinkering with their tools. All the guides on how to use user scripts for something even as trivial as changing the background of a website will now have to be modified to include text such as "this requires you to permanently enable developer mode if you're using Chrome".Yesterday I also received a passive aggressive email informing that my MV2 extensions will stop working by June of next year, and hence I have only 6 months to rewrite them with MV3.I'll make sure that not a single one of them gets migrated to their declarativeNetRequest abhorrent API. Using the MV3 API is like playing a piano blindfolded and with the right hand tied behind your back for no practical reason other than the owner of the piano being a sadist.My extensions from now on will be Firefox-only, I'm also planning to pull both the Platypush and RSS Viewer extensions from the Chrome Store.We as FOSS developers now have a duty of going the extra step and making sure that our extensions and scripts won't work on Chrome, if breaking extensions, refusing to embrace their extension manifest and user script changes, and purposefully writing code that breaks on Chrome is what it takes to pull people away from that cesspit - that's exactly the kind of stuff that Google has been doing against competitors for years anyway.Engineering time is precious, and keeping up with whatever a hostile company like Google comes up with to defend their broken adware business model is a waste of engineering time. There isn't a single reason not to use Firefox.https://developer.chrome.com/docs/extensions/reference/api/userScripts
       
 (DIR) Post #AcWAM5a2DFA7ZeX4wC by FreePietje@x0f.org
       2023-12-06T01:49:23Z
       
       0 likes, 0 repeats
       
       @blacklight "We as FOSS developers now have a duty of going the extra step and making sure that our extensions and scripts won't work on Chrome, if breaking extensions, refusing to embrace their extension manifest and user script changes, and purposefully writing code that breaks on Chrome is what it takes to pull people away from that cesspit - that's exactly the kind of stuff that Google has been doing against competitors for years anyway."💯