←back to thread

Yt-dlp: External JavaScript runtime now required for full YouTube support

(github.com)
798 points bertman | 1 comments | 12 Nov 25 10:12 UTC | HN request time: 0s | source
Show context
xeonmc ◴[12 Nov 25 12:31 UTC] No.45899355[source]▶
In ten years time YouTube will be entirely inaccessible from the browser as the iPad kids generation are used to doomscrolling the tablet app and Google feels confident enough to cut off the aging demographic.
replies(9): >>45899394 #>>45899462 #>>45899465 #>>45899525 #>>45899536 #>>45900001 #>>45900317 #>>45900441 #>>45900653 #
vachina ◴[12 Nov 25 12:52 UTC] No.45899536[source]▶
They’d need dedicated hardware to enforce any kind of effective DRM. Encrypted bitstream generated on the fly watchable only on L2 attested device.
replies(7): >>45899618 #>>45899734 #>>45899739 #>>45899807 #>>45900214 #>>45900945 #>>45902867 #
yard2010 ◴[12 Nov 25 13:21 UTC] No.45899807[source]▶
Can you explain in simple terms what would prevent one from running the decryption programmatically posing as the end client?
replies(5): >>45900061 #>>45900104 #>>45900132 #>>45900160 #>>45903399 #
1. GeoAtreides ◴[12 Nov 25 13:50 UTC] No.45900160{3}[source]▶
Yes, it's called: Web Environment Integrity + hardware attestation of some kind

> "the technical means through which WEI will accomplish its ends is relatively simple. Before serving a web page, a server can ask a third-party "verification" service to make sure that the user's browsing environment has not been "tampered" with. A translation of the policy's terminology will help us here: this Google-owned server will be asked to make sure that the browser does not deviate in any way from Google's accepted browser configuration" [1]

https://www.fsf.org/blogs/community/web-environment-integrit...