Fucking based, not giving them an inch. #systemd should learn from this and not enable this crap, not even *signalling* a teeny tiny amount of support.

Wonder what #Motorola will do about this, I don't think they like this. But who cares, doing the right thing rarely makes the maximum amount of profit.
#GrapheneOS #Android #Linux #privacy #security

@Natanox This is good, though I'm switching to a Linux- based phone later this year because Android slowly becomes hell as a whole
@clumsy @Natanox Using GNU/Linux with mobile desktop environment is not more secure, private, stable or fast than OS based on AOSP like GrapheneOS. And Android is Linux distribution too.
@a53bdb @clumsy Is that so?
https://keepandroidopen.org/
AOSP is still in the hands of Google and the repo is awfully locked down. Maimuaika is right to switch, I'll do it myself if I can (have to change a few things and get the money before).
Keep Android Open

Advocating for Android as a free, open platform for everyone to build apps on.

@Natanox @clumsy Developer verification is a part of Google Mobile Service, not AOSP. The same policy is done by macOS years ago, it doesnโ€™t make Android closed in my opinion. The delay of security patches does affect security of AOSP distributions, but the delay of AOSP doesnโ€™t affect much.
@Natanox
I wonder if any group has considered just spoofing it with a hardcoded 1970-01-01.
@Natanox i hope they will also get some sort of an anti-genai policy. i know they can't do much about aosp code, but they can apply it to their own projects and their own changes
@Natanox Why the mention of Motorola there? 

@Natanox

Looks like systemD is now going even further, integrating AI agents and disabling any init compatibility. I'm here for the Unix way of life, not the slopfest.