Marti Admin

Re: @jscher2000:

One feature at a time... watching/favoriting/liking or whatever terminology will be used will come eventually. Patience Sir Jefferson. :)


Re: @jscher2000:

This was already answered by me a while back. People might try it out... might not work for them for whatever reason without reporting it or liking it. IDK... may be referenced offsite somewhere too. You will never get 100% accurate stats. I test the meta routine daily with install counts as it's part of my Admin responsibilities. Older GMs don't support the request header. Shared IPs in (proxies) in foreign lands... dynamic IPs... short urls... the list goes on and on and on and on. :)



Please don't obfuscate your code. This is currently prohibited.

You and/or your script has become eligible for removal.

This is your only warning.


Please don't obfuscate your code. This is currently prohibited.

You and/or your script has become eligible for removal.


SeaMonkey (SM) users heads up for Greasemonkey Port (GM Port)

I had to cherry pick up to the current greasemonkey/greasemonkey@4ea165f and omit the following commits during testing:

Affected issue ticket is greasemonkey/greasemonkey#1937

Author reported Step to Reproduce (STR):

  • Installed the mentioned script there.
  • Visit a site that is included in that script currently
  • Reported error does not appear to be exhibited in SeaMonkey 2.26 and 2.26.1
  • Confirmation about Anthonys statement but using SeaMonkey of:

    Though I can't reproduce quite the error described.

What this may mean:

  • The current patch in those commits may be incorrect.
  • SeaMonkey release may need an update to match Firefox release code.
  • The great unknown e.g. something else missed.

What this ultimately means since I am the remaining maintainer of GM Port, since Philip seems to have gone off the GM map, is that rather than pollute the slavestep branch with a strong veer of a major GM API method... I am going to wait and see what happens. It is possible to cherry pick all the other commits for 2.1beta1 and they seem to check out okay in SeaMonkey.

Please remember to try things out in Firefox + Greasemonkey (optionally on SourceForge) and if they don't work report on GitHub GM. I am always paying attention for GM Port and will try, as much as possible, any clear STRs for SM.


Please don't obfuscate your code. This is currently prohibited.

You and/or your script has become eligible for removal.


Re: @TimidScript:

or does it only keep the latest version.

Latest version at this time.

How do you search on the forum

Not implemented at this time... but you can search individual comments... go to that Usernames page and click on Comments and you will see a search bar.


Please don't obfuscate your code. This is currently prohibited.

You and/or your script has become eligible for removal.



Please don't obfuscate your code. This is currently prohibited.

You and/or your script has become eligible for removal.





Re: @Quackmaster:

I don't wanna miss out on the GM_ functions.

If you are using @grant none then you probably won't have access to the GM_* functions. If you are in the Sandbox, by using any other @grant access right, you should have access to the GM API. Since I haven't had much time to examine this change, or test this, I can't with all certifiable accuracy confirm this... but this is how it looks to me especially with greasemonkey/greasemonkey@7031a32.



Re: @harakiwi:

Firefox isn't able to playback 1080p+ and the new 60fps videos w/o dropping up to 60% of the frames on a 300USD quadcore intel

What does your about:support say for Graphics acceleration?

Works fine for me but I'm also hyper-threaded which you omitted to mention in your issue here. That is an important thing for graphics acceleration especially with videos of that nature.

"A @require is missing (JSL).
Either you're not using the correct plug-in, or @require isn't working.
Please review the script's main page to see which browser & addon to use."

All assets (requires) appear to be available for me. Try, try again?


Perhaps GM is blocking it because of page scope?

Bad assumption. It's when page scripts are disallowed. You might want to note that in your user-content area that it requires page JavaScript to be enabled. ;)

I didn't have time to click through and read the Greasemonkey Wiki.

Make the time... It will make your presentation better for your script for other potential users. :)

I'd really like computers to do more work, and me to do less, so I wish everything would just work without needing 20 @ tags in the header!

Nothing is for free. You have to do the effort in order to achieve what is wanted.

90% of scripts don't even need those functions, and could safely run in page scope.

Another bad assumption and interesting making up of stats. Where is your empirical data on this? ;)

After this long post, you had better like my userscript!

LOL... well it works now which is an important thing... continuance is another. :)

Down with GM_*!

Never. The other child browsers still have some catching up to do. ;)

I don't think @description is OUJS-specific!

It's specially handled. If we list all of the keys we'll run out of page space. If you feel the need for an enhancement please make a single, refined, issue for it upstream on GH after searching first to see if it's already been reported.


Re: @cpasmoi:

i had to add -webkit. thanks you much

You are quite welcome. Glad that those exact links helped you find what you needed to do especially under "Browser Support". :)


Re: @joeytwiddle:

@grant GM_addStyle DONE (really, I have to do this now? :P )

Are you sure it is done right now? Yes you do need to. Sniffing ended. Your current version removed the requirement since you aren't using the API anymore.

If you think @version (and other tags) are very important then perhaps they should also be featured in the left-hand column.

They are and there is a nice link at the top to explain all of the metadata block. One just needs to read. :)

If you contribute changes on here, how could I get them back to Github?

Do it on GH... those will always overwrite what is here.

With its own "Issue tracker" isn't this site re-inventing the wheel

No everyone is on GH.

and violating DRY?

Love acronyms that almost no one uses in real life... what is that? ;)

These make scripting a nightmare, especially since 90% of scripts run in page-scope

Mine work just fine and Sandboxing has been around before your 90% came along. :)

Please give the latest version a try!

When I get back to my dev machine I'll give it a whirl. Thanks



Heya joeytwiddle... I thought I'd give your script a whirl but there seems to be some issues with it currently.

  • You don't currently define @version so automatic updating won't ever occur for anyone.
  • You don't currently define @grant GM_addStyle so the script fails in Greasemonkey 2.0 to run at all.
  • In the error console I get a $ not defined... not sure if you are using jQuery or something else... so possibly the @require is missing? Since I can't guess on what you are using I can't even assist with any further suggestions.
  • It would awesome if you could use some of the OpenUserJs.org supported metadata block keys found here and also referenced currently in the far left pane when you add a script on this site.

Thanks and hope to see this come to fruition. :)


Re: @vBm:

I'm wondering if there is a dedicated IRC channel for OUJS maybe ?

No. I really don't have time to maintain the necessary bot requirements for IRC and pay attention to text scrolling across the screen prolificly... you can, of course with all irc:, make an unofficial one between whomever wants to join.

Site issue tickets are best to be submitted to the site GH issues though.


Microsoft (M$) is at it again... instead of admitting that closed source has malware in it, in which you agree not to reverse engineer otherwise you would see it... they've decided to attack everyone else.

No-IP’s Formal Statement on Microsoft Takedown

This applies to any script that is using usoCheckup... use dune.net, preferably on the SSL channel, or just remove it from your metadata block altogether... granted this isn't USO but there are some scripts still lurking around that are using the redirectme.net and that's my service for the redirect.


Re: @JRI:

Love this! Great to have a new perspective added to the fold. Welcome aboard. :)