Is there a specific reason that projects like these seemingly often are Chrome only. I use Firefox and I feel «left out» on a near weekly basis.
As for the extension, it doesn't depend on anything other than hackernews and the search api, so a port should be easy.
Update: It's now available as a userscript, tested on Firefox with Tampermonkey
That said, from the two (the other one being Safari), Firefox is much easier to port the extension to and there's even webextension-polyfill that gets you >95% of the way there (most of the time).
Is it? Has anyone in this thread tried this? (I have not.) https://developer.apple.com/documentation/safariservices/saf...
To be more precise the last time I did this I had to: - Adjust cookie SameSite attribute (cookies didn't work properly otherwise) - Migrate back from MV3 to MV2 (Safari DevTools are really bad for MV3 for some reason and there were also other issues that didn't appear in MV2) - Adjust JS and CSS (some newer techniques were simply not supported in Safari)
Firefox didn't have any of those issues. On top of that, there's much more resources available online than there is for Safari - though, to be fair, it's mostly because its support for WebExtensions is newer and there aren't as many extensions for Safari. But, when you do find some resources you have to verify whether they're actually on the most recent standard - Web Extensions - since Safari supported multiple over the years, that have nothing to do with WE, and are very similarly named: Safari Extensions, Safari App Extensions, Safari Web Extensions
https://developer.apple.com/documentation/safariservices/saf...