AmputatorBot VS Fenix

why amp is bad, and how to remove it from your URLs.

I would suggest you use AmputatorBot when coming across AMP links u/Ok-Flamingo-1499. AMP is a google centered project. From the AmputatorBot page:

This is for everyone & not just OP. Reddit seems to automatically delete GoogleAmp links. So they are not visible unless a mod approves them. Before posting (and also in comments), check if your link is a GoogleAmp link. Find a better link or clean the link before posting as post or in comments - https://www.amputatorbot.com/

www.amputatorbot.com

credit amputatorbot

I recommend using amputator bot to remove amp from links. Google keeps track/caches all these links to (supposedly) speed things up, but it's another Google control method (and not secure).

You should really remove the /amp portion of your link. This should help make that easy and explain why it matters.

It's been that way for years: https://github.com/mozilla-mobile/fenix/issues/20351

I lost hope it and other issues would be fixed and moved to Chromium on Android.

Firefox for Android was rewritten pretty much from scratch circa 2020. Collections are one of its many unfinished and poorly-thought-out features, and they never got around to implementing the ability to sync Collections to desktop. It was a known problem in 2019, while the rewrite was being worked on, and Mozilla doesn't appear to have given it any attention in the years since.

People have been asking for this for over a year via Mozilla's current feedback channels, and for two years on the previous issue-reporting venue, to no avail. It was automatically moved from the old venue to Bugzilla ostensibly because Bugzilla makes it easier to track and work on issue reports, but they haven't actually worked on that issue report at all.

Known issue, not a new issue, and unlikely to be fixed any time soon, unfortunately. I had this before I stopped using the Android version a year ago. It was reported as a bug at least a year ago on their old issue tracker, and later moved to the current one, where last activity on the issue report was three months ago. No apparent progress toward any fix.

Since Fenix's first release they've been saying that the absurd limitations on add-ons support were only temporary, and they would have quickly increased the number of supported ones.

And instead absolutely nothing changed for three years.

Furthermore the insane bugs from which Fenix suffers from its release (https://github.com/mozilla-mobile/fenix/issues/12731) (making it unbearable) have been left hanging, focusing the few resources on dumb ui experiments.

So everything suggested that Mozilla did not care of its Android browser, or actually that they were deliberately sabotaging it.

This news instead represents a huge improvement, hence my bewilderment.

I don't know what people who downvoted my message thought I meant.

https://github.com/mozilla-mobile/fenix/issues/20012 and https://bugzilla.mozilla.org/show_bug.cgi?id=101865

This was sadly deprecated on Android: https://github.com/mozilla-mobile/fenix/issues/12099

It was such a huge loss for me that for at least a year I used the outdated pre-Fenix. Now they still work on Desktop but they just stopped working on Android (althouth the bookmarks itself are synced-up)