@GrapheneOS Well, you've to ask #Google and #Fiarphone that and consider invoking #Regulators like @EUCommission, @kartellamt@social.bund.de and others in that matter.
Which again proves my point:
#AllGAFAMsAreEvil and NOONE shoud've ever trusted them with anything!
The #Android ecosystem is fucked up and there is a need for #vendors to refuse to bow before #Google and actually do #secure & #repairable devices.
Again: You seem angry at the wromg person if that means you're angry at me.
The question to me is how is #GrapheneOS gonna go about this?
- Cuz we both know Google can afford to go "maximum asshole" on you [the Grpahnene OS Project] and even in the worst case their legal department won't even notice this whole shitshow even if miraculously by the wounders of everyone from @eff to @fsf to @noybeu and @CCC forcing Google to literally support and endore GrapheneOS, because by the time any binding court ruling would be enforced, Google would've choked the project out of the market.
So my question is when will you get forward and work with other #vendors instead of tying your project to Google-specific and thus sorta-proprietary implementations?
[...] Pixel targets have a lot of device-specific hardening in the AOSP base along with some in GrapheneOS which needs to be ported over too. For example, various security features in the kernel including type-based Control Flow Integrity (CFI) and the shadow call stack are currently specific to the kernels for these devices. [...]
To me that sounds like some very serious #VendorLockIn you're stuck in, and now it bites you in your rear...
I hate to say it, but #ToldYaSo sadly happened!
I guess you gotta have to bootstrap it from scratch starting with #toybox + musl / #linux sooner or later...
Not to seem like an asshole, but I do sincerely wish GrpaheneOS and it's team only the best of luck and that the issue gets fixed sooner than later, because this #Vendor #LockIn is a major issue [and yes I do blame the Device Vendors that shit out unmaintained garbage] so unless you can afford the legal cost of actuall enforcing #EU laws re: #SecurityUpdates and force Vendors like #Fairphone to actually follow their claims re: #Security and #Updates, this won't move anywhere.
- Yes I know you don't have that money and I don't expect this to be the case!
I do however also don't expect you to find a magical solution. My point is that there needs to be a change of strategy, and relying on Hardware you neither own nor control in the sense of Stakeholding isn't going to provide you with the necessary stability.
- Because Google is a [pulicly traded] #Corporation and Corporations are explicity nobody's friend!
Breaking: Microsoft limits Extended Security Updates for Windows 10 to one year at $30 post-October 2025! 
Users must decide if it's worth it or time to upgrade. 
