Re: @deFco247:

Until @TimidScript gets around here you can try changing this line back to the original and that should alleviate the issue.

I just spent a few hours retesting Greasemonkey Port for SeaMonkey (SM) due to your concern... although it is unclear if janekptacijarabaci did something correctly for SM so it was omitted for integrity... but if that fork works in PM go for it. :)

@TimidScript

So my educated guess is that your current script, which currently uses cloneInto, is no longer supported from the removal at greasemonkey/greasemonkey@7e2eafc#diff-eed5161116c8f3737a46e5dd4ac7fe8fL65.

As I said earlier it's getting kind of messy handling the Fx changes to what is privileged for Add-ons and what isn't. Not quite sure yet on why PM is saying Cu.cloneInto is failing here in the GM code unless Cu is out of scope in PM for some reason.

Refs:

• greasemonkey/greasemonkey#2070

@TimidScript

Usually cloneInto is done with unsafeWindow for most use cases. I decided to retest this a bit with RFC 2606§3 - GM_listValues Unit Test and it seems to work without cloneInto in PM (and Fx 41.0.1 distro build).

Refs:

• TimidScript/UserScripts@bb7d7b5#diff-a6912c0fbdd75af1506a2b7fbac9ec22
• greasemonkey/greasemonkey@12ec962...9c19186 (diff between GM 3.4.1 and 3.5.0)
• greasemonkey/greasemonkey#2033

Re: @deFco247:

Greasemonkey versions ... and 3.5

Btw GM 3.5 with PM 25.7.3 has this in the console and kills all Userscripts:

[12:50:20.996] TypeError: Cu.cloneInto is not a function @ chrome://greasemonkey-modules/content/sandbox.js:138

... so it's not getting exported to the sandbox e.g. this particular instance is a GM issue. From observation the primary maintainer of GM is a bit shaky on PM support so be super nice if you report this... he could drop support for this.

Re: @deFco247:

Try window.cloneInto... as I'm not always in Pale Moon I seem to recall this was one of the messages I read on upstream but not sure where at this time. I do know that GM_listValues is an issue with some other ports because it returns a complex object and that is restricted in sandboxed environments... and Moz keeps changing this. Please let this author know if that works for you. TIA.

Re: @Haris:

Managing Userscripts

Forgot to say all existing flags, save for a couple, have been cleared... time to start anew with why something needs to be flagged.

Ciao for now.

Flagging now has a reason field.

Please be courteous and remember typically when the flags hit critical Moderators and above should see that flagged item.

If any user is found to be abusing the flagging system their account may be eligible for removal... this includes bogus reports... so play nice please. :)

Everyone is encouraged to use the peer review system (voting up and voting down) and create a Script discussion Issue first. Site moderation is typically for dangerous scripts and not bugged scripts that may or may not work. If you find something that violates the TOS by all means please flag it and fill in a brief reason why you think it should be moderated.

Thanks,
OUJS Admin

Re: @memnoch:

@memnoch
Is this still the case for you?

Apologies for not getting back sooner but I didn't have any possibilities.

Maintenance complete... approximate downtime was 8 minutes. Until the next time... Thanks guys and gals. :)

The boat leaving for the mainland leaves in five minutes. Drop what you are doing...

See you all on the other side soon.

It's that time again... announcement for later this evening... there is some scheduled maintenance. Expected downtime should be approximately 15 to 30 minutes... perhaps shorter. The usual doing it as close to the end of day EST today is planned.

Patience is a virtue. Thanks. :)

Base64 encoding isn't permitted on a script element text... please correct this within the next 24 hours or your script and your account will be eligible for removal.

Thanks,
OUJS Admin

Please reread the Terms of Service specifically in this section.

All scripts published and authors here must meet this requirement. e.g. everything here is open source and freely available to fork... you received your attribution on this scripts homepage under Fork History. Now, if you see that someone did not fork it properly e.g. flat out copied with no site attribution we could fix that.

Thanks,
OUJS Admin

So what you meant to say is that you ignored the caution notice about using your email when you signed up here. ;) The username you entered on that page is sanitized for use not "screwed up". :P

A few things to remember:

• Read everything first and this includes the Terms of Service.
• Your newest account has been merged into this old one with a rename and setting as google as the default authorization.
• Your newest account was deleted in order to preserve your tenure here and your activity.

Luckily I was able to detect the newest username was you... but if I wasn't able you would be out of luck for ignoring the caution. So in short you should be good to go. Re-sign in.

Refs:

• #233

Re: @Arthur-BDR:

I don't know where the link to the problem image disappeared to,...

It's there indicated by your alt text but the server at dropbox has it return a html page with the image in it. e.g. it's a rewrite on the final target to handle it as a web page instead of an image... then there is a deep image link. Run into that a few times myself.

Server maintenance complete. Total downtime was approximately four (4) minutes. :) Appears the new back end is working as expected so far. There will be more at a later date but that will be announced as usual.

Near Oct 3, 2015 there is some server maintenance scheduled. Approximate down time should be less than one hour... perhaps shorter on the optimistic side. Again... I will try to do this as late as I can in the evening EST.

Thanks for your continued patience. :)

WTFPL is not on the OSI list.

Please dual license with a Code License (Usually it's MIT for the least protective) and you'll be able to keep your script here.

Further refs:

• http://opensource.org/minutes20090304 (Search for WTFPL)

Thanks

WTFPL is not on the OSI list.

Please dual license with a Code License (Usually it's MIT for the least protective) and you'll be able to keep your script here.

Further refs:

• http://opensource.org/minutes20090304 (Search for WTFPL)

Thanks

Re: @Limnic:

just wondering if peoples' installs are broken because the script was remade.

Provided @name is still the same (casing, whitespace and characters) it should be fine. OUJS doesn't have the same issue that numeric indexed sites have. We use your modified username/scriptname instead of treating you or your scripts as a number. :) Only issue may be in the .user.js engines with using full source for update checks but that is negligible.

btw I'll be moving the comments in this discussion later this evening to the proper discussion announcement to keep things on-topic. (Completed move)

Re: @Limnic:

And one response to your comment in the cache here. :)

Re: @Limnic:

uploaded script

And here is the source (from Aug 23, 2015) for that script e.g. just a metadata block pulling from your GH io page.

Re: @Limnic:

loss of accounts was not mentioned.

Yes it was and even here on production too. You created your account on August 14th, 2015 You are back and you will need to restore what you wanted here. Goo's cache is here :)

my uploaded scripts are also gone.

I only see one in the cache named Hugelol keyboard navigator but that depends on the cache period visitation.