Gossip Relinker

By Scytale Last update Apr 26, 2013 — Installed 6,064 times.

Update notices

Subscribe to Update notices 7 posts, 4 voices

AnotherUser321 User

With Greasemonkey automatically checking for updated scripts once a week I have seen an update notice for Gossip Relinker a couple times now. Even though I have manually updated the script when new versions came out. Just wondering if you have made any changes/tweaks that might cause this?

Scytale Script's Author

I use a 3rd party update plugin that basically just uses the version number to see if a new script has been released. I haven't made any changes to that part of the script.

That said, there have been a number of minor updates over the past few weeks, so maybe that is what you are seeing? I thought if you manually updated then the update script would leave you alone but perhaps it works in a slightly different way. Keep me posted if you see weird behavior from it and I can look into it.

Marti Scriptwright

AnotherUser321 wrote:
I have seen an update notice for Gossip Relinker a couple times now.
Scytale wrote:
That said, there have been a number of minor updates over the past few weeks, so maybe that is what you are seeing?
There is a known bug upstream with Greasemonkey (GM) right now that is triggering false updates in 1.2 and 1.3 (1.4 isn't much better but seems to have resolved this particular issue). Even with usoCheckup(usoC) added to your code GMs updater will still trigger. If you wish to disable GMs updater in your source code, just for this script, add these lines to your metadata block and usoC will be exclusive:
// @updateURL file:
// @installURL file:
// @downloadURL file:

Sometime in the near future too you will probably want to add the @grant access permissions in the metadata block too... the core of usoC currently uses these:
// @grant GM_getValue
// @grant GM_log
// @grant GM_openInTab
// @grant GM_registerMenuCommand
// @grant GM_setValue
// @grant GM_xmlhttpRequest

plus any of your own GM_* API calls and unsafeWindow

See also:

  • this topic for a important privacy and security issue with GMs updater that still hasn't been fixed properly.

If you don't wish to deal with most of this you can remove the @require for usoC and let the end User choose to install an updater with uso - installWith but you will still need at minimum // @grant unsafeWindow since you use it in this source code currently. installWith will add what it needs in the usoC wrapper for @grants and the end user can choose to enable the GM updater... currently installWith disables GMs updater by default if a supported updater is added or the usoCheckup Μετα where no updater is added only twiddling with the metadata block.

If you choose this option you may wish to add a blurb on your homepage like GIJoe did... "If you want an updater added go there"... or some equivalent verbage on your scripts homepage with which specific updater/theme you recommend.

Hope this helps. :)

AnotherUser321 User

After reading Marti's post I checked my version of Greasemonkey and saw that it was 1.3 and was waiting for a restart to get to 1.4 which I have done. So we'll see if this fixes the updater problem. Although that privacy issue is a little bit annoying.

Scytale Script's Author

How do you guys feel about the updater situation? I'd be happy to disable the GM updater, usoC, or both depending on what works better for the users of the script. Please post here if you have an opinion.

AnotherUser321 User

Updating to GM 1.4 seems to have fixed the problem with the constant update notices so I'm happy with things as they are.

bathsheda User

AnotherUser321 wrote:
privacy issue is a little bit annoying.
I foresee them further trying to hack into everyone's privacy with http://github.com/greasemonkey/greasemonkey/issues/1651.

The Grim is upon us.