Re: @Mr_FJ:

Any idea why?

Nope. Works for me. Try a different browser and/or a clean profile... then try again?

OUJS Admin

One other quick note... the oldest account gets priority... so any scripts on this account will get axed and you lose all of your stats for them.

via some sort of...

Flag this script. Put in the comment field what both of your accounts are. Do this for both of your accounts. Make it the same unique content string but as similar as possible since one flag will have your username here and the other flag will have the sanitized email address account name. This is the most private atm that I can think of for the both of us.

Then I may be able to investigate if it's possible and clear the flags. I'm quite busy atm but might find some time soon.

OUJS Admin

I'm one of those stupid users that initially registered with their e-mail address.

Reading the screen helps. ;)

OUJS Admin

Tick tock... Thursday, the 7th of March, 2019 is the deadline.

~13 minutes to do the maintenance... and back online. Thanks for the patience.

Re: @alonaar:

Since the link didn't work

That's because you used the ! in front of the markdown. ![...](https://imgur.com/a/m0vfSyO "comment") is what you typed. Imgur uses html and a script to show images at a share link... presuming they don't randomize the image(s) (there are two from your url)... the first one is currently https://i.imgur.com/lqxVpxH.png currently. So your second comment is the way to do it.

Anyhow... /end teach ;) :)

OUJS Admin

Sometime in the next 24 hours a backup is scheduled... not sure on the time since it's a new VPS and it might be faster or slower since it's bigger.

As some of you may know from following the Development link below google authentication is changing relatively soon. We've already put our feelers out for getting this fixed in our dependencies however there is some chatter, but not from our dependency developer, in the past several months.

As of the 28th of October, 2018 we disabled new Google authentications and only allow existing ones to authenticate. We are also awaiting the dependency to be updated and it could use votes and/or discussions at that dependency issue and PR. Obviously since I'm the backend VPS maintainer I can splice in the PR but that shouldn't be necessary nor is it wanted every time I update the site. e.g. This should be handled by the dependency not us. As a result...

It is strongly suggested that if you have google authentication only that you add a secondary one, under your preferences to avoid a repeat of Google Authentication Deprecation 1.0! e.g. if goo auth goes dead it goes dead until that peer dependency fixes it. I can't guarantee that existing goo accounts will continue to work either but we have done what we can within our workflow to hopefully avoid another goo fallout.

In the meantime we are watching this as a primary issue on our Development and when the goo deadline happens we'll see what fallout goo has done again this round.

Thanks for your continued patience.
OUJS Admin

See also:

• #1526 (Please do all technical queries over there as I most likely will not respond here for this announcement)
• jaredhanson/passport-google-oauth2#50 (Dependency Issue)
• jaredhanson/passport-google-oauth2#51 (A possible Dependency PR to begin the road to fixing this)

getElementById("img")

I've seen some browser issues with this particular method just recently. id is supposed to be unique to one element/tag albeit some sites still don't pay attention to this, use it incorrectly and optionally abusively... then .user.js doesn't seem to handle them in the scope they are assigned.

1. Try another browser and .user.js engine e.g. not TM and see if you can replicate the issue.
2. Try getElementsByTagName and see if that works better for you. You may need to use a selector with querySelectorAll if this alternative is "too wide" of a capture in the DOM.
3. Something else?

P.S. As OUJS Admin I fixed your lack of code fences on your snippets... please see this FAQ on how to use them.

Here's your commit where you changed the script @name thus it will always spawn a new script here on OUJS by design.

Migration is up to you how you handle your old @named script. Most user.js engines will spawn a new script as well and we match that behavior. e.g. this is your user error for changing the @name and not offering a migration path for your users. Yes you will lose all the script statistics if you change the @name. No we will not migrate your scripts because it is intended behavior.

Also not seeing any @description change in the corresponding GH commits as of right now.

Btw https://openuserjs.org/scripts/Mottie/GitHub_Indent_Comment_Blocks currently shows a publish date of Mar 26 2017... and where is this duplicate you are mentioning?

Re: @Mottie:

I recently modified the description on 5 of my userscripts. Now it won't automatically update, and if I attempt to import or edit the same script, it creates a brand new userscript.

