That’s interesting. This post had suggested it isn’t yet possible to host an AppView. It seems the reality is more complex.

Whether it soon becomes possible to self host an AppView, the one remaining centralized component will tell us a lot about where it’s headed.

ATProto is almost there with the only missing piece being the AppView. I’m not sure if BlueSky is hesitant about releasing theirs as open source, but I don’t think there are any barriers to a third party implementing one.

I’d still echo the (current) top comment’s advice to use something open source, local, and encrypted.

They’ve already taken the hard stance. If they roll it back, they will lose the trust of their users.

Biowink GmbH is probably not a corporation registered under US law. If I had to guess, the government of Germany will not be particularly eager to force them to turn over data to the USA. The Germans take their Datenschutz very seriously.

It seems to me software designed to facilitate discussion shouldn’t have a downvote buttton. There should be a UI for marking comments as inappropriate, but it should require a second step saying why. Perhaps one of the reasons should even be “I disagree”, but that option should have no effect.

It’s not impossible to abuse of course, but it nudges people in the right direction. Those UI nudges can be pretty effective.

Maybe, but the archetypal non-technical user, my mother does want to run a third-party ROM. Her phone is out of its official support period, and she knows that security updates are important and would like a way to get them. Most people, at least in wealthy countries do have a technical person in their lives they can ask things like that. She doesn’t want to buy a new phone because it would be too big and lack a headphone jack, a position I share.

I had to recommend against running what I run (LineageOS, Magisk, Play Integrity Fix). Without PIF, too many apps will refuse to run on LineageOS. She doesn’t need root for much else (maybe adblocking) and doesn’t have the knowledge to make good decisions about whether to grant root permissions to an app that asks (Magisk doesn’t have an allowlist-only mode, but it should). Finally, keeping root through an update is fussy. It’s not hard, but it’s an extra step that has to be done in the right order every week or two.

Unlike Firefox in 2024, a third-party Android build that’s easy enough to install and isn’t sabotaged by Safetynet would something many non-technical users care about: an extended useful life for their devices.

Last time I used one was because I forgot my physical wallet and needed to pay for something. I don’t want to tell Google about my shopping habits, but I like to have options in case of emergency.

I’m running LineageOS (with GMS), Magisk, and Play Integrity Fix.

Can you cite examples of rooted smartphones leading to significant data breaches or financial losses? When the topic comes up, I always see hypotheticals, never examples of it actually happening.

It seems to me a good middle ground would be to make it reasonably easy (i.e. a magic button combination at boot followed by dire warnings and maybe manually typing in a couple dozen characters from a key signature) for users to add keys so that they can have a verified OS of their choice. Of course, there’s very little profit motive to do such a thing.

Google doesn’t want distributions of open source Android without Google services to be a viable option for mainstream users because that would reduce their ability to extract profits from the Android ecosystem.

While the focus is surely more on OEMs than end users at this point, I’m sure Google wants to keep the difficulty level for end users high enough that it remains niche.

I think the main reason third-party ROMs aren’t more popular is that Google and certain app developers fuck with people who use them. The article addresses the difficulties later on, but comes up short in my view on just how much of a hassle it is for someone who isn’t a tech enthusiast who wants, for example to keep an older phone up to date for security reasons.

I think the main motivation for Google is limiting user control over the experience. More user control leads to unprofitable behaviors like blocking ads and tracking, which is also the motivation for recent changes to the Chrome web browser that make content blocking extensions less effective. In all cases, companies that try to take away user control claim the motivation is security, usually for the benefit of the user.

Even if you did (don’t eat batteries), the voltage range is much lower and you probably wouldn’t feel anything.

Now if it was added to rechargeable batteries, it would be pretty useful

I think the reason we haven’t seen that is that NiMH rechargeables have fairly stable voltage during discharge while alkalines don’t.

I use Firefox almost all the time, but I’ve run into a few sites that act up, and the rate seems to be increasing. Sometimes I complain.

When Firefox had a tiny set of permitted extensions, I used Kiwi most of the time.

There are better ways to assess the legitimacy of a media outlet than critiquing its web design. The Wikipedia page might be a good start.

I don’t like the loginwall, but it doesn’t require payment.

The biggest reason is most likely that the cases had different judges.

My initial reading of the reporting on this ruling suggests it won’t do that. App developers can opt out of most of the provisions, but Google may not pressure them to do so.

Extension developer information from Firefox explains why it was necessary to make some technical changes. What they’ve never explained to my satisfaction is why they took a cautious, curated approach to it reminiscent of Apple.

The typical approach of a large open source project is to put a “here there be dragons” sign on unstable features and let anyone who wishes to use them anyway do so at their own risk, and that’s the approach I prefer.

Kiwi Browser has offered an Android build of Chromium that will install and attempt to run any extension available for desktop Chrome. Most of them work.

Firefox also recently regained reasonable extension support on Android, which was a slow and frustrating process for those of us who had used it before.