Storage is cheap, and text doesn’t take a lot of it. If I provided only 100GB of my 30€/month dedicated server’s 1TB storage space to the network, I could store one hundred billion characters of text.
(In reality, it’s of course going to be less because of multibyte encoding, metadata, encryption and the like, but the ballpark remains the same).
If I do not use the full 100GB, I get Safecoins, which I can also use to store data.
Meanwhile, for the average person, setting up a SAFE node just to post text messages to a message board hosted on SAFE is going to be a hassle. Also, they would have to dedicate system resources, no matter how little, to the network, which some may not be able to do, or buy Safecoins from somewhere else, which is also at least inconvenient - and it would be difficult to purchase an amount so small that it’s only useful for text.
So why not put them and me together?
What I’m thinking of is either a user-friendly Safecoin faucet (software) that pays out small amounts of Safecoin, but still enough for the average person’s message posting habits, in a manner that does not require fiddling around with addresses and other technical stuff (perhaps through integration with client apps through an API), or preferably a service (software) that allows people to post small amounts of data to the network without the user having to run a full node themselves, also interfaced with SAFE-based applications.
I’m aware the latter option could be a privacy risk for unencrypted content, though that could be mitigated by providing such a service as a Tor hidden service.
Both options could be protected from abuse by a proof-of-work scheme similar to Hashcash. Hashcash’s idea was to add proof-of-work to email, requiring people to spend CPU time for sending a message, making spam unprofitable because the average amount of money spent on an email would exceed the average amount of profit made with it, but not inconveniencing human users because of how small the amount actually is. My idea is to require proof of work to make running an actual SAFE node and either spending hardware resources or money cheaper and easier for larger amounts of data.
Any thoughts on this?