3 ms·

Though this isn’t actually about importing extensions that aren’t already in Firefox, the extension APIs are standardised enough that this is actually possible

Though this isn’t actually about importing extensions that aren’t already in Firefox, the extension APIs are standardised enough that this is actually possible a lot of the time. For example, I unpacked the Google Translate extension, made a single change to the manifest (I think so Firefox recognises it as supported) and loaded it into Firefox and it works perfectly! But it doesn’t work for everything, Amazon’s Send To Kindle extension didn’t work for me. It would be nice if there was an automated way to do this, I think there used to be. Maybe I can try to make something

Tijdreiziger 3y ago
Push to Kindle is a pretty nice solution for this https://www.pushtokindle.com/ https://www.pushtokindle.com/
Georgelemental 3y ago
There used to be https://github.com/Noitidart/Chrome-Store-Foxified https://github.com/Noitidart/Chrome-Store-Foxified, but it has been unmaintained for years
dotproto 3y ago
> the extension APIs are standardised enough that this is actually possible a lot of the time A bit off topic, but as a co-chair of the WebExtensions Community Group[1] (WECG) I'm a bit touchy about the calling WebExtensions "standardized." A few years back the Browser Extensions Community Group[2] created a spec for WebExtensions, but it never reached a state that we'd normally refer to as a web standard. (Technically W3C community groups can only produce "Reports" and these documents are not on the standards track.[3]) FWIW, I'm very bullish about specifying and (hopefully) standardizing the WebExtensions platform. I'm especially excited about having a good chunk of dedicated time to sit with browser folks at TPAC 2023[4] and try to work out some open questions about where we're going and how we're going to get there. [1]: https://github.com/w3c/webextensions/ https://github.com/w3c/webextensions/ [2]: https://browserext.github.io/ https://browserext.github.io/ [3]: https://www.w3.org/community/about/faq/ https://www.w3.org/community/about/faq/ [4]: https://www.w3.org/2023/09/TPAC/ https://www.w3.org/2023/09/TPAC/

Tijdreiziger 3y ago

Push to Kindle is a pretty nice solution for this https://www.pushtokindle.com/ https://www.pushtokindle.com/

Georgelemental 3y ago

There used to be https://github.com/Noitidart/Chrome-Store-Foxified https://github.com/Noitidart/Chrome-Store-Foxified, but it has been unmaintained for years

dotproto 3y ago

> the extension APIs are standardised enough that this is actually possible a lot of the time A bit off topic, but as a co-chair of the WebExtensions Community Group[1] (WECG) I'm a bit touchy about the calling WebExtensions "standardized." A few years back the Browser Extensions Community Group[2] created a spec for WebExtensions, but it never reached a state that we'd normally refer to as a web standard. (Technically W3C community groups can only produce "Reports" and these documents are not on the standards track.[3]) FWIW, I'm very bullish about specifying and (hopefully) standardizing the WebExtensions platform. I'm especially excited about having a good chunk of dedicated time to sit with browser folks at TPAC 2023[4] and try to work out some open questions about where we're going and how we're going to get there. [1]: https://github.com/w3c/webextensions/ https://github.com/w3c/webextensions/ [2]: https://browserext.github.io/ https://browserext.github.io/ [3]: https://www.w3.org/community/about/faq/ https://www.w3.org/community/about/faq/ [4]: https://www.w3.org/2023/09/TPAC/ https://www.w3.org/2023/09/TPAC/