Anytime I get one as an Uber I try to play stupid like I can’t figure out the door handles. Slam the doors, pull the emergency door release (if there is one), push against the motorized door close mechanism. Ask if there’s a shade for the glass roof. Anything to remind the driver that it’s not a good car, especially as a taxi.

Building a linux phone: do you mean from scratch, or just installing one of the Linux phone OS's that already exist? I've been following Ubuntu Touch for several years now and, while they have made a lot of progress, its main hurdles have the same thing in common: mobile hardware is incredibly locked down. For example, Ubuntu Touch uses proprietary Android drivers for many low level functions. Even then, there's some features that aren't stable across all devices, like VOLTE. It sucks, I really want to use Ubuntu Touch (or any of the Linux alternatives) but I can't make phone calls or text in the US without VOLTE support. There are a few phones that support VOLTE, but the feature is either in beta, the phone is expensive, or the phone is not sold in the US. Anyways bringing that back to Graphene: In my case, I'm using this as a stopgap until Linux phones take off (assuming they ever do). For now I guess the best thing is to just be skeptic, keep things minimal, and bloat-free.

The cost of consuming media doesn’t match its worth. I never used ad blockers until they became invasive and disruptive.

Read again. I quoted something along the lines of "just as much a development decision as a marketing one" and I said, it wasn't a development decision, so what's left? Firefox released just as frequently before, just that they didn’t increase the major version that often. This does not appear to be true. Why don't you take a look at the version history instead of some marketing blog post? https://www.mozilla.org/en-US/firefox/releases/ Version 2 had 20 releases within 730 days, averaging one release every 36.5 days. Version 3 had 19 releases within 622 days, averaging 32.7 days per release. But these releases were unscheduled, so they were released when they were done. Now they are on a fixed 90-day schedule, no matter if anything worthwhile was complete or not, plus hotfix releases whenever they are necessary. That's not faster, but instead scheduled, and also they are incrementing the major version even if no major change was included. That's what the blog post was alluding to. In the before times, a major version number increase indicated major changes. Now it doesn't anymore, which means sysadmins still need to consider each release a major release, even if it doesn't contain major changes because it might contain them and the version name doesn't say anything about whether it does or not. It's nothing but a marketing change, moving from "version numbering means something" to "big number go up".

Wait until AI reduces it to just owners.

Cool, so that's a specific problem with your needed use case. That's not what you said before.