Marti Admin

Re: @3jameo3:

I might try my hand in creating a python code to compare 2 different codes in the future.

Seriously doubt the browser itself can handle this... but I also haven't looked to see if there is a runtime client side. Since this would need to be DOM side it would need to be JavaScript. I seem to remember there's some upcoming compiled language but haven't relooked into it (or remembered it's name too ;).

In short this needs to be pure JavaScript and on the client side... perhaps with some optional workers to utilize more cores. The one I twiddled with did too much. We just need the text and not the prettyfication which is probably what slowed it down to a halt.

Anywho... GH is a better place to discuss this rather than here. ;)


Re: @3jameo3:

Sounds like a good amount of interesting updates to the site will be coming.

Time permitting... just tested the "top" diff type package and it locked up my browser with a and b sources. I have a pretty hefty multi-core machine too so that particular package probably isn't going to happen for everyone.

I look forward to that as I have little to no Linux knowledge.

Hope I've improved it a little bit... see the FAQ section. With Windows it's best to use git-scm. All others like it are getting older, and perhaps a bit overly bulky.

Anyhow... sorry about the intervention... but maintaining integrity of the forums here. You should see what we get to remove sometimes. ;)


Re: @3jameo3:

The prior changes have been diffed as follows:

  • a.user.js is @eileen12 's @version of 3.22+0552534
  • b.user.js is your original full script source diff'ed to what full source was at this comment
  • c.user.js is your original full script source diff'ed from b.user.js to what full source was at this comment

I don't understand the code change part of the FAQ

I will try to update it a little bit for Windows users since it's mainly for git-scm. I diffed the prior comments using Linux diff -u command after downloading all the sources and then diffing a to b, then b to c. As you can see it's intensely clearer. I left your original "this" to "that" change comparisons. I've done this myself.

I also need to find a DOM diff package (or make one) that we can stick next to beautify/wrap of @eileen12 's source code and then you can choose your method of presentation by dropping in your changes without forking (but forking is still the preferred at this time since it makes way shorter discussions and doesn't open up a security issue... you can delete a fork at a later date if @eileen12 adopts the changes). It's on my long list of things to add to the site. :)


Re: @3jameo3:

@3jameeo3

I realize you are trying to help out here but please don't post entire scripts. That is what forking is for. Then you can refer to it on your fork. Just rename the @version to something unique.

If you need to show differences please utilize this FAQ.

Thank you for your cooperation,
OUJS Admin



Should be complete... had to reimport an old script for some reason.


Re: @3jameo3:

TypeError: $(...).ready is not a function

This portion usually refers to jQuery being absent.


Refactoring for non-primary @license now (ex. CC)... please be patient.




Unfortunately that maintainer has gone rogue so this will be delayed again pending a more secured dependency... will try again with at least one PR and if he is a team player he'll do the right thing. :)


Re: @Marti:

Is there some way to specify "GPL-3.0-or-later"

This should be coming soon pending a PR upstream and some final rechecks.

Please reread the prior Re for applicable specifics. I will notify here when things are moving forward.


Re: @gobub:

copy paste didnt work for some reason

That would be user error. Please use a single pair of code back-ticks or a code fence which is three backticks on their own lines (See this FAQ). Your prior posts have been fixed with these. You can always use the Preview button to ensure it is what you want to post.

Thanks,
OUJS Admin



Re: @y-less:

Ahh you must have hit the GH cache limit... if you commit too many at once the raw data isn't updated... it's part of their rate limiting.





Any time you change @name it will spin off a new script instead of updating your old one. Please pick and stick with the same @name.

We currently index the scripts homepage so you really don't need to put too much into @name and @description. e.g. if you put supercalifragilistic in your scripts homepage via "Edit Script Info" and someone searches on that they will find you even if it's not in @name and @description. You can change @description all you want but @name needs to be more consistent especially for people installing it. If you continually change @name no-one will know there's an update.

Thank you for addressing this.


Please do not upload the same script and just change the title.

I will give you a few hours to fix this in your scripts. If you do not respond here and do not do this you will be removed.

OUJS Admin



USO based icons are 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.

This could use a fix at your earliest convenience.


USO based icons are 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.

This could use a fix at your earliest convenience.


One other note... if you have an issue with a script not installing please let the script Author know just like I have. I will not be doing this frequently from GM development to an OUJS issue.

If you have an issue with a 404 it is most likely been deleted by the Author or removed by us for a TOS violation. If you are unsure please ask us! We are more than willing to investigate.


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.