New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Trusted sites should be able to detect Greasemonkey is installed #1964
Comments
But you can detect that Greasemonkey is instaled: |
Ticket #1787 will probably get resolved some day, but I never considered it high priority. This is more or less the exact opposite request. |
Being able to tell what is "trusted" and especially doing so over time seems like a dangerous/complex thing. |
I was just thinking user script hosting sites like Greasy Fork, openuserjs, etc. In my idea, "trusted" just means "trusted to know that Greasemonkey is installed" and not trusted in other ways. The purpose is solely to smooth out the user script installation process. In the case that I or someone else who was trusted turns to the dark side, what could we do to abuse the trust? Block access to the site if Greasemonkey is installed? That'd be madness for a site that hosts user scripts... |
Sorry to revive this but.... |
On Greasy Fork (and pretty much any other script hosting site) there's a big Install button to let people install scripts. Works great if you have Greasemonkey or other managers. If you're new to user scripts and don't have Greasemonkey, the Install button leads you to a page of code with no indication on what you're supposed to do with it.
What would be great is if Greasy Fork could detect that Greasemonkey is installed. If it is, Greasy Fork would have just the Install button. If not, Greasy Fork would have prominent text on the page telling the user what they need to do (but still include the Install button for clients that don't support the detection).
I realize that Greasemonkey tries to operate in stealth mode to prevent affected sites from taking countermeasures. This would have to operate on a whitelist basis.
The text was updated successfully, but these errors were encountered: