User scripts on Chrome (which includes TamperMonkey, Greasemonkey, Violent Monkey etc. and all of their customizations) 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 is an evil company that has decided to use all of its weight to break the browsing experience for all the power users, if that's what it takes to kill adblockers.
Google and its executives must burn in hell for their evil. And if you still use a Chromium-based browser you're also part of the problem.
Yesterday I also received a passive aggressive email from Google informing me 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. I won't waste a single minute of my dev time to rewrite my software in a way that benefits a rotten company that forces thousands of developers worldwide to invest days or weeks of development time to rewrite their extensions only because they've decide to declare a war on adblockers.
My extensions from now on will be Firefox-only, I'll pull out the entries from the Chrome Store, and you folks don't have a single excuse not to use Firefox.
https://developer.chrome.com/docs/extensions/reference/api/userScripts
Fabio Manganiello /
npub1v7…ukv0u
2023-12-05 09:14:36
Author Public Key
npub1v78mmuz20p6qd6nve30axhqu74avwn4f6z4grhug7755rat7wh3syukv0uPublished at
2023-12-05 09:14:36Event JSON
{
"id": "eb4ec1ce7d1799bfeef9101a54b47c244fd1e49671ec433e89fb004fa1b13e8e",
"pubkey": "678fbdf04a787406ea6ccc5fd35c1cf57ac74ea9d0aa81df88f7a941f57e75e3",
"created_at": 1701764076,
"kind": 1,
"tags": [
[
"proxy",
"https://social.platypush.tech/users/blacklight/statuses/111526810522003225",
"activitypub"
]
],
"content": "User scripts on Chrome (which includes TamperMonkey, Greasemonkey, Violent Monkey etc. and all of their customizations) will require developer mode to be enabled.\n\nOf 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.\n\nNot because Google is an evil company that has decided to use all of its weight to break the browsing experience for all the power users, if that's what it takes to kill adblockers.\n\nGoogle and its executives must burn in hell for their evil. And if you still use a Chromium-based browser you're also part of the problem.\n\nYesterday I also received a passive aggressive email from Google informing me that my MV2 extensions will stop working by June of next year, and hence I have only 6 months to rewrite them with MV3.\n\nI'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. I won't waste a single minute of my dev time to rewrite my software in a way that benefits a rotten company that forces thousands of developers worldwide to invest days or weeks of development time to rewrite their extensions only because they've decide to declare a war on adblockers.\n\nMy extensions from now on will be Firefox-only, I'll pull out the entries from the Chrome Store, and you folks don't have a single excuse not to use Firefox.\n\nhttps://developer.chrome.com/docs/extensions/reference/api/userScripts",
"sig": "2e9e3df843f83ea38395fde652ab8239a7805b0f73c7ebbd78551c8ffe1f67a3c23366fc64aafaa60b3e7e7d729cd14ad264ce874e4060eb64b1b0d9b1a317ee"
}