For posterity here's the current @icon url. e.g. http://s3.amazonaws.com/uso_ss/icon/417751/large.png?1395216776 ... click it and watch the raw XML message come up. Here are the HTTP headers:

http://s3.amazonaws.com/uso_ss/icon/417751/large.png?1395216776

GET /uso_ss/icon/417751/large.png?1395216776 HTTP/1.1
Host: s3.amazonaws.com
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 SeaMonkey/2.49.3
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-US,en;q=0.5
Accept-Encoding: gzip, deflate
DNT: 1
Connection: keep-alive
Upgrade-Insecure-Requests: 1

HTTP/1.1 403 Forbidden
x-amz-request-id: 52EE29EF5CC1A33D
x-amz-id-2: BN9VtLhdfeVpeGDkroFUD15hKDAjykUZMvuua6cIAzC91dSjHpe5XrgvnmEKotg/ukrEMSX929o=
Content-Type: application/xml
Transfer-Encoding: chunked
Date: Sun, 24 Jun 2018 09:43:48 GMT
Server: AmazonS3

... notice the 403 Forbidden on the response. This is what is hanging GM4. e.g. it's a fatal error that GM4 currently doesn't allow.

Currently at /scripts/lomacks/Reddit_Mouseover_Popup_Image_Viewer/source#Hb66f397L8 the Author is using a USO based icon that is no longer allowed e.g. 403 Forbidden. e.g. userscripts.org (USO) icons have been terminated by Jessie and/or AWS. This happened a few months back. That site of course has been gone for several years but USO AWS was still active until recently.

You, the Author, seem to have caused some commotion at greasemonkey/greasemonkey#2974. This is not an OUJS issue.

Both listed forks also have the same issue.

If someone feels like forking this script on OUJS (go to this scripts source code page, make the following changes... setting it's @license to MIT; then commenting out the @icon; and then clicking "Submit Code as Fork") that should make it acceptable for anyone to install the script.

Thanks for the look,
OUJS Admin

Please give Userscript Beginners HOWTO a quick read.

Admin closing.

Re: @HaYTo:

I presume you mean "thanks". Please make your issues clearer or they might be considered spam. If this is a "Thank you" please close it as well... ideally you should be up-voting the script on its homepage.

OUJS Admin

**REMINDER BUMP**

Re: @grenzionky:

That's what:

// @supportURL https://community.wanikani.com/t/userscript-kanjidamage-mnemonics-for-wanikani/18845

... in the UserScript metadata block is for.

Re: @ZugZwang:

... it says '$' is not defined...Can anybody help me with this?

jQuery is that. One of the @matches synchronously loads v2.1.1. Are you blocking their CDN for their custom jQuery?

I wonder why this script author didn't include a copy of jQuery of equivalent version in the UserScript metadata block in case it's removed or blocked. It's usually something like this:

// @require https://code.jquery.com/jquery-2.1.1.min.js

... and near the top of the script after the metadata blocks:

this.$ = this.jQuery = jQuery.noConflict(true);

I can sort of figure out what you are saying after rereading this a few dozen times.

uploadsmith.com have been fixed only Chrome can access to download files from these website

This is not true. I downloaded the file hosted there with Pale Moon.

i trying to change user agent to chrome in firefox but did't work

Try a clean profile in Firefox if you are having issues.

want to known how they block other browser is'nt chrome and have anyway to avoid block and access to download files without chrome ?

It is more likely a profile issue and/or your region where you live.

Most of this is beyond the scope of Userscripts.

Not a good idea to post download links to executables on a file sharing network. It has been sanitized. If you don't respond this will be considered signature spam. Not to mention the question is still a bit vague.

OUJS Admin

In relation to the GDPR announcement we've clarified some existing policies already in the OUJS eco-system and mirrored to the TOS.

Please give the Fair Use Rationale section a quick read. It's short and to the point.

There may be additional clarifications for those who can't seem to understand things.

Re: @3jameo3:

If you could be so kind as to fix the highlighting problem that would appreciated...

Done.

... as well as inform whoever is in charge of bugs about it I would appreciate it very much.

That would be you in this case. A code fence is only applied if the code is pasted by the user into the text area first; then you highlight what is code; and then tap the </> button... otherwise it's inline code single surrounded back ticks. I usually find it easier just to type the triple back tick and the language I'm using after. We mention this at this FAQ. While the inline code multiline isn't detrimental to policy it does make it DOM single node heavy and difficult to read and parse when it's validated (try a DOM inspection sometime on a multi-line code block vs a fence sometime ;)

Apologies for going off topic here but trying to be a little helpful without seeming too obtrusive. :)

