So I’ve been trying to think about websites/webapps that would be nice to make on the SAFE network, and in doing so I’ve found myself wondering about data ownership.
If for example, you were making a simple website where people post images and text would they upload it to your site’s storage, or would they upload it to their own storage, and link it to the site?
The first option is the most convenient one for the user, I would say, in most situations, but maybe if you were making a sort of YT replacement, it might be nice to have the video always be the users data, instead of the site’s data.
The only thing that seems like it could be a downside is relating to Safecoin. In the situations where the user is hosting their own data, they must pay Safecoin. Now, I’m sure this could be automated in many circumstances, but what concerns me is how fast could an average user generate safecoin, and how much data usage would they get per coin?
Something that I think would suck is if during your normal usage at some point you get hit with a “you don’t have enough funds in your safecoin account to post that image on this website” message.
Is this simply something that’s going to get worked out in one of the testnetworks when safecoin goes into beta, or is there already some kind of vision for how this will work?
My understanding is the majority regular users of public web site may not want to pay for visiting site or uploading/posting to sites. People r used to the ‘free’ stuff offered by web.
my short term vision of gaining users for web site, is that we need to think about ‘free use’ based business model to attract users.
The general idea is that you own what you upload. You always stay in control of your data. But it also means that you need to pay for it. It’s quite different then what we are used to and it’s gonna take some time before people get used to it. All for the better IMO.
That’s the big question. Basically the cost of storing data will be a function of how much space is available and of how much Safecoins is available (how many Safecoins get recycled). This is driven entirely by the behaviors of all users.
My guess is that once the network is live there is going to be a lot of space available and it’s gonna be fairly cheap to store something. On the other hand it will also means that you won’t generate a lot of Safecoins with your vault. Somewhere a balance will be found.
My hope is that it will be fairly easy to get enough Safecoin to pay for your daily needs but you will need to be a bit more mindful when posting larger data like pictures and videos.
Yeah, I agree some people will rage quit over this. It’s like paying for water when you are used to getting it for free. But it’s a different mindset and people will learn to be more careful about what they wish to post online, which can also have good side effects.
AFAIK that’s the plan for now and I’m hoping it stays close to this vision. You can’t take ownership without paying your dues.
This is a good point. It will mean that people become mindful with the “garbage” they put online. It might stop the (figuratively) infinite re-posting of meaningless stuff.
Isn’t part of the beauty of the internet how much garbage is on it, though?
I mean, not social media nonsense, but just the random stuff you can find out there. Websites for people’s dogs, dumb YT videos… the works.
I mean, it all remains to be seen, and maybe that will still happen, but there would be a bit of an empty spot in my heart if that disappeared completely.
The frame of reference for “site” has to shift when thinking of the SAFE architecture. All data is maintained by the network at large, once uploaded. Immutable data is always the same ( i.e., immutable) once uploaded. Access is determined by whether or not you have the data map to access it, and any additional encryption key. A “site” is also basically just data maintained by the network at large that refers to other data. The site can change if it is mutable data. Then the site owner can modify the data to point to different content, etc. That’s the simple view anyway.
My point is that thinking about SAFE you have to remember that the network stores all data and will deliver requested content to anyone who has the knowledge to request it. So there really in no such thing as “your site’s storage,” at least in the way we’re used to thinking about it.