tampermonkey VS aboutconfig

This extension makes use of JS computed property names to perform user specified dynamic actions on user specified elements.

I started working on an extension primarily for my own very specific use case. I knew of Tampermonkey and it's relatives before, but hadn't used it extensively. I also was following the news of MV3, so wasn't sure of their long term viability. But more than anything having recently got into frontend development I also just wanted to build an extension myself, getting to understand the newer limitation and alternatives was just a bonus point.

Literally a couple of days ago I got to know (From HN nonetheless https://news.ycombinator.com/item?id=38526277) that userscripts are going to be allowed in MV3 too, so I finally decided to actually check out ViolentMonkey, which is pretty neat, but from the looks of it would have to migrate to `chrome.userScripts.register` which would eventually require `userScripts` permission and with it would need [developer mode enabled](https://developer.chrome.com/docs/extensions/reference/api/u...). While browsing through the subsequent discussions I saw there were many other alternatives for dynamic script execution, from creating and the dynamic code to `` tags to using `evaljs`, but I wasn't aware of them while building this (see for ex: <a href="https://news.ycombinator.com/item?id=31425256">https://news.ycombinator.com/item?id=31425256</a> and <a href="https://github.com/Tampermonkey/tampermonkey/issues/644#issuecomment-857838249">https://github.com/Tampermonkey/tampermonkey/issues/644#issu...</a>) (and tbf it wan't even my goal to get full JS execution in my extension).<p>Long term my goal was to build a small JSON config for the actions needed and parse and apply them to have the desired behavior. I also was planning on exposing some extension only behavior (like tab functionality) via message passing with service workers (The config could be something like

Do you use "Never Remember History"? There are bug reports about it. Fix is soon to be released.

Yes, I'm having the exact same problem. It was updated on Nov. 30 and I can't find a way to downgrade back to the last version. There's been several issues posted on the tampermonkey github recently but I don't have enough technical knowledge to know if any of those issues applies to this problem. And just like you, I can't even see my scripts to move them to a different script manager.

I have no damn idea why Tampermonkey, which as very best I can tell is closed source <https://github.com/Tampermonkey/tampermonkey/blob/master/REA...>, is on the "blessed" Firefox for Android list when Violentmonkey <https://github.com/violentmonkey/violentmonkey#readme> is MIT, although I readily admit doesn't it have a "politically correct" name

I use it a lot and it used to be on github until version 2.9. I guess I could use that but wondering if there are some other nice selfhosted versions where I can easily modify my Chrome webpages that I should consider.

I want to chime on that as it's worth noting that Tampermonkey is no longer open source. I mean it's like that for years - its GitHub repo clearly stands it's just an archive version and commits there date back to 2018. Here's one of the first posts when author went proprietary license and started gaining data (with his comment btw) and technically there's also Security section in FAQ and full Privacy Policy. Also FWIK website is the only place you get info about changes - highlighting that to stop looking for insights on GitHub.

If you can't the answers you're looking for in the Tampermonkey FAQ, you can ask them in the official Tampermonkey support forum.

Tampermonkey devs have implemented it but didn't release it yet and Violentmonkey devs don't want to implement it, so I guess I'm not fixing this issue anytime soon.

Specific case: uBlock Origin seems to block TamperMonkey from either injecting or running my userscript. (See https://github.com/Tampermonkey/tampermonkey/issues/1709 ) I was thinking it might be one of the above rules but I can't really get much out of the logger, and trying to disable those rules doesn't work. Does anyone have an idea on how to progress?

https://github.com/Tampermonkey/tampermonkey/blob/master/COP...

this says GPL so unless they update their license file here, this stays

I'm glad they're making changes, but I'd advise everyone to watch closely what they end up implementing and what potential security and privacy risks will be introduced. It seems like I'm having to disable something or other with every major update of firefox lately, and as long as they continue to let me disable risky features I'll keep using it. Nothing strikes a better balance between useful and secure like hardened firefox, but it takes a lot of vigilance and a willingness to add or modify hundreds of about:config options (after installing https://github.com/earthlng/aboutconfig)

Therefore I now use this, which gives me the traditional layout and functionality: https://github.com/earthlng/aboutconfig

from an autoconfig script you can call registrar.registerFactory(CID, className, contractID, factory) and set up the same kinds of objects that firefox does. I haven't explored this that much, so far only used it to create a new about: page. if you wanna see that example here's the link. it's just a regular autoconfig script, but of course it needs some html for that new URL to lead to.

In this example we're just assigning the URL about:cfg to earthlng's pre-87 aboutconfig module. Its path would normally be something like chrome://userchromejs/content/aboutconfig/config.xhtml, which isn't perceived as a system page and is a bit of a nuisance to type in the urlbar. Shortening that particular url and making it fit in like a genuine system page would was my main reason for looking into this, but it could conceivably be done with any URL. local files, extensions, etc. The new URL even shows up in about:about which is pretty cool.

the page is no longer present, so need an integration (https://github.com/earthlng/aboutconfig)