Live data from Hacker News

Add-on support in new Firefox for Android (2021)

discourse.mozilla.org

171–180 of 220 posts

Re: Add-on support in new Firefox for Android (2021)

#171
post #97

Earlier quoted context omitted.

Every video, I get errors in the UI. I once powered through, it seems eventually the video does play normally. Perhaps that is because of blocked ads(by newpipe then - I have no other restrictions on mobile)

Keep NewPipe updated. You must install every update as soon as it tells you one is available. I've not got any error for a while.

Also, add the NewPipe repository [1]. The versions in the main F-Droid repository are often out of date.

[1]: https://newpipe.net/FAQ/tutorials/install-add-fdroid-repo/

Re: Add-on support in new Firefox for Android (2021)

#172

Earlier quoted context omitted.

they know it. that's why they've killed XUL. that's why they're going even further by enforcing an inferior extension standard from their supposed competitor. that's why they've killed off the extensions and about:config for the android version. that's why you can't even use a private extension on desktop without jumping through the hoops. that's why usercss (toolkit.legacyUserProfileCustomizations.stylesheets - lega…

No. > that's why they've killed XUL We couldn't deliver a multiprocess browser without doing it. > about:config for the android version I completely supported this and continue to do so. GeckoView on Android works completely differently than desktop Firefox, and about:config's semantics are not identical between the two. A few of us were interested in offering an alternative that gave users a way to make adjustments…

> We couldn't deliver a multiprocess browser without doing it.

So uh. What was that whole thing about making all the extensions rewrite their code to support multiprocess?

Which many extensions did, putting in huge amounts of work, only to be told shortly after that XUL was going away.

https://web.archive.org/web/20191220054834/https://developer...

Re: Add-on support in new Firefox for Android (2021)

#173

Earlier quoted context omitted.

Not only does it not make sense, they presume they know better than their poor users what their users should see and what opinion on web content they should have. If I want activist browser developers, give me teams like Brave and Vivaldi, thankyouverymuch. Both actually do things that serve the end user in their own way. Insofar as the browsers have politics, they are politics about the browser itself like antitrack…

> if California would stay in California, that would be great Then you wouldn't have most of the IT industry and especially FOSS.

>especially FOSS.

I just wanted to log in and point out that Free Software got started at MIT.

Re: Add-on support in new Firefox for Android (2021)

#174
post #79

Earlier quoted context omitted.

you can use fennec from f-droid too. it's compiled from stable, not nightly.

You don't have to put so many copies of the same comment on one story.

It think it's fair, its a response to all the copies of the same complaint (aka "i dont want to have to use firefox nightly")

Re: Add-on support in new Firefox for Android (2021)

#175

To this day Firefox for Android still does not have a tab bar on tablets. Which is double ridiculous since the previous two rewrites both did have one (in fact I contributed to the former...).

Yeah, but what's the tablet market for Android these days?

I just bought a Galaxy Tab S8 after continually being disappointed with the iPad and lack of user-friendly multi-tasking capability.

I was disappointed to find that Firefox's tablet interface is just a blown-up phone interface. I have switched to using Edge instead because it looks like a proper desktop browser with a tab bar, and has integrated ad-blocking.

For me, the two biggest pain points I experience with Firefox is the lack of PWA support on desktop, and now the lack of a proper tablet interface. So I end up using Chrome/Edge on desktop for PWAs, and now I use Edge on tablet.

It's getting harder to stick with Firefox...

Re: Add-on support in new Firefox for Android (2021)

#176

Earlier quoted context omitted.

> if California would stay in California, that would be great Then you wouldn't have most of the IT industry and especially FOSS.

>especially FOSS. I just wanted to log in and point out that Free Software got started at MIT.

That did cross my mind as I wrote the GP, but the center of it has been and is CA.

Re: Add-on support in new Firefox for Android (2021)

#178
I remember back in late 2018, early 2019 I downloaded the Nightly version, Mozilla had been hinting on a rewrite for a while and I wanted to see what they were up to. This version seemed solid, although a work in progress: you could not customize the listed sites in the home screen, addons were disabled and the settings seemed lacking compared to what we had in the stable release, but work was solid.

Then, out of nowhere, they phase out what we currently have with this half-baked Nightly version. The app updated itself overnight and now all the addons are no longer supported (Violentmonkey was a big one for me as I could customize some websites with a user script), the home page icons can't be rearranged, the history can't be deleted and overall this updated app seems like a worse deal that we previously had.

Mozilla has stopped caring about their products. It seems that nobody in there is dogfooding Firefox, and it shows. They have a big advantage because of Google still not allowing addons on Mobile Chrome, and instead of opening up the whole ecosystem (which previously most of the desktop addons were compatible with the mobile app), they double down on allowing only a very short list of preapproved addons.

Re: Add-on support in new Firefox for Android (2021)

#179
post #114

Submitted title was "Firefox addons are still unavailable on Android, two years after Fenix release". Since that language doesn't appear in the OP, it seems a little editorialized and I've replaced it with the page title now. If there's a better (more accurate and neutral) title that uses representative language from the article itself, we can change it again.

This title change is a complete disservice. It's vague and milquetoast to the point of meaningless now when before it firmly but fairly stated the truth of the situation.

Re: Add-on support in new Firefox for Android (2021)

#180
post #114

Submitted title was "Firefox addons are still unavailable on Android, two years after Fenix release". Since that language doesn't appear in the OP, it seems a little editorialized and I've replaced it with the page title now. If there's a better (more accurate and neutral) title that uses representative language from the article itself, we can change it again.

This title change is a complete disservice. It's vague and milquetoast to the point of meaningless now when before it firmly but fairly stated the truth of the situation.

Actually I saw the (2021) in the title and it made the tragedy quite clear.
Post reply on HN