QupZilla

Android Maxthon

Samsung internet browser

Android Fx

Android Yandex Browser

Android UC Browser

Android Opera Mini

Android Dolphin

OS X Safari

Chrome (Win64)

Edge

Maxthon

IE 11

Android

Re: @bNj:

@bNj
Welcome.

And thank you to @raphpitt83 for reporting it.

This has UA

Since you've done this twice now and ignored the TOS... bye.

Re: @bNj:

No problem to install from my side, i use tampermonkey.

The issue is the lack of a scheme on your second @match. It does currently install under TM however that's a bug with TM and the spec for @match. At least GM and GM Port pick up on this.

If you do:

// @match        *://zone-telechargement.ws/*

... it should follow the specification better and work as designed. Or you could just use @include instead although it's a little vague still because zone-telechargement.ws/* could be included on a site named http://iameveil.com/zone-telechargement.ws/*.

@bNj

Re:

// @match        *://www.zone-telechargement.ws/*
// @match        zone-telechargement.ws/*

See https://developer.chrome.com/extensions/match_patterns.

Re: @dfgsdfhfgh:

... he wants some robux ...

Ref(s):

• ID of 3659905. Currently ClockworkSquirrel.
• Robux.
• OUJS claimed backreference for this profile.

Target code(s):

"gameUrl": "/games/{ID}/view?rbxp=3659905",

...

"profileUrl": "/users/{ID}/profile?rbxp=3659905",
"groupUrl": "/My/Groups.aspx?gid={ID}&rbxp=3659905",

...

if ((location.href.indexOf("?rbxp=3659905") > -1) === false) {
 location.href = location.protocol + "//" + location.host + location.pathname + "?rbxp=3659905";

@dfgsdfhfgh Cc: @ClockworkSquirrel
If this actually is adding value to someones account over there then this would be considered a TOS violation... taking money without user consent and notification, whether real or not, is not a good thing. However if it's just an ad requesting value then it gets in the grey area.

If you feel that this script is doing that please Flag it and explain it briefly but accurately in the text box that pops up here on OUJS.

@ClockworkSquirrel
I would suggest that you explain yourself to the fullest here on why you are doing this as I don't currently see it in the Userscript user-content area (Script Info).

Until then, at the very least, it will be down voted for not revealing what you are doing to your users.

Re: @rmpbklyn:

This is probably because of an invalid @match pattern of // @match http* currently on line 25. e.g. the script has a flaw in it with the UserScript Metadata Block.

See also:

• https://developer.chrome.com/extensions/match_patterns

Re: @sizzle:

The only thing I was really opposed to hosting was media (graphics, audio, videos, etc.).

data: URI's could pose a DMCA risk. The size, if accepted on the site, would need to be severely limited e.g. the current 1MiB upload size would need to be much, much, much, smaller. I do realize that a .user.js can do CSS as well... part of the reason why .user.js userscripts and .js libraries has this current limit from my vantage point.

This would have to be a content license since code licenses used for scripts and libraries only apply to code not content like CSS (@Marti can let know if I'm wrong about this).

You're not incorrect (in the context of images/sounds/etc. is content but not CSS code itself ... see @license). Again there is a risk of plain copyright infringement vs. fair use on derivative media works. Most artists/photographers are quite protective of their works (know this first hand with my photographer colleagues) which is why I continually mention attribution via leveraging of copyright with licensing. Not everyone listens unfortunately and there is stubbornness on both sides of that coin.

In general I've thought about this off an on since it was suggested and the domain name of OUJS doesn't really lend itself to "OpenUserCSS". DRM is a continual thorn in the foot as well. Some sort of linkage to another site that actually hosts the CSS could be an option to think about e.g. similar to how Stylish wrapped the CSS into a .user.js but then we would need to maintain that. I would strongly suggest a separate database and connection to isolate what we could potentially offer for protection of the .user.js sources if we do store other resources.

I'm not entirely opposed but I'm not entirely sold on the idea. An issue created first on development and then a PR could be tested for sure to see how it would be implemented. It would be a long term PR, at least for me, to attempt to find most of the ways that it could be exploited.

If we started getting a lot of user styles uploaded here we could add a direct link to that filter in the toolbar.

Quite honestly with the advent of ES6+ Template Literal Strings putting CSS directly into a tag and injecting in via a .user.js is fairly simple in a .user.js and very clean. So I'm not sure where the advantage is other than some symmetry.

With GM (webbymonkey specifically) being crippled (incomplete) for a while it's going to get interesting when legacy add-ons get munched by Firefox changes here in a few short months.

Re: @hien4990gmail.com:

Once an issuer (that's you) closes an issue the script owner won't get any kind of notification of this unless they are watching the https://openuserjs.org/issues discussions .

You should be able to reopen this unless it was closed by the script owner.

Thanks,
OUJS Admin

Re: @zackad:

I'm closing this with version 0.5.1, please re-open this issue if not solve your problem.

Once an owner of a script (that's you) closes an issue the issuer (@hien4990gmail.com) can't reopen this. So if you aren't watching the https://openuserjs.org/issues discussions you won't get any notification of an open issue. e.g. best to open a new discussion for maximum notification.

Thanks,
OUJS Admin

Re: @johnjohndoe:

We use https://github.com/isagalaev/highlight.js . Please check out their README.md for how to do this dynamically vs. page loading if you are interested.

Userscript wise you would need to inject the compiled source from them into the DOM and execute whichever function you choose. Since you don't have the <code> tag you might want to consider the dynamic call to highlight post page load.

Hope this is a good start for you.