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.

Marti, are there images on your page ?

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 blue i circle... usually used for information.

and in Chrome.

Maybe Chrome will let me download it on Win7 today... I'll give it a shot there shortly.

My suspicion is that Marti uploaded his script from localhost but I conversely have inserted my code in online editor.

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

confirmed.
I see no way to edit my script description.

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 comments after the initial posts.

Other systems count replies after the initial posts. ;)

• If there is no updateURL & downloadURL, GM logs the install URL as the downloadURL

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.

• GreasyFork intentionally removes updateURL & downloadURL from all scripts

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.

• MonkeyGuts seems to have adapted both (ie .meta.js?c & .user.js?c) (although the site is heavily dependant on client site scripting)

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 have seen a few scriptwriters that use github as their permanent private repository. I dont know how practical it is..but I have to find a permanent home

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.

View Source is a dead end..there is no back button or link to get back to the script's main page ie for install (have to use browser's back facility)

I had to think about the logical human interaction on this one quite a bit and came to a few conclusions:

• "It's too hard"... to use the back button in the browser... was the first thing that came to mind.
• "What if someone linked directly to the source page?"... then it could be kind of irritating.

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:

• SF Greasemonkey
• SF Greasemonkey Port

Oh and...

• Set 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:

• Load uso - Count Issues
• On the script homepage of USO enable archive mode in the preferences panel
• Then you can backup the sid.vid (scriptid/versionid) with the "download" link that shows up on the Source Code page. There are additional options to include the detected date stamp and the sha1 hash from the meta.js routine by hovering over the date first, where it retrieves the meta.js for that version, if enabled
• Create a repository on GH
• Write a shell script (or cmd for Windoze or use PowerShell) to commit each version into your local cloned repository... or you can do this manually.
• Push the local repository up to GH.
• Voila! ;) Easy as... well not exactly easy... but doable.

how would @updateURL & @downloadURL work here?

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:

• greasemonkey/greasemonkey#1824

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. :)

What I get is this http://imgur.com/yc58wBq each time I press the "find scripts in github"

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?

is there a way for me ... to change my username?

Not currently but this site is relatively young... so patience? :)

is there a way for ... (... you guys) to change my username?

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.

I was trying to add a script I have through github and for some reason it said to me that the socket was closed.

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?

If I click on "View Source" I can edit the script.
When I click on "Edit Mode" I get a 404.

Hmm well it appears that it's working for you now since your update is showing about 6 hours ago. The site may be tweaked in the back end so perhaps you ran into one of those times or perhaps some add-on/extension could have hindered you. IDK.

If it happens constantly let us know on GH with an issue and full steps to reproduce. Right now that has better exposure to the devs... this will eventually improve here. I usually check a few times a day in the Garage.

Mozilla/5.0 (X11; Linux x86_64; rv:29.0) Gecko/20100101 Firefox/29.0

When I try and edit my script online, I get the message:
"The file or folder was not found."
Is anyone else having this problem?

At what point did you get this... "Edit mode", "Edit Source" or "Submit code"?

Unfortunately I can't replicate your issue. See my source that I just edited now with a comment back to your comment here.

That way when someone starts an off-topic discussion in one of the specific categories, we can move it to the general area.

Hey now... I'm still trying to find that user.js to do my laundry soon... I'm running out of clean clothes! ;)

question was about spacings in tables

Currently HTML special characters are supported in markdown. So try a web search for those. There are a lot of spaces out there. :) Took me quite some time to get my Compatibility Matrix converted to markdown without it getting foobarred... but it is a little brittle due to the limited nature of GH flavored markdown. Unfortunately for table creators mediawiki tables are usually much more powerful for table creation than is markdown... but markdown is pretty much safe to boot.

Can you give me a reason why you'd post a script to the site, add it to a group, and then somewhere down the line decide to remove it from that group?

Personally no... however publicly yes. I've sent many a message for people adding scripts to the wrong groups on USO and because it's single user managed they have to remove it. Moderators and higher should have the ability to "clean up" the groups if they see something awry.

See even I'm not perfect with markdown. LOL Must remember to do a double line break after > more often. ;)

I'm suggesting to at least add fields for configuring script meta block ( title/description/version/author ) and to show what's already in script after the upload.

While it's not 100% of them some of them are already shown and utilized. As far as a separate editable openuserjs.org (OUJS) meta I would recommend against this. The userscripts.org (USO) feature of separate metadata has an issue where spammers/malicious script writers rename their scripts even though they are malicious in nature e.g. they have the option of not being in sync with what is displayed... and I'd rather not see this happen here.

Another is issue is targeted image tracking. Even with USO I don't display those due to privacy concerns unless they are hosted on USOs native CDN url. Most of the stats can be achieved by the user content area of each script if someone really wants to add that ability. Take a look at my current profile (still working on generating this a bit).

In summary it's not that difficult to look at the script source and view the metadata block.

Could you automatically add .meta.js (as updateURL) and .user.js (as installURL) to script code
All of the user.js engines are smart enough to create these internally for those values from the script host site and should technically not need to be set for updating. Since the community is split over multiple sites right now it is best to leave those unaffected and let the author set them... e.g. it's not the responsibility of the hosting site to modify protected works nor should it ever be.

or at least show users created URLS.
Once I get into the full swing here, I or one of the other devs may be able to incorporate some of uso - Count Issues into the site or at the very least a oujs - Count Issues type derivative user script... obviously not named this since OUJS currently already has the issue count on the main script page.

Just an editorial note to you @Dexmaxter... to quote someone please use the > symbol at the beginning of the line instead of a header markdown tag to quote someone. Before my general greeting discussion gets too much more technical you are welcome to try creating your own discussion or preferably submit a request for enhancement (RFE) on the sites Issue Tracker where more of the devs will see it. :)