1001
Language
(lemmy.blahaj.zone)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 26 Aug 2025
1001 points (100.0% liked)
Microblog Memes
9000 readers
2068 users here now
A place to share screenshots of Microblog posts, whether from Mastodon, tumblr, ~~Twitter~~ X, KBin, Threads or elsewhere.
Created as an evolution of White People Twitter and other tweet-capture subreddits.
Rules:
- Please put at least one word relevant to the post in the post title.
- Be nice.
- No advertising, brand promotion or guerilla marketing.
- Posters are encouraged to link to the toot or tweet etc in the description of posts.
Related communities:
founded 2 years ago
MODERATORS
I think that, with the current state of OSes like Windows and Android, there should be some minimal amount of friction to enabling installation of non-vetted apps. Maybe some switch that can't be enabled accidentally, or without understanding that there's risk involved (or at least a switch that can be disabled and password protected) for the sake of children or the elderly.
On the other hand, though, an OS should be built with enough security and sandboxing that no single application can brick your entire device without at least tapping through and giving it a ton of permissions; which means that the only remaining risk to the end user would be access to disinformation or other harmful content, or the risk of personal information exfiltration (i.e. phishing). At that point, a simple block list (or even just an allow list) maintained by a trusted guardian or third party would be sufficient to keep children or the elderly from harmful content, and whoops we've just invented the internet again.
I am once again begging for Boot2Gecko to become a thing.
Yeah I can accept some kind of "hey we can't verify this, you are on your own if you want to install" warning message, but if it prevents me then I don't want it.
I don't know about you, but my Pixel 6a already does this. When I go to install an APK not from the app store directly it warms me, requires me to acknowledge that the APK was downloaded through Firefox, and acknowledge what permissions it is requesting.
Yes, the problem is that Android is talking about requiring developer verification at install time; as I understand it, without allowing an override.
Boot2Gecko is a thing: it's called KaiOS. It targets lower tech devices though and is just as locked down as Android, potentially even more actually.
I'm interested: why do you want it? I'm not a big fan of the idea of web development being the standard
I, too, hate web dev being the standard. It's inevitable though. Mostly OS agnostic, easy to learn, etc.
As for KaiOS, I don't think that's really a good successor of Boot2Gecko; from what I've seen they went the app route, which kind of fundamentally violates the spirit of what B2G was supposed to be.
Let me answer your question with a question: How many things do you do with your phone that aren't also able to be accomplished with a website already? I'd be willing to bet that the answer is in the single digits. And for most of those, that limitation is likely to be entirely arbitrary, instituted by a developer as an anti-consumer form of lock-in.
Delivering application-like experiences via the web allows users to make accessibility changes to that experience without the developer needing to support it explicitly. It also allows users to implement plugins that extend and improve their experience, by removing undesirable content or adding functionality that you haven't provided. And because browsers are built on open standards, there's no longer any device ecosystem lock-in; I should be able to access all of the websites I want to from any browser on any device. Users could even build their own bespoke applications, without the need to enable a developer mode on their phone or get a certification from a megacorp.
And because downloadable and cacheable progressive web apps are a thing, as well as local storage options for browsers, the experience for an end-user of a browser-only phone wouldn't need to be any different in low-signal or high-latency situations.
The web is a mature and proven platform for delivering arbitrary code and data, plugins make the web more accessible and easier to use, and web standards make the world more open. It's not a perfect platform, of course, but it's the one we've got; I think making it the default rather than the fallback for the devices most people use more than any other would be a great boon for the world at large.