Posted September 04, 2018
high rated
I have two suggestions and a question.
First, I'd recommend ViolentMonkey over TamperMonkey. ViolentMonkey is a fork of GreaseMonkey v3 and seems to be as open about its development as Greasemonkey, while I've always been wary of TamperMonkey's custom license and I never did conclusively determine whether there was a public source repo.
Second, have you considered putting AF up on GreasyFork.org?
1. Pointing people at GreasyFork will avoid the Firefox CSP issue
2. People who go to GreasyFork looking for GOG scripts will be able to find it. (Barefoot Essentials is hosted there already.)
3. The "Source Syncing" feature can keep your workflow the same.
GreasyFork supports automatically watching a git repository for updates to both your script (from which it extracts everything on the GreasyFork page except the description and screenshots) and the description... though, if you want pushes to go live both instantly and automatically, you'll you'll need to use a full-blown GitHub repo rather than Gist so you can turn on webhook-based update triggering rather than using polling or manual triggering.)
4. GreasyFork adds an extra layer of security for users by doing safety checks on updates before pushing them public.
(eg. It applies a whitelist to @require to limit the potential for sneaky stuff)
Direct GitHub repository URLs are explicitly *not* on the whitelist, but your jQuery URL is on the whitelist and your attrchange dependency is on cdnjs, which is whitelisted. I haven't tracked down a whitelisted jquery.highlight.js URL on a CDN, but you're allowed to @require from GitHub via RawGit as long as you link to a specific commit.
OpenUserJS is another such site that's popular, but their documentation is poor, so I wasn't able to determine whether their features match GreasyFork's.
Third, are there any plans to support GreaseMonkey v4's promise-based APIs via the back-compat polyfill as Barefoot Essentials has done?
I intend to target GreaseMonkey 4 for my own scripts (which make up the lion's share of scripts requiring @grant in my browser), since a promise-based API gives more freedom for performance optimization, and it'd be a shame to have to choose between losing AF and keeping a copy of ViolentMonkey installed in parallel with GreaseMonkey 4 just to toggle it on when I want AF.
(Aside from AF, the only script requiring @grant that I have installed and didn't write myself is an unmaintained script that was last updated in 2009 called "Try This Search On" which I've been doing minimal maintenance on every time my installed copy breaks.)
First, I'd recommend ViolentMonkey over TamperMonkey. ViolentMonkey is a fork of GreaseMonkey v3 and seems to be as open about its development as Greasemonkey, while I've always been wary of TamperMonkey's custom license and I never did conclusively determine whether there was a public source repo.
Second, have you considered putting AF up on GreasyFork.org?
1. Pointing people at GreasyFork will avoid the Firefox CSP issue
2. People who go to GreasyFork looking for GOG scripts will be able to find it. (Barefoot Essentials is hosted there already.)
3. The "Source Syncing" feature can keep your workflow the same.
GreasyFork supports automatically watching a git repository for updates to both your script (from which it extracts everything on the GreasyFork page except the description and screenshots) and the description... though, if you want pushes to go live both instantly and automatically, you'll you'll need to use a full-blown GitHub repo rather than Gist so you can turn on webhook-based update triggering rather than using polling or manual triggering.)
4. GreasyFork adds an extra layer of security for users by doing safety checks on updates before pushing them public.
(eg. It applies a whitelist to @require to limit the potential for sneaky stuff)
Direct GitHub repository URLs are explicitly *not* on the whitelist, but your jQuery URL is on the whitelist and your attrchange dependency is on cdnjs, which is whitelisted. I haven't tracked down a whitelisted jquery.highlight.js URL on a CDN, but you're allowed to @require from GitHub via RawGit as long as you link to a specific commit.
OpenUserJS is another such site that's popular, but their documentation is poor, so I wasn't able to determine whether their features match GreasyFork's.
Third, are there any plans to support GreaseMonkey v4's promise-based APIs via the back-compat polyfill as Barefoot Essentials has done?
I intend to target GreaseMonkey 4 for my own scripts (which make up the lion's share of scripts requiring @grant in my browser), since a promise-based API gives more freedom for performance optimization, and it'd be a shame to have to choose between losing AF and keeping a copy of ViolentMonkey installed in parallel with GreaseMonkey 4 just to toggle it on when I want AF.
(Aside from AF, the only script requiring @grant that I have installed and didn't write myself is an unmaintained script that was last updated in 2009 called "Try This Search On" which I've been doing minimal maintenance on every time my installed copy breaks.)
