This is a futurism exploration and a fun example of turning it into a game based on my last post. This is largely inspired by Jane McGonigal’s inspiring talk at GDC this year – about how game designers are the reality hackers of the future and how we will be called on to solve problems. So here goes:
Background
In the theoretical future, a major data collapse happens. A single service like Amazon S3 or one of those services to back up your personal data online falls to a natural disaster, manmade disaster or virus. Much like trust in the banks is an issue today, trust in services becomes an issue. It’s also just a plain-good optimization pattern, disaster or no, but sometimes people won’t move on something until after they should’ve so I pulled this scenario out of the blue as an example.
My solution is the cloud storage game. It’s also sort of a cloud processing and cloud throughput / latency solution (see last post) but for simplicity of example sake I’m going to focus on storage. It’s based on parity-driven data storage and delivery models like ZFS and BitTorrent. Let’s say you take a picture on your phone – it needs to be stored somewhere. It will of course also be stored on your phone, but that’s not enough because phones die and the data is lost for good.
ManyWhere Inc
Instead of storing it somewhere you store it ManyWhere (my name idea for this). A number of possible storage vendors are all available for you to store this data with a single API (ManyWhere API) bridging their APIs. However, as with all these systems, these cost money (in the cast of S3, transfer, request and storage over time are all charged). Also there’s the trust issue. Here’s where the ZFS-ish part comes in. You have some thick hardware lying around – so do your friends and people you would trust to hold onto something. Through a simple provider interface, they will store some of your data if you store some of theirs. So now when you store something you have a list of places it will go and a cost threshold. It will go to ALL of the places below the threshold. Imagine data being stored (in an encrypted or parity form of course) across your entire social network.
Adding Game to It
Now while companies charge money for this, your friends instead charge points. By providing storage or processing power for your friends you amass points from them. Your points are visible as a ‘who owes you’ breakdown as well as an amass of total points owed to you. You proudly display this on your social networks as a form of social capital realized. Other friends-of-friends can see that many other people trust you with their data, so you must also be fairly trustworthy. Local social networks and large groupings have leaderboards (this is again all based on offering up spare storage and cpu – so it’s of no real cost unless you decide to be philanthropic). In addition the number of parking wars -esque games that could be created on top of this is pretty epic.
Corporations and Causes
Ok, now we bring the companies back in. Companies can be both sources-of-last-resort (trust * cost = social cost) – if you trust them enough and their cost is low (or nothing) they might also make it in past your threshold. On the reverse side, companies may need storage or processing needs to offer in return for points. Those points may be microtrans equivalent values (virtual currencies) which may be redeemable by them or by partner vendors. For example, provide some extra CPU for big internet company A, redeem some virtual goods from MMO company B (a partner of A). The leaderboard concept still applies and is already gamey (SETI and Folding are two projects doing this RIGHT NOW with no direct incentive).
Results
The end result of all of this would require a descriptor system (looking at you bittorrent, zfs), and would require that this be either decentralized (a DNS-like system or extension would work), or a part of a service (whether hypothetical company ManyWhere, or more likely a partner project with someone like Google). However the ramifications are – less traffic and latency all around (using the description which is easily cacheable, you could always pull from a close, often local data/processing source), less storage and cpu costs for society in general (we’re not likely to ever move to a word of only thin clients – and due to that there are trillions of FLOPs and Gigabytes lying around dormant), a visualization of social capital mechanics (likely to breed its own decorum, but you can base some value decisions on it regardless), and an incentive for people to provide help to causes they care about (no one has to provide cpu to NastyMarketingCompany but many would choose to offer up social capital for HelpsFeedTheHomelessOrg).
There are some obvious technical limitations to the processing side (universal language – though that’s relatively solveable by bucketing the service into platforms), but the storage side is something people could work on NOW, so I think it at least deserves a PGI award (Pretty Good Idea). [Edit: This also requires to a certain degree an embrace of OpenID or something like it. Not from a technical side but from a society-accepting-distributed-trust-brokering side]
What do you think, internet?






