Totally agree. Apparently FDroid devs don’t want to ship it as an update. They need to go trough uninstall flow so no data migration.
The best solution is an update over the old one. Same package name, same key, different app name. FDroid devs don’t want this.
The 2 apps proposal was me attempting to find a compromise.
This was about the link Bubu posted ONLY!!!
F-Droid will build and sign and the app will update as usual.
No, same answer as above
It does seem like the original Fennec and this one have two different use cases. Some people will want to use the original Fennec and some will want to use this one for different reasons.
Then there’s the people who might want to use both at the same time, eg. one for personal sites the other for non-personal???
Fennec Mk II
???
Just throwin it out there.
Fennec was a code name, that browser (code base) is no longer developed, has evolved, has been replaced.
Use the older not developed anymore, not patched anymore for personal or?
Because there’s no Fenix ESR.
Tell me more…
I’m curious, will this version have the same limitation on the available extensions that Mozilla’s official Play Store build has? Or will it allow all extensions previously supported on Fennec?
will this version have the same limitation on the available extensions that Mozilla’s official Play Store build has?
Yes.
There is a lot of work in adding extension APIs. Most extensions in IceRaven are broken.
Fennec F-Droid - will RIP soon on my device similarly like Firefox. New code base is a total disaster and no freedom. It have better to kill yourself then trying to live with this catastrophe next generation (for degenerates) browser from Mozilla.
According Report Broken Add-Ons Here: Sensible default addons list · Issue #63 · fork-maintainers/iceraven-browser · GitHub there are few add-ons broken. All add-ons I used on fennec work on iceraven.
Problem is: Fenix ain’t Fennec. Firefox for Android users were angered by the fact that the new Firefox is so different form the old one - in both good and bad ways. And since there is no feature parity between both browsers the migration was and still not fully possible. I think we should stick with the codename approach and call it Fenix to reflect these changes and differences between the two.
On the other hand: If we want to build a “brand” with the Fennec name we should have some kind of long term strategy regarding the name. I often promote Fennec F-Droid during CryptoPartys and similar events but I’m not too sure how much the “Fennec” name is stuck in anyone’s head. Maybe we should discuss this more publicly via Mastodon? Maybe have another (including some thoughts from this thread)?
Could you make a patch?
@CryptGoat
That is browser.urlbar.suggest.topsites
https://searchfox.org/mozilla-central/source/browser/components/newtab/data/content/tippytop/top_sites.json
iirc
I don’t know. First things first: Where would one submit that patch?
The upstream ticket tracking this is here: Support pref on Nightly to enable loading arbitrary extensions · Issue #14034 · mozilla-mobile/fenix · GitHub (well, one of many tickets)
When that’s supported upstream it should be easy to enable this in the f-droid build (or is enabled by default). Mozilla’s plan so far seems to be to allow loading arbitrary extensions only on nightly/dev builds.
Fennec 81.1.1 for arm64 is available now! armv7 version will be built later.
81.1.1 is not marked as the current version yet, upgrade manually if you want to. This is the last chance for Fenix haters to disable automatic updates.
The upgrade from 68.12.0 went smoothly for me.
Thank you, this is excellent! Upgrade went fine here as well.
