1. Forum
  2. General Discussion
  3. Renaming userscript and migrating to a new one
sjehuda Author

Hello,

I've decided to rebrand FREEdirector to Proxy Redirect.

Is there an automated manner to do so?

Currently, I've changed the older program to direct users to it's project page, in the hope they will see the message and install the new one, but it doesn't seem to work as the installation amount of the older programs keeps growing.

Please advise,
Schimon

Marti Admin

Re: @sjehuda:

Is there an automated manner to do so?

No and there won't be.

... but it doesn't seem to work as the installation amount of the older programs keeps growing.

--- /scripts/sjehuda/FREEdirector/source@30+6242765
+++ /scripts/sjehuda/FREEdirector/source
@@ -13,6 +13,7 @@
 // @version     30
 // @grant       none
 // @icon        data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHZpZXdCb3g9IjAgMCAxMDAgMTAwIj48dGV4dCB5PSIuOWVtIiBmb250LXNpemU9IjkwIj7wn5SAPC90ZXh0Pjwvc3ZnPgo=
+// @downloadURL https://openuserjs.org/install/sjehuda/Proxy_Redirect.user.js
 // ==/UserScript==
 
 location.href = 'https://openuserjs.org/scripts/sjehuda/FREEdirector#freedirector-is-now-known-as-proxy-redirect'
\ No newline at end of file

... is one option for you. Don't forget to @version bump so they get it. However you could nag them before you do that with an alert for a while then do the redirect. This will keep both copies on their machine so that's why I would say do the nag first. An example of a nag is here. Depends on how naggy you want to be.

As far as "(it) keeps growing" that will always be the case. If a user doesn't visit the site that is @included / @matched then they won't get the nag message... unless you get real naggy and change those to include the script everywhere. Just don't forget the appropriate return(s) and not execute the old script any further to avoid reports.

In general you'll probably always get hits from possible bad actors and other scraping sites that aren't all that sophisticated.

There's probably more ideas that others may have but it's all up to you what you do with your publication and how responsible you wish to terminate the old one.

OUJS Admin

sjehuda Author

Metablock // @downloadURL seems to solve this issue to some extent.