(as a bonus - thinking forever = GLM)

Of course money has to be involved.. try asking them whether device X will be supported or try reporting a bug. First you'll be verbally abused by "BadDaemon" (https://gitlab.com/BadDaemon), then you won't get the answer and your bug (and patch) will just sit in the tracker, because as this incredibly kind guy will explain to you, they're volunteers, they'll fix the bug when they want to, or they will never fix the bug. They might support the device in the future, or they might not and you're not supposed to ask about that unless you want to interact with BadDaemon - this interaction is the only thing guaranteed there.

Of course there are awesome people there, like npjohnson or mikeNG, but a pack of volunteers just can't compete with big tech giants..

> I have terrible news for you about how the official firmware works.

I've seen some e-waste ODM (Tinno) code and their freestyle philosophy on modifying the kernel code.. however they at least have to fix this so that basic functionality works as there's QA and serious bugs will affect certification and they'd not get paid. But here if you report a bug to PostmarketOS (but well, even LineageOS), nothing will happen unless you fix it (and if you submit a patch, it will sit there forever, welcome to FOSS).

> My general understanding of the Android ecosystem is that they do write drivers, and you don't want those drivers

What's wrong with pixel drivers for instance? I'm of course not talking about those written by e-waste ODMs like Tinno who can't even release GPL kernel sources properly.

Unfortunately even that one is missing modern replacements of outdated unsupported AOSP sample apps (like Phone and Contacts, others can be replaced without extra privileges).

We had Librem 5 which had real OS support that didn't have to rely on third-party volunteers, I wish they released something more modern..

Basically in the AI age, the difference between a vulnerability and a backdoor diminishes..

So far I'm able to block everything I want, but I mentioned replacing the response body because this is the only way I could modify or even inspect the service worker.. I think this vector could help circumventing ad blockers, but again - it would only matter if there were ads I'd not be able to block.

When it comes to distribution, firefox sucks because I can't even run my own extensions there, my distro doesn't package firefox developer edition so signatures are required. In contrast, Chrome let's me load unpacked extensions without any problems.

MV3 DNR redirect is notably lame though, instead of replacing the response it generates a real redirect which breaks for example replacing the service worker response. But could MV2 webRequestBlocking replace the response? Well of course not.

- sharing the model with DoD, NSA and Israeli government

However, in this particular case, AI has certainly helped us get much more tools, including those without the expectation of profit.

However, it's pointless to focus on what's not available but could - it's the WHY that matters. A toaster without fancy functionality might be mine, but a toaster that only cooks a specific brand of bread, or that displays ads doesn't feel like mine. This is not just a lack of a feature - it's deliberately not there to prioritize the manufacturer over my experience..

What you also seem to be ignoring is that the fact that for example there's no simple runtime internet permission toggle is NOT an accident, this functionality is deliberately not directly exposed despite creating no "security risks" and you know it very well.