>>106197702
>unlockable bootloaders
part of the DRM pipeline
>vanilla web browser extensions
the fuck does that even mean
>play integrity attestation
that's DRM...
>random anti-bot checks for third party YT clients
every browser is a third-party client
>don't underestimate how powerful the cat is here.
you don't seem to know what you're talking about
a DRM solution based on PCR 0,1,7,23 is doable right now, taht's how it works on android and ios, not yet on desktop and it would be retarded as you can easily import your own PK/KEK/DB/DBX to your motherboard which would defy the point of the solution (you can do that on pixel, that's why grapheneOS only support them).
board makers have the microsoft keys/DBs pre-installed (that expire in 2026 btw, don't use them) but taht's it, if they want to ensure the entire root of trust they would have to force board manufacturers to prevent peopel from importing their own keys/DBs and factory flash google ones (they own widevine the most used DRM extension for web browsers).
that's why ARM without UEFI is gaining marketshare, no UEFI no issues, bis repetita of the android non-free market where globohomos sell a product but keep ownership of it.
>we're playing cat and mouse against a rich immortal cat cyborg that becomes strong after every defeat.
and the game would be infinitely more harder if they used DRM.
the only future I see is google replacing linux in android by their own kernel for more control, a total lockdown of bootloader even on pixel and services like youtube refusing access to people on desktop where they can't verify the root of trust (most people watch videos on their smartphones these days)
there is no technical way to prevent people to watch youtube without DRM, the easiest way is to block desktop altogether but I'm not sure it would hold in court especially in the US.
