There is a solution to this for videos you upload from now on. The problem is decoupling persistence and access. Imagine a decentralized network where you could “pin” videos the way you do in IPFS, but they’d be streamed and end-to-end encrypted.

Websites could ask their visitors to keep a tab open and their browsers will automatically store chunks (and earn safebux for serving videos, if they want to turn that on). This was designed to be far simpler than IPFS, with no “sealing” … just open a browser tab and get paid.

https://www.helpnetsecurity.com/2026/06/19/safecloud-browser...

It works now, you can try it locally:

https://github.com/Safebots/Safecloud

The real interesting part is when it connects with Safebox remote attestation. Here you can prove that the server has not been compromised, and that together with HTTPS proves that the JS is official. You don’t need men with guns for DRM or copyright… you can enforce it this way. An individual user might hack the JS they got but someone else can’t distribute the hack at scale (unless it is with a rogue jailbroken browser). The Jets in safecloud wouldn’t release the chunks unless there was a recent assertion + TPM attestation from the Safebox serving the player iframe.

This way you can enforce revenue streams like “pay per minute” and have the client side actually enforce it for nearly all users.

@tptacek you would love Safecloud I think