greasemonkey/greasemonkey

GreaseMonkey vs ViolentMonkey

Closed this issue · 9 comments

stokito commented

Maybe this was answered somewhere but I didn't found.
Why the GreaseMonkey is still doesn't support Chrome?
The TamperMonkey is closed source and there is yet another one ViolentMonkey created.
This is so confusing

erosman commented

General Information:
At the moment, Chrome store doesn't accept manifest V2 extensions and manifest V3 doesn't support userscripts YET.

See also: Userscript managers support

  • 👍2
Vampire commented

Since when is TamperMonkey closed source?
It is GPLv3 licensed: https://github.com/Tampermonkey/tampermonkey

  • 👎2
Vampire commented

And how did TamperMonkey then make it into the Chrome store if it does not allow manifest V2 extensions?
https://github.com/Tampermonkey/tampermonkey/blob/master/build_sys/manifest.json.google.com#L2

bunglegrind commented

Since when is TamperMonkey closed source?

5 june 2018, I suppose...maybe 6 june. well, whatever...it's written in the readme

Vampire commented

Oh, sorry, missed that

erosman commented

And how did TamperMonkey then make it into the Chrome store if it does not allow manifest V2 extensions? https://github.com/Tampermonkey/tampermonkey/blob/master/build_sys/manifest.json.google.com#L2

Chrome store had stopped accepting new MV2 extensions. The ones already on store were supposed to covert to MV3 by Jan 2023 but the deadline was extended.

The transition of Chrome extensions to Manifest V3

There are two key dates for the phase-out:

  • January 17, 2022: New Manifest V2 extensions will no longer be accepted by the Chrome Web Store. Developers may still push updates to existing Manifest V2 extensions, but no new Manifest V2 items may be submitted.

  • January 2023: The Chrome browser will no longer run Manifest V2 extensions. Developers may no longer push updates to existing Manifest V2 extensions.

Chrome Extensions Manifest V2 support timeline - Chrome Developers

image

Since when is TamperMonkey closed source? It is GPLv3 licensed: https://github.com/Tampermonkey/tampermonkey

tampermonkey

This repository contains the source of the Tampermonkey extension up to version 2.9. All newer versions are distributed under a proprietary license.

Tampermonkey version 2.9 dated 2012-12-28
Tampermonkey current version 4.18.1

  • 👍1
sjehuda commented

Are you bound to voluntary regulations?

Are you even consider such regulations?

I'm not using Chrome, but I assume there's another store which you can use to host Greasemonkey.

I'm not using Android, but when I did use it (DivestOS), I exclusively used F-Droid as an app store.

Now, I use F-Droid when I launch Waydroid inside postmarketOS, but very rarely so.

Don't forget, that the company behide the store you mentioned in your comments above has banned call recording apps, so what type of a represntation does it want to give, especially with the moto of "do no evil"?

I'm asking again, are you bound to frivolous regulations?

I hope not.

To me, Greasemonkey and USO (userscripts.org) are the pioneers of what the web is today; I think they are the influencing projects on HTML5, CSS3 and the whole system of WebExtensions.

Greasemonkey is a serious business, hence I think that any regulation that limits the idea behind Greasemonkey or Greasemonkey itself, is likely not appropriate.

Moreover, albeit my userscript doesn't work with your project, my userscript Newspaper that implementats a native web feed reader that the red lizard has removed at the pressure of its advertiser clients, would not have been possible without Greasemonkey and USO.

Also @scriptcat, reportedly base on this project, is available on the repository (i.e. "store") in question. https://scriptcat.org

jelabarre59 commented

All the more reason NOT to use Google Chrome, AKA MSIE6-revisited (or anything Chromium-based)

sjehuda commented