Unless you have a disability, I can't imagine "needing" an extension besides uBlock Origin. What the heck are you doing with your browser?
Firefox
A place to discuss the news and latest developments on the open-source browser Firefox
Bitwarden Singlepage Video downloader Forest and many many more! Were you trying to be funny?
Bitwarden is on FF, as are various video downloaders. Guessing from the title, equivalents of Singlepage. No idea what Forest or the others do, but a search by functionality may turf something up.
@jtk @Subject6051 Have you tried mouse gestures? Once you got used to them, you don't want to live without them.
#keyboardmasterrace lol
this is robbery, show me your mouse page gestures. You don't have the right to remain silent.
PS: I know they might be private, but give me examples of what you use it for
@Subject6051 If you want, I can send you my Gesturefy backup JSON file.
Examples are: scroll top, scroll bottom, go forward, go back, switch to left tab, switch to right tab, refresh page, close page, open a link in a new tab ... these should be the ones I use most often.
that would be very helpful! lemme dm!
Depends on your aptitude & what you want the extensions to do (some being much more complex than others), but most people can learn the skills needed.
You'll only know if you try, but even if you can't manage to write exactly what you want, you'll learn a lot on the way.
There are great resources out there, and forums where you can seek help from more experienced people.
There's also Orion browser, which isn't FOSS, but which takes both Firefox & Chromium extensions.
Orion browser, which isn’t FOSS
Edit: I don't think supporting both chrome and firefox extensions is a major selling point anymore. I don't know a single extension which is available on FF which isn't available on Chrome.
Aye, but OP wants extensions which are on Chrome but which are not on Firefox.
it's not terribly difficult for a developer of a chrome addon to also support firefox, as they both use webextensions (with a few differences--more once chrome fully drops manifest v2 in their effort to neuter adblockers), so the first step would be simply to ask them to.
start with an open source example and continue
Not sure what the question is -- are you looking to port extensions over yourself, or are you just exclaiming, "it can't be so hard, so why won't someone do it!".
There's plenty of documentation over at MDN as to writing extensions, writing cross-browser extensions, porting mv2 firefox extensions over to mv3, the differences between Firefox's mv3 implementation, and that found in Chrome, etc. etc. etc. The following are good starting points: https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions & https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/Build_a_cross_browser_extension
For ground-level, basic stuff (managing a popup, communicating between popup & a 'background' script, between content loaded on the browser & your scripts, managing a context menu, etc.) writing an extension is straightforward once you develop some degree of understanding of the sometimes convoluted paths the data needs to take, the permissions you need to have in order to pass messages through, etc. Larger extensions are full fledged applications in their own right, though, so tackling them introduces difficulties of a different order of magnitude.
The Falkon browser is extensible (in its own way) through QML; and the Nyxt browser is extensible in common lisp. These aren't 'webextensions' in the precise sense of the term, though they could be just as useful. I wrote a basic bookmark manager that I use mainly on Firefox; but I ported its core functionality (just send the current page's title, url, & selections from the <head>
tag over to my database (postgresql via the postgrest http frontend, to which I just make a fetch request)) to QML, and it was pretty straightforward. Falkon is based on Qt's QtWebEngine, which is Chromium-based; Nyxt is based on WebKit.
edit: There's also luakit and qutebrowser . The former is extensible via lua 5.1 scripts, the latter, python; there isn't a wealth of documentation & examples, though (at least there wasn't last time I checked) so the API can be a bit of a mystery. Luakit as webkit as its engine, qutebrowser is built on QtWebEngine just like Falkon.
I can't help you with your problem, just wanted to note that Firefox is not the only non-chrome browser out there. The big one is Safari, which is it's own thing based on the Webkit rendering engine. But there are others aswell. Iirc the standard browser that comes with GNOME is also based on Webkit, and there are a few Firefox forks (like the previously mentioned Waterfox or the Mullvad Browser) out there.