2 Answers
2

Don't use unsafeWindow, this will break in Chrome and will not even work in Firefox+Greasemonkey if the effective @grant changes.

Avoid leading * wildcards in @includes, if you can help it. This is a big performance hit. @match limits the wildcard scope and performs much better and reports the sites/security correctly on Chrome. This gets all current SE sites:

The regex match needs to be more robust, to account for all legal characters in the URL, and for anchors.

Use injection so that the script will work on most userscript-capable browsers (Chrome, Firefox, Opera, Safari, etc.).

Here's a variant of the script I've been using. It also adds a "revisions" link since a post's history is sometimes hidden. It works on Chrome and Firefox, and should work on most other userscript-capable browsers:

I noticed this seems to have stopped working so I posted a small tweak as a new answer, but then noticed you have a gist with the download link. I wasn't sure what the best way was to handle it - maybe you'd be best to update your gist with the change and just delete my answer once done assuming it looks OK to you?
– PeterJAug 28 at 11:42

Thanks, @PeterJ. It looks like they changed the markup in the last day or so. Updated the script and will try to remember to move it to GitHub proper on some future rainy day...
– Brock Adams♦Aug 28 at 15:14