

Here you go:



Here you go:



Precisely. Same reason why Apple pushes zsh and ancient bash down everyone’s throats.
If I convert my claude-code to pastafatianism, will it be able to cook spaghetti for me? Will it also pick up sauce recipes if I put them into the skills directory?


Being honest, I would be surprised if there wasn’t malware there. The whole Telegram platform is kind of a nesting ground for it.


Well, 1.5 milliwatts doesn’t sound a lot… But seems like for TECH(sic!)radar somehow it does.


It doesn’t really matter in the context of this particular topic. They’ve highlighted the problem and I think in here we should abstract from their personality and their conflicts with Murena & Co., and focus on the problem itself.
And the problem is that, regardless of who’s implementing the attestation technology and regardless of who is critizing it, the very concept of device attestation based on OEM/Google/Apple/Murena/GrapheneOS/whoever approval is harmful and anti-consumer at its core.
No matter who owns the authority to decide which devices are deemed “good” and which are deemed “bad”, this authority shouldn’t exist at all. Only the user should be in charge of the decision of which os to use — be it Google’s Android, GrapheneOS, MIUI, eOS, PostmarketOS or MS-DOS — OEMs/Google/Murena/etc should have no say in it.


https://grapheneos.social/@GrapheneOS/116200110686604617
It’s literally the same crap, just “under the new management”.


Fuckers.
Which is ALSO a good thing, obviously :)