Replies: 1 comment
-
|
Thank you for your suggestion, but we are not currently planning to add default userscript. If we do add any, it would only be one with very basic userscript. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Greetings.
I think, that it would be beneficial to have a routine (i.e. "default", so called) set of extensions upon first installation.
These extensions will be disabled, and the users will have to manuallly activate them.
Doing so, would allow to demonstrate the capabilities of this software, which would subsequently influence more people to utilize Userscript.
Some extensions that may be qualified are these.
https://greasyfork.org/scripts/465933-cleanurls
https://greasyfork.org/scripts/465932-newspaper
https://greasyfork.org/scripts/465953-enforce-https (Maybe there are better than this one)
https://greasyfork.org/scripts/465950-no-referrer
https://greasyfork.org/en/scripts/490282-ruffle-flash-player
https://openuserjs.org/scripts/navchandar/Open_Current_Tab_via_Web_Archive
I wrote those to browsers that thankfully do not have "webextensions", such as QuteBrowser, Falkon and Otter Browser.
Beta Was this translation helpful? Give feedback.
All reactions