Then you must have changed the @name somehow. Works for me at this commit and the corresponding webhook update of OUJS Unit Test e.g. PASS

Is there any way to prevent creation of a new script or at least transfer the current users from the old userscript to the new one?

OUJS is processing @name as expected. If you change @name it will always spawn a new script by design e.g. intended behavior... verify that you didn't change something that triggered a @name change. You've done a bunch of changes and it's difficult to see what you've done isolated to these five scripts in your GH commit history... perhaps link all changes in... (see next note)... on GH.

Finally this issue should be on GH if you feel it's an actual issue. Unreproducible on my end.

Please don't apply this to all urls in the browser. This is considered a form of obfuscation since it is unclear exactly where this is being applied.

You have a short period to fix this before the default TOS action is applied.

Thank you for your immediate cooperation.

OUJS Admin

Please don't apply this to all urls in the browser. This is considered a form of obfuscation since it is unclear exactly where this is being applied.

You have a short period to fix this before the default TOS action is applied.

Thank you for your immediate cooperation.

OUJS Admin

This might be a little on the old side of news but noticed it today. A few Authors here are using it in script source for some assets.

Re: https://rawgit.com/

RawGit has reached the end of its useful life
October 8, 2018

RawGit is now in a sunset phase and will soon shut down. It's been a fun five years, but all things must end.

GitHub repositories that served content through RawGit within the last month will continue to be served until at least October of 2019. URLs for other repositories are no longer being served.

If you're currently using RawGit, please stop using it as soon as you can.
...

Those parties utilizing this MITM CDN may want to adjust their .user.js soon.

OUJS Admin

A notable, and noticed, change:

https://github.com/blog/all.atom seems to have changed domain names... so if you are following pay a visit to https://github.blog/ for some of the current feeds.

As of right now the "All" category seems to be broken. e.g. at https://github.blog/all.atom

Please use these instead:

--- /scripts/FreeStyler/linuxmint.com.ru_improvements/source@0.0.3+ebac760
+++ /scripts/FreeStyler/linuxmint.com.ru_improvements/source
@@ -9,8 +9,8 @@
 // @supportURL   mailto:zanygamer@gmail.com
 // @include      *linuxmint.com.ru/
 // @match        *linuxmint.com.ru/
-// @updateURL    https://openuserjs.org/meta/FreeStyler/linuxmint.ru.user.js
-// @downloadURL  https://openuserjs.org/install/FreeStyler/linuxmint.ru.user.js
+// @updateURL    https://openuserjs.org/meta/FreeStyler/linuxmint.com.ru_improvements.meta.js
+// @downloadURL  https://openuserjs.org/install/FreeStyler/linuxmint.com.ru_improvements.user.js
 // @grant        none
 // @run-at       document-end
 // @require      https://cdnjs.cloudflare.com/ajax/libs/jquery/3.2.1/jquery.min.js

OUJS Admin

Good sure didn't. YAY! Been a while since I've tested this mode of the site out.

Did I RO discussion/comments?

Test

Test Chromium update

Re: @x2000:

a fork of this

Please use the "Submit Code as Fork" on the scripts Source Code page. Had you not mentioned it here and we received a flag of not using this fork mechanism (or seen it ourselves) we would be within the guidelines of the TOS to terminate your account.

I have manually fixed it. Please don't repeat however you did it the first time again. You must use the Submit Code as Fork option available on everyones Source Code page. All you needed to do was to change the @name before you click it to modify it for your account. Then it creates the fork on your account. Then you do the actual changes for FLAC support to the code base. It's not that difficult to figure out.

Thanks for your cooperation,
OUJS Admin

Re: @dlupu:

I'm collaborating with a colleague on several scripts and found it would be easier to create in advance empty scripts.

The moment you change @name the system will spawn off a new script at a different URL compounding the issue further. So unless I'm missing your point there's not an advantage to doing that methodology. Most of the .user.js engines have a template manager as well.

We don't mind testing within reason.

Re: @channelstage:

Can I download the following like site ?

Please rephrase the question for everyone here as it is unclear (at least to me). That link is currently a ~2 hour video of a fireplace and some other audio stream which doesn't appear to work.