1. Forum
  2. General Discussion
  3. Transfering userscript to another owner
sjehuda Author

I have contacted the original author of RSS+Atom_Feed_Subscribe_Button_Generator and asked him to maintain a version at OUJS too. He agreed.

May the admins kindly make the transfer or should we handle it on our own?

Of course, I assume that we would have to keep some paths (not the page) for Userscript manager software to make the required updates.

Marti Admin

There is an inconsistency in the script source vs. what you did @sjehuda. Copyright year term is incorrect compared to original. That must remain the same as the USO source code page. Also the license header block has to remain forever in any publishing. It can be updated year wise of course to 2023 if it's the original author. Technically your name should also appear for the period that you managed your copy @sjehuda

Secondly... I've forked it (which you could have done @junkblocker and how I did it as you... you can always undo it and redo it yourself if you want the practice but I also copied the script info markdown) by going to sjehudas script Source Code page and clicked the Submit Code as Fork. This should be sufficient enough.

As far as your users @sjehuda you'll have to do your usual deprecation method (or something new) that we've talked about before. You can always create // @downloadURL https://openuserjs.org/install/junkblocker/RSS+Atom_Feed_Subscribe_Button_Generator.user.js so that script updates you trigger load junkblockers on update... then the user will need to uninstall yours otherwise two copies will be present on their system.

And @junkblocker you would also ideally add that key in the UserScript metadata block but also the // @updateURL https://openuserjs.org/meta/junkblocker/RSS+Atom_Feed_Subscribe_Button_Generator.meta.js... so to keep the users from getting confused or their .user.js engine managers.

OUJS Admin

Marti Admin

Here's what I mean about the license header and keys in code:

--- /scripts/sjehuda/RSS+Atom_Feed_Subscribe_Button_Generator/source@2.1+6350c31
+++ /scripts/sjehuda/RSS+Atom_Feed_Subscribe_Button_Generator/source
@@ -11,10 +11,12 @@
 // @version     2.1
 // @date        2013-04-19
 // @icon        https://upload.wikimedia.org/wikipedia/en/thumb/4/43/Feed-icon.svg/128px-Feed-icon.svg.png
+// @downloadURL https://openuserjs.org/install/junkblocker/RSS+Atom_Feed_Subscribe_Button_Generator.user.js
 // ==/UserScript==
 
 /*
- * Copyright (c) 2006-2013, Manpreet Singh [junkblocker@yahoo.com]
+ * Copyright (c) 2006-2014, Manpreet Singh [junkblocker@yahoo.com]
+ * Copyright (c) 2017-2023, Schimon Jehudah (http://schimon.i2p)
  *
  * Permission is hereby granted, free of charge, to any person
  * obtaining a copy of this software and associated documentation

... and ...

--- /scripts/junkblocker/RSS+Atom_Feed_Subscribe_Button_Generator/source@2.1+6350c31
+++ /scripts/junkblocker/RSS+Atom_Feed_Subscribe_Button_Generator/source
@@ -11,10 +11,14 @@
 // @version     2.1
 // @date        2013-04-19
 // @icon        https://upload.wikimedia.org/wikipedia/en/thumb/4/43/Feed-icon.svg/128px-Feed-icon.svg.png
+// @updateURL   https://openuserjs.org/meta/junkblocker/RSS+Atom_Feed_Subscribe_Button_Generator.meta.js
+// @downloadURL https://openuserjs.org/install/junkblocker/RSS+Atom_Feed_Subscribe_Button_Generator.user.js
 // ==/UserScript==
 
 /*
- * Copyright (c) 2006-2013, Manpreet Singh [junkblocker@yahoo.com]
+ * Copyright (c) 2006-2014, Manpreet Singh [junkblocker@yahoo.com]
+ * Copyright (c) 2017-2023, Schimon Jehudah (http://schimon.i2p)
+ * Copyright (c) 2023, Manpreet Singh [junkblocker@yahoo.com]
  *
  * Permission is hereby granted, free of charge, to any person
  * obtaining a copy of this software and associated documentation

As far as the unsupported @date key that can be handled however both accounts see fit.

sjehuda Author

Script has been updated (copy of version 2.7) with the following metablocks:

- // @version     2.1
+ // @version     2.6 <-- this is intentional
+ // @homepageURL https://openuserjs.org/scripts/junkblocker/RSS+Atom_Feed_Subscribe_Button_Generator
+ // @supportURL  https://openuserjs.org/scripts/junkblocker/RSS+Atom_Feed_Subscribe_Button_Generator/source
+ // @updateURL   https://openuserjs.org/meta/junkblocker/RSS+Atom_Feed_Subscribe_Button_Generator.meta.js
// @downloadURL  https://openuserjs.org/install/junkblocker/RSS+Atom_Feed_Subscribe_Button_Generator.user.js

@junkblocker
Please update your version to 2.7.

@Marti
Is it possible to hide page from search and profile?
Is it also possible to reset installs number? (5415)

Marti Admin

Re: @sjehuda:

Is it possible to hide page from search and profile?

No.

Is it also possible to reset installs number? (5415)

No. If you are worried about increases for the future see https://openuserjs.org/about/Frequently-Asked-Questions#q-is-there-a-way-to-not-count-script-updates-with-this-sites-install-counter-

// @supportURL https://openuserjs.org/scripts/junkblocker/RSS+Atom_Feed_Subscribe_Button_Generator/source

That's not how that key works. Should be https://openuserjs.org/scripts/junkblocker/RSS+Atom_Feed_Subscribe_Button_Generator/issues

Please update your version to 2.7

Yes... both of you should version bump after you make all the necessary changes to trigger the .user.js engine manager to know that there is one.

OUJS Admin

sjehuda Author

The numbers are soaring, despite the message I have posted. What should I do?

Marti Admin

Re: @sjehuda:

The numbers are soaring, despite the message I have posted. What should I do?

If I were a new user and saw your version vs the other accounts version... I'd say... hmmm yours seems to look newer so try yours...

In a plain, blunt, evaluation... your scripts @version is 2.6 and your source mentions 2.7 ... and the transferred is at 2.1 ... i.e. it was poorly maintained by both accounts. If I were to use it, I would see that and down vote both scripts for lack of consistency.

OUJS Admin

sjehuda Author

I give up.

Even my attempts against it did not appear to work.

I will contact the original author for further planning.