Just a miscellaneous note regarding this discussion topic. One of the goals of the GDPR is "Vulnerability Assessment".

Since my years here that's just about all I've done. Occasionally there is a new feature put in when I can do it. Same goes with other contributors and collaborators.

The GDPR does not specify exact security requirements, but makes it clear that normal and usual security actions MUST be in place to be in compliance.

We are already doing this continually. Target sites in the EU must comply with this themselves. e.g. if there is an exploit exposed on a particular site it is their responsibility to fix it on their site... not ours. It is a good idea for those sites to accept help, sometimes in private if it merits it rather than publicly, to fix their vulnerabilities just as we do.

As we have "preached" many times before the Terms of Service and Privacy Policy are well formed and are the primary governing factor for most of our actions here. As I briefly stated earlier the integrity of OUJS will be maintained and there will not be any level of intimidation for demands accepted by any agent of the GDPR. Most of the time we don't even know who anyone is unless we're explicitly told and usually verified to the best of ability when needed.

Re: @3jameo3:
Guess you don't want syntax highlighting to assist the understanding for @twelve27 (or anyone else following) ... code fences are the ones that allow that not multi-line back ticks for inline code.

Re: @twelve27:

Fixed... and you thought no one was watching. ;) Try the Preview button out.

OUJS Admin

Basilisk

Re: @jscher2000:

It is done. Thank you again.

https://blog.github.com/2018-06-04-github-microsoft/

I have mixed concerns about this but time will tell especially if importing/syncing gets broken.

Webpack is obfuscation... post in the clear... this script is removed.

Please point your scripts @updateURL to the content from the Author Tools not the one that shows up in your .user.js engine template.

Thanks,
OUJS Admin

Re: @no_name:

素人でも分かるように解決策を教えていただきたいです。宜しくおねがいします。

Userscript Beginners HOWTO (Japanese translation)

Re: @chmorik:

Announcing your script is not necessary especially in three forums. We do that already in the script Userscripts list. Usually you would only do this sort of thing in this forum if someone requested it as a response... not proactively pushing it.

If you do that again you'll be removed for spamming. The other two are deleted. This is your only warning.

OUJS Admin

Re: @jscher2000:

Could I suggest truncating the IP addresses sent to Google Analytics?
...
See:

• https://support.google.com/analytics/answer/2763052

That sounds reasonable to me. This is a @sizzle exclusive thing so I'll have to run it by him. I never see that thing. I usually block it everywhere so I didn't even know this existed. Thanks mate! :)

While you may lose some precision in your geographic statistics, that level of detail may not be particularly relevant/useful anyway.

According to the image it's just one octet which again seems reasonable ... I am eventually going to be interested in how that reacts with IPv6 compatibility but that's probably way down the line.

Some of you may have heard about the EU laws regarding the GDPR. We already have very strict privacy policy so there may be a layer or more added.

Although jurisdiction is the United States for this server we are making an effort to incorporate some of the basics provided they do not compromise the integrity of OUJS.

1. First thing you will notice, so far, is that there is a check box saying you consent to the TOS and Privacy Policy. This is already the case for existing users however to humor the EU law on their end we've added it as a mandatory action.

2. If you are a GitHub user and are using the webhook you must pay us a visit and login to get that flag set on your account then the webhook will work as usual. If you don't pay us a visit the server will currently reject script updates.

It's simple so far... just check the box when logging in (preferably giving those documents a read too which you should have already done in the first place). Once this happens normal webhook operations will resume.

Apologies for any inconvenience including whatever else might be implemented later to participate.

OUJS Admin

Re: @DarKZonEDZ:

Please remember to do a code fence around your code blocks. An example exists at this FAQ. One has been added to your comment so it is readable.

Thank you,
OUJS Admin

It'd be great if there were some easily locatable documentation that spelled this all out.

Guess you didn't read the page here.