Greasy Fork

Greeting.

Whereas many utilize Greasemonkey to modify HTML content, it may be that not enough of us are aware that people could be identified by server-side analyses of the changes which our own Greasemonkey extensions are responsible to.

So, it might be good to add DOM as an anti-feature, in order to increase awareness, and encourage the use of functions "GM.notification", "GM.registerMenuCommand", "confirm", and "prompt", when possible.

Recently, this is what I did with these extensions, by removing DOM code in favour of native controllers.

https://greasyfork.org/scripts/490282-ruffle-flash-player (removed all)

https://greasyfork.org/scripts/465936-proxy-redirect (removed some)

https://greasyfork.org/scripts/562198-wiki-check (no dom)

Prehaps a positive "pro-feature" of "Stealth", instead.

FWIW, changes in DOM may be done inside a closed shadow root so the site will only see a faceless div element.

"Antifeature" is current defined as something done for the author's benefit rather than the user's. This sounds like something different, though I'm not sure what exactly you're referring to. Do you mean it contributes to browser fingerprinting?

@woxxom

Changes in DOM may be done inside a closed shadow root so the site will only see a faceless div element.

I did not know that.

@JasonBarnabe

Do you mean it contributes to browser fingerprinting?

Yes. Now, I think of "pro-feature", instead.

This seems too widespread and not bad enough to warrant any kind of warning on install. In addition, there would be nothing stopping a script from claiming to be good but not actually being good, and it would be difficult to detect automatically or manually.

It seems to me that this would be better served as something to emphasize in documentation. Or, potentially script managers could restrict access to the functions that cause the problem unless a specific meta key was present (or the other way around). If that was done, then Greasy Fork could detect that key and provide the info back to the users (if the script manager didn't already do so).