Are you sure you want to go to an external site to donate a monetary value?
WARNING: Some countries laws may supersede the payment processors policy such as the GDPR and PayPal. While it is highly appreciated to donate, please check with your countries privacy and identity laws regarding privacy of information first. Use at your utmost discretion.
You've been given a chance to remedy this situation. Please document fully on your script description exactly what you are liking automatically.
Failure to do so may result in being barrred from this site.
You've been given a chance to remedy this situation. Please document full on your script description exactly what you are liking automatically.
Failure to do so may result in being barrred from this site.
You've been given a chance to remedy this situation. Please document full on your script description exactly what you are liking automatically.
Failure to do so may result in being barrred from this site.
You've been given a chance to remedy this situation. Please document full on your script description exactly what you are liking automatically.
Failure to do so may result in being barrred from this site.
Please don't obfuscate your code. This is currently prohibited.
Please don't obfuscate your code. This is currently prohibited.
Alright everyone... give it a shot now! :)
Created #120
@trespassersW
I assume that you started out without a
@namespace
and then added one in.@jehan
All your scripts currently don't have
@namespace
.Working on the issue upstream. Thanks for your patience.
Any better today?
Yet another one... testing UTF
We are here therefor we are not there.
Sorry about the late reply... been busy reconfiguring this system. Still have a bit more to redo too. heh.
Yes... right before every header including
Welcome
... it's a little bluei
circle... usually used for information.Maybe Chrome will let me download it on Win7 today... I'll give it a shot there shortly.
Well the whole point of that script is that I pasted into the online editor. The uploaded version is a different one from here.
I really don't know what to say. Did I miss your answer to the question I asked?
Third time perhaps is the charm? (Just changed it to include a space at the beginning because I added the icon though... so the 2nd time posting here did work ;)
this script header
I can see markdown is going to be an issue with that script... I'll just put in the url without trying to abstract it.
https://openuserjs.org/scripts/marti/httplocalhost.localdomain/RFC_2606§3_-_Hello,_World!_(pasted)#anchor-welcome
Tried in a clean profile to rule out the obvious?
I just added a welcome header to this script to you!
Welcome personally btw. :)
Other systems count replies after the initial posts. ;)
Correct however in GM 1.16beta5+ it uses a header so if the server recognizes it it will return just the metadata block. See my announcement here.
That's not all they remove. Changing legally protected scripts can be a sticky issue to deal with so it's best not to do it. If you don't type English posts they'll ban you from the site. I thought that was rather prejudicial when I read it in their terms of use... and there is more like this.
I did not know that about that sites client side scripting... good to know and thank you for that. I don't particularly have favor for equazcions style of accusations so I haven't had much of a chance to visit his pre-fabricated site yet.
I look at this way currently... I have an external repo where I keep my code and content and have a presentational website, such as OUJS here, where I can work in a more integrated community than just a standard SCM offers.
I had to think about the logical human interaction on this one quite a bit and came to a few conclusions:
So in conclusion I will support this Request for Enhancement (RFE)... however you need to do it on the upstream issue tracker first. There are a few UI changes that may be coming through at some point so we'll need to patiently wait on polishing finishes such as this.
I usually don't release beta cross-streams of Greasemonkey (GM) before everyone at Addons Mozilla.Org (AMO) has a chance to fully review upstream changes but it seems to be gaining the necessity to do this at this time and does currently apply to the shop here at OUJS.
We will try Anthonys method of checking for updates. The way I am understanding the methodology currently is that it tries to pick the
.meta.js
first of any site... then if it fails, ever, it will always use full script source with.user.js
until changed in the config.xml... unless a hosting service utilizes the request header for meta retrieval. This procedure can, of course, still be overridden with@updateURL
and@downloadURL
An additional fix in these also include the full fix for greasemonkey/greasemonkey#1884 and greasemonkey/greasemonkey#1924. Someone might want to tell them. ;)
File Repos:
Oh and...
Show inline Versions and Diffs on Source Code page
on otherwise you won't get the sha1/date if ticked.@jscher2000
At minimum if you want to keep your diffs you can use this procedure:
Best to omit these if this is your permanent and only home here. If you have an external repository and want it to update from there by all means add it in... I would suggest that you create a .meta.js on that repository though. OUJS doesn't need this since GM 1.15+ sends the request header.
See also:
Created upstream#101 and upstream#100
n/m on the GH url request ... found it.
I don't see anything unusual that I haven't tried out already but I'll keep looking. :)
Just retried it on my repository and it doesn't seem to be exhibiting this behavior for me. Try a clean profile to rule out any Add-on/Extension. Is there a specific GH url for your script that I can inspect the source to confirm with some of the recent changes for UTF-8 handling and anything else I can think of?
Not currently but this site is relatively young... so patience? :)
Possibly but sizzle will need to be the one that needs to answer this more accurately on his next visit to this area on OUJS.
You may also create a RFE on the GH issue tracker if it's not already in the existing issues as an improvement/enhancement/etc.
Hmmm haven't seen this one yet. Is your script here the one that you are working with? e.g. Did you get it successfully on here but with an error afterwards? Was the socket error a white page with black text or did it have some of OUJS showing like the "Scripts", "Groups", "Beggar's Corner", etc. showing through or something else?