Greasemonkey Port 3.10.0.1rc4pre-sm.xpi is available now at the SF file repo.

This fixes an inconsistent compatibility issue introduced with SM 2.53.14 through 2.53.16 with the locale preventing management and general usage failure... some SM preferences were renamed/missing but not in all SM locales which is very odd. em:minVersion remains the same i.e. SeaMonkey 2.40 or better.

Re: @sjehuda:

SPAM!

1. This is the Authors own issue... so within reason it's not spam as it was already pre-verified as doing exactly what it says vs the script source.
2. You are spamming this script issue with your message... more precisely harassing. You are doing your best to test your ability to be eligible to be removed permanently.
3. If you feel a user is spamming you flag the User with brief yet concise details.

Please don't test my patience any more. The subject of this intervention is closed here.

OUJS Admin

Re: @sjehuda:

I've just checked if something has changed since then.

Use development only and not production. Further development questions beyond this response will be ignored here on production. Please reread.

I'll look into it and add Feeds for OUJS

Probably related to next see also... again please use development.

and later add a Web Browser News like the one of USO.

See #914

I don't have (the time to establish) a node.js server.

There's Development... just give it a read.

Do we have a sandbox node.js server of OUJS to make tests on?

Again Development (Last time I'll remind you). If you want a clean or dirty DB with a basic auth set go to https://github.com/OpenUserJS/OpenUserJS.org/tree/master/dev and import that for MongoDB... otherwise make your own auth keys.

Nope.

See from a Development search... #15 and #242 on Development... I know you are there. :P

OUJS Admin

You do not need to advertise this script outside of its homepage for releases like you did in the General Discussions. Your account menu lists as well as the global Userscripts list is enough for notifying people of your news.

If you do it again your account may be eligible for removal. The discussion has been deleted.

Thank you for your immediate cooperation.

OUJS Admin

Re: @sjehuda:

Thanks for the visit however this can be achieved outside of the library in post-op before it is applied to the website.

This is also very beta still and very much on the back burner.

Closing as not planned.

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

Alright.. think I found the issue. Love Unicode sometimes (sarcasm).

Try it now.

OUJS Admin

Re: @gyakkun:

If it's due to upstream dependency update, maybe rollback to a previous version is a good idea?

Nope.

However both of you haven't given me any concrete links to the issue... however I guessed that @gyakkun changed some source recently and encountered it from the image included... and I can replicate on unminified code.

This shouldn't be happening ever... I will look into it more shortly.

OUJS Admin

This is obfuscated code... which means it could be malware. I would suggest that you uninstall it for sure as it is going away.

OUJS Admin

Re: @Anakunda:

some library sources are cut before end especially if fetched as library.min.js.

If you think it's a bug then it should be on Development not here.

Re: @Anakunda:

Just fetching the raw source is broken.

Semi-colons can be removed since terser defaults at that version may be configured that way. i.e. we don't do it... it's an upstream issue. We are also using terser@v4.x due to incompatibilities with terser@v5.x... so if there's an error don't use it or find some other possibly shorter workaround similar to the one you've mentioned in your code to get the result you want. i.e. we can't do anything about it especially here on Production instead of Development. You would also most likely be redirected to upstream anyhow. Btw some of our served .js for the site itself doesn't exhibit your behavior because it's working without your "work-around". i.e. we (you, me, the dog/cat, etc.) all would know instantly. bootstrap-markdown.js here on OUJS is one of many examples compared to it's native source there. It would appear from the lack of trailing closing square bracket and semicolon in your latest library update (without your comment block) that it is a terser error.

As a general rule of thumb also check your device(s) for malware, corruption of storage media or memory (ran into several machines that requires exact CPU MHz specs used instead of what was advertised in their XMP/EXPO/equivalent... segmentation faults specifically which are rare when there should be none), if your ISP is preventing you from doing something, and of course a clean browser profile and other non-chromium based browser.

OUJS Admin.

P.S. We have a special key for edge cases that don't have a work-around so you can let others know about a possible code incompatibility. See here.

Re: @adaaaam:

Bye

Re: @adamlui:

Pointing out what I believe to be a glitch

No... assuming it was a glitch is another of your errors when it was clearly user error with the casing.

Yet many other scripts (including my previous commit) pass validation with lower cases

That's because the correct SPDX short identifier was used in most cases... unlike your user error. Enforcement of correct SPDX codes was done after a few years of abuse which is why Reeks is arbitrated to MIT. The community at large disagrees with your incorrect assessment.

but the smarter idea is remove case sensitivity

It would not be smarter and the fourth bullet at https://openuserjs.org/about/Terms-of-Service#etiquette is what you are treading dangerously close to. Don't be snarky and admit you made a mistake like we all do at some point (a thank you would have been appropriate as well). If you continue the passive-agressive behavior we will apply the default TOS action.

I don't need a faster response,...

You were helped you should be grateful not snarky. This is your only warning.

OUJS Admin

Re: @adamlui:

My script fails to sync from github when using @license mit as a metadata

See the incorrect commit and license change at your repo.

MIT @license wrongly fails validation due to 'not OSI primary'

Rightly fails validation because usually that SPDX short identifier is all uppercase. This is also how it is shown at https://opensource.org/licenses/MIT and https://spdx.org/licenses/MIT.html .

Make the fix to your source and please try to be a little more courteous when creating a post here. As I have continually said if you think there is a site issue Development (the link at the bottom of every page) is usually the place to get a faster response. If it is truly a site issue then we can work on it over there.

OUJS Admin

This maintenance is completed... there will be more at some point.

Sometime in the next 96 hours a backup and migration is scheduled (depending on time available). Status will be, as usual, reflected on Development with a topic label which is usually towards the right/top of the page.

Thanks for your patience.

OUJS Admin

Re: @Mayriad:

Here's a relevant response from derjanb that we've been going off of (and the rest of the topic). There are more instances elsewhere on his issue tracker but the overall perceived responses is that TM, and their users, doesn't really like the asynchronous GM 4.x API all that much. If derjanb were to clearly indicate support for this in his documentation then we can add it... until it's more official our hands are tied. It is a very easy addition on our end but their end requires wording/supporting it outright instead of "shadowing" GM 4.x. The only reason we support some of the extended GM objects is because VM has it outright listed here and of course GM proper.

I think the userscript scene is moving quite slowly, so I have no idea when it will be documented.

Go bug 'em on a new documentation type issue. You might want to reference the response over there so we can all get a little clearer picture on what TM's intentions are as of late.

OUJS Admin

Re: @Mayriad:

Let's start with what .user.js engine supports this... i.e. We need verified public syntax documentation.

GM nor TM, and VM seems to document it:

• https://wiki.greasespot.net/Greasemonkey_Manual:API (and obviously GM Port since I maintain that... doesn't support GM.* anyways in v3.x compatibility)
• https://www.tampermonkey.net/documentation.php
• https://violentmonkey.github.io/api/gm/

So until it's full publicly documented/supported then we can make a decision on that on Development.

OUJS Admin

--- /scripts/jaidedctrl/Nitter_Redirect/source@+cca1470
+++ /scripts/jaidedctrl/Nitter_Redirect/source
@@ -3,7 +3,7 @@
 // @description  Redirect Twitter to Nitter
 // @author       jaidedctrl
 // @license      GPL-3.0-or-later; http://www.gnu.org/licenses/gpl-3.0.txt
-// @match        *://*twitter.com/*
+// @match        *://*.twitter.com/*
 // @run-at       document-start
 // ==/UserScript==
  

... makes it valid @match syntax from the standard documentation.

It is a good idea to correct this so the script rating doesn't fall.

OUJS Admin

Re: @macheteYeti:

You proposed a change only to @updateURL but this indicates I might need to do something else with @downloadURL as well?

Nope. However VM handles updating when @downloadURL is absent it doesn't seem to do an update in the logic either. It should default to the install source for both of those keys... but then there is your issue of it not doing the 2nd call to get full source... and the final return.

Appreciate all your help in debugging this.

Welcome and thank you for all you've done.

but you seem relatively frustrated with my choice of forum.

Nope... listing that as a consequence (hands tied here) of not being able to fully assist you with the time allotted...

But I did also post on VM's GitHub.

... however that helps. Subscribed.

Re: @macheteYeti:

https://imgur.com/a/gID94hT

That's the meta routine alright.

Are you able to offer any insights based on this info?

Also reexamined a bit deeper with the Violentmonkey (VM) code at violentmonkey/violentmonkey/blob/6098f9e/src/background/utils/update.js#L101-L104 and that appears to be the culprit. It seems to be not doing a second call to get the full source data and just does a return of what it first retrieved from us (just the meta) with the text/x-userscript-meta header... which is highly probable why it's getting "truncated" by your .user.js engine.

Try this instead and report back:

--- /scripts/macheteYeti/[LWAF]_Open_Saved_Searches_Hide/source@7+9ee99d6
+++ /scripts/macheteYeti/[LWAF]_Open_Saved_Searches_Hide/source
@@ -8,7 +8,7 @@
 // @require     https://cdnjs.cloudflare.com/ajax/libs/arrive/2.4.1/arrive.min.js
 // @require https://raw.githubusercontent.com/phstc/jquery-dateFormat/master/dist/jquery-dateformat.min.js
 // @downloadURL https://openuserjs.org/install/macheteYeti/[LWAF]_Open_Saved_Searches_Hide.user.js
-// @updateURL https://openuserjs.org/install/macheteYeti/[LWAF]_Open_Saved_Searches_Hide.user.js
+// @updateURL https://openuserjs.org/meta/macheteYeti/[LWAF]_Open_Saved_Searches_Hide.meta.js
 // @author       macheteYeti
 // @description  Opens AC saved searches & hide recently active
 // @grant       GM_addStyle

... to see what VM is going to do with it next update cycle.

not seeing an edit button.

That's what the Preview button is for. Also more than likely imgur doesn't allow hot linking so the URL is the the best option.

To reiterate the importance of opening an issue like this on GitHub development (the link at the bottom of every page here on OUJS) I would have been able to summon gera2ld or tophf to the issue so they could look into it further. Since you chose here... you get to do this all over again on VM's repo with an issue there if you want your @updateURL and @downloadURL styling to not change.

OUJS Admin

Re: @macheteYeti:

so I am not sure that if I documented it the next time it occurred that you would be available to investigate.

Yes then it can narrow down the UTC time in the logging and/or any other patterns that may emerge. Don't try to guess what is useful and what isn't here just yet.

I also just checked Violenmonkey code and it appears to be correct as well for the text/x-userscript-meta albeit your symptoms described are the opposite which is a use case that can't happen in normal circumstances. When that "partial" meta comes through capture it for your script and paste it in a code fence. If you want to potentially rule out a browser/extension caching issue with text/x-userscript-meta then please use the .meta.js routine described here. I've also seen alternate DNS providers (Cloudflare, etc) and/or proxies strip or even add headers, ignore headers, etc.... so perhaps this could be a choice for you.

I'm not sure any of my users would eagerly reinstall a browser to debug this

If it's profile corruption then create another profile and test it there with only the basics. i.e. no other extensions except the .user.js engine of choice with default settings. If it's browser corruption then there is no other choice.

OUJS Admin

Re: @macheteYeti:

For about a week we've been struggling with script updates.

What scripts to test against?

When the user clicks the install button, the script is truncated and only some of the meta lines are visible.

Working completely for me on your most recently updated script. Again what scripts?

I believe this must be some kind of OpenUserJS outage

Nothing in the error logs and is working for the tests that I just ran.

so I am hoping someone has some insights on how to ensure this does not happen

Tell your users to try a clean profile. Chrome itself bombed on several Windows machines recently and had to be reinstalled from scratch. Fx is having some issues elsewhere as well with some other sites.

In short nothing detected here. If you can give a solid steps to reproduce we'll look into it... otherwise the dreaded "Works for Me" stands for the moment with the vagueness you've given here. Ideally this should have been on development as an issue not production here... but I was doing my daily routines and saw this.

OUJS Admin

Re: @Bloggerpemula:

is that possible to disable Submit Code as Fork button ?

See https://openuserjs.org/about/Terms-of-Service#reserved-rights at last bullet.

Re: @Bloggerpemula:

is there any admin or moderator who can explain to me ?

Already did starting at https://openuserjs.org/scripts/Bloggerpemula/Bypass_All_Shortlinks_Manual_Captcha/issues/Script_info_issue...#comment-17ebd1cf739

OUJS Admin

Test