Kathryn Bigelow’s most under-rated film is almost upon us…just 30 years later than we thought.

Also…if you haven’t seen that movie…go watch it. It’s low-key one of her best.

My last few phones have been Motorolas and I’ve been very very happy with them.

My only issue was that back then, I wasn’t really paying attention to alternative OSs like Graphene, Lineage or e/os and was therefore not really too concerned with ROM support/chip set. When I switched over to e/os, two of my Motorola’s (including the one I WANT to use with it) has no ROM support because it’s running a Mediatek chipset. So I’m using my second to last one while my nice new one collects dust.

Moving forward I’ll be paying more attention to Qualcomm vs Mediatek.

This was honestly my biggest fear for a lot of FOSS applications.

Not necessarily in a malicious way (although there’s certainly that happening as well). I think there’s a lot of users who want to contribute, but don’t know how to code, and suddenly think…hey…this is great! I can help out now!

Well meaning slop is still slop.

I feel embarassed to say this as someone who is fairly techy, but I’m a little confused by the whole brouhaha.

Is Google making changes to Android, or to AOSP?

If Google is making changes to the Android fork they put on their own phones, then fuck 'em. Use Graphene. Use e/OS/, use Lineage…use something that forks their own branch of AOSP and Google can pound sand because those forks are in no way obligated to make the same changes as Google. AOSP is open source for that very reason.

If Google is making those changes to AOSP itself, which means that anyone who uses AOSP as a base have those changes by default, then isn’t Google obligated to keep those changes as Open Source, in which case anyone else who uses AOSP can just remove them from their own fork?

Someone explain like I’m a particularly dim five-year-old, please.