Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

New rule regarding script update checks

edited October 2017 in Site Feedback Firefox
Today I heard from my hosting provider that last month, the site went over its bandwidth allowance. Looking into this I found some scripts that were excessively checking for updates, resulting in hundreds of gigabytes of daily bandwidth. Looking at the code for these scripts, it appears they checked for updates every time the script executed.

So starting right now, scripts must only check for updates after a reasonable period (1 day?) has passed since the last check. Any script I find making excessive requests will have its update URL blocked until the issue is fixed in its code.

If anyone has any example code on how to correctly perform update checks, that would be useful.


  • BTW, I don't understand why would a script author want to check the update URL manually. A userscript manager addon/extension checks for that automatically.

  • Do all user script managers do that?
  • Tampermonkey and Greasemonkey do, which accounts for 99.999% of all script managers installations, I guess.

  • With this information in mind, I'm happy to disable the auto-update checking from inside my script completely. Thanks wOxxOm :)

  • wOxxOm said:

    Tampermonkey and Greasemonkey do, which accounts for 99.999% of all script managers installations, I guess.

    Violentmonkey also checks for userscript updates.
  • Guys/Gals, I use some fairly old scripts, it might be years - or never- before the authors remove the update check -- what would we manually need to look for & comment-out to remove the check?

  • Really, it's only a problem for the site if there's a ton of bandwidth being used. If the script's update URL does not appear as one of the top offenders, I will not be proactively doing anything about it.
  • Greasemonkey seems to not have an update check in place at the moment in version 4.0:

    So, sometimes an script internal update check will bring advantages. Also I like to display more information and I am absolutely no fan of silent updates. There was one time where a library used in multiple allowed scripts was hacked. This hack destroyed hundreds of accounts in an online game. In the end the game provider rolled back more than 100 game servers world wide. Thus, I am more a fan of active updates of userscripts. Usually I do this by setting the update url to about:blank and use my script internal updater. As the url is replaced here at Greasy Fork, this will not work, but at least for my privately hosted scripts it is fine.

    My update logic can be found here:

    It let's the user decide between different update check intervals (including no check at all) and also provides an option to check manually or hide notifications for specific updates or patch levels.

  • Greasemonkey 4 is an early work-in-progress so its temporary lack of the auto-update feature may be disregarded.

Sign In or Register to comment.