You got me there

Not that I disagree with the message, but why is most of it highlighted?

You don’t know how long that crumple zone was before it hit the three

Modern cars are a wonder of safety engineering

I’ve seen Uber drivers just using Waze

I mean if you let cars on a car-free street, it’s not a car-free street.

Edit: okay wow it’s even worse than the headline says. Waymos aren’t even going on the road, it’s manned Uber and Lyft rides. No wonder people are confused.

Probably ECC unfortunately

I think you do you liar

Should’ve used a quebecois accent

How did you get my power bill

Caitlyn Jenner is one of the most famous examples of pulling the ladder up after yourself

Isn’t Bluesky like the most pro-Iran social media site besides some Mastodon instance at this point? Seems counterproductive to silence your biggest megaphone.

The words are fully synonymous in American English, and Australian possums are named after American possums.

Titled Goose Game

I really hope this is a shitpost

Ubuntu, Mint, and Debian all still rely on the Linux kernel, though. A better comparison might be how LineageOS is technically a fork of the dead CyanogenMod project, but even before the latter fully imploded was different enough to be its own thing.

Both of them still relied on the existence of AOSP though, for new features, bug fixes, hardware support, certain core functionality, etc. AOSP is a lot bigger than just the Linux kernel, and because of the tighter coupling between hardware and software on mobile devices, there’s a whole other discussion about creating a real non-Android OS for them, but I think that’s a closer parallel.

Only on that platform. The Android™ platform is way more popular than AOSP, but that doesn’t mean Android™ precludes AOSP.

For the purposes of making a custom Android-based OS like GrapheneOS, AOSP is better than ever. Whether or not there are actually devices to install GrapheneOS on kind of isn’t the point here in my mind since we’re talking about which one someone prefers, which means they’re already able to use both.

And as GrapheneOS’ existence demonstrates, it’s still pretty easy and even increasingly mainstream now to change your device’s firmware. GrapheneOS currently is only built for Pixel devices, made by Google, the company that also develops AOSP and owns the Android brand. In theory Lenovo is going to have a Motorola branded device running GrapheneOS officially in the near future, but Lenovo doesn’t have a great track record with mobile software support.

Android™ itself might be getting more locked down and centered around Google’s services, but it’s still an option to move to something else based on AOSP, and thanks to things like Project Treble (which is enforced by Google Play’s compatibility tests), you might not even need device-specific firmware to have a usable and pleasant non-proprietary experience.

The situation with Android is weird, because Google technically owns all of it, but it’s completely different departments going completely different directions, and it doesn’t help that we all call the entire concept Android when that’s technically the brand for Google’s special certified versions of AOSP (which also includes the word Android but not as a brand…).

The source code is still fully available (and even searchable with code references) which is why all of these community and FOSS forks are still possible.

Google is absolutely abusing their influence over the Android brand to continually lock down consumer devices and the versions of Android that ship on them, but AOSP has only gotten more open-source friendly over time if anything. The problem is there are fewer and fewer devices that will actually let you leave branded Android™ for some version of AOSP.

Ironically the fork that only runs on the phones made by the company that also makes Android

You’r?