Yeah, these options rely on having your own server alongside the network though, and I think in an ideal world we would all rather the network itself could handle these things
1 Like
You would anyway need a server to grant the access right.
But yeah, I wonder if it would be possible to have a webshop where a customer could pay for example with eth and get some album (or any data) linked to the sending address.
So first pay eith eth, receive an Autonomi data address which you could open only by using the eth secret key.
Could this be possible?
I don’t really know how Eth secret keys work but I can’t get away from the feeling that something more on the server/network side will be needed. The roadmap is a bit jargony though so hopefully I’m wrong and the talk of smart contracts is heading in the direction of the network itself being able to verify a user’s permissions and serve the data on that basis
If you buy MP3s from Amazon, I believe they are DRM free and you can do with them as you please. Obviously, local laws may dictate that you shouldn’t share them with others, but that doesn’t prevent it from happening.
In terms of distribution, you could package them uniquely (e.g. a tarchive with a random file/noise at the start) and threaten folks not to share it. It would mean there was a fresh upload cost for each, in order to randomise the chunk addresses though. I guess it depends how much uploaders care about that?
1 Like
but would it be practically same if you upload only once and tell not to share the secret key?
Nothing against distributing things without DRM per se but to my mind Autonomi is particularly suited to streaming as opposed to local storage.
Either way on the technical side the current model (if I’ve understood correctly) would be that you make a file non public and then share the address of the data map for that to chosen people/ customers. All it takes is one person to start sharing that address and then anybody can access the file in perpetuity, which seems a little bit too easy and cheap and permanent as a form of piracy!
Any workaround I can think of seems very cumbersome, and unless it uses a server probably not secure enough to be worth it anyway.
In addition and maybe most importantly any workaround compromises the potential interoperability of data between apps, which is one of the biggest potential benefits of Autonomi.
For my own purposes (I’m not super precious about copyright) I will probably start with the above piracy friendly model so that the focus is on interoperability and Jams and other apps can all play the files easily, and then see what the future holds/ how others approach it. Hopefully at some point the nodes will have more capability for this sort of transaction, because I think it could be a huge opportunity for the network.
2 Likes
Isn’t It what multisig is for? As far as I understand that’s still on the roadmap
1 Like
How about adding a watermark to the end of the data? Every customer gets an own key but it would not prevent de-duplication,
1 Like
I’ll look into it, I suspect you’re right - to be honest I’d be surprised if it wasn’t on the roadmap at all, it’s just this version seems particularly impenetrable in it’s use of technical jargon!
The current de-duplication arrangement almost does that anyway I think - I can always check if the data is my exact version by hashing it. My problem is the current arrangement seems to make the data I have paid to store available to everyone, if I make it available to any one.
Well, it has always been like that. With autonomi it is just easier because only the key need to be shared, not the whole data.
People are going to bootleg everything. Why not market to collectors?