Permissioning: only selected users can access media. This would require encryption or a level of permissioning.
Upload: users can upload media and decide who to give it access to.
Seeding/hosting/pinning: users can decide to host specific media (ie. à la IPFS pinning, torrent seeding, etc)
These are the 3 main must-have features. I could add an extra one which would be to offer these features through a nice interface.
I don't have a specific stack in mind but I think that encryption and keypair-based permissionning will allow to consider a variety of protocols. For example, there was Starling's archive explorer that used the Lit protocol to decrypt NFT content (if you owned a specific NFT). This means that the NFT is public but it content is only revealed to specific pre-approved users.
Keypairs allows for such flexibility in using tech that does not have built-in privacy (but allows for easily adding privacy/permisionning on top of it).
Some of my thoughts regarding prototype criteria.
Must-haves:
These are the 3 main must-have features. I could add an extra one which would be to offer these features through a nice interface.
I don't have a specific stack in mind but I think that encryption and keypair-based permissionning will allow to consider a variety of protocols. For example, there was Starling's archive explorer that used the Lit protocol to decrypt NFT content (if you owned a specific NFT). This means that the NFT is public but it content is only revealed to specific pre-approved users.
Keypairs allows for such flexibility in using tech that does not have built-in privacy (but allows for easily adding privacy/permisionning on top of it).