My name is Bruno and I'm the protocol designer and lead developer of Oyster. Oyster is a true 'two-birds-one-stone' project thats solves easy-access anonymous storage and traffic revenue generation. The Oyster protocol creates a set of network based economic circumstances which causes monetary value to flow from the pockets of those who want to spend on anonymous storage into the pockets of those who want to monetize their web content.
Adverts are distracting and invasive. They take up precious pixel space, often break the content and design continuity of websites, and are rarely politically neutral. Adverts must always be manually interpreted and approved for ethics compliance, therefore the system can never be fully decentralized. A famous example of a website that understands the inherent flaws in banner advertising is Wikipedia.
To illustrate the unseen economic potential of Oyster, imagine the potential revenue generation of Wikipedia. If Wikipedia enabled Oyster it would be able to pay for server costs without having to solicit their users for donations every year (which breaks design/space aesthetics like adverts and financially burdens the users themselves).
Payments to website owners are completely automated and decentralized, therefore no economic leverage is held against them.
If you have any questions please feel free to ask.
I love the idea behind this project and I hope you and your team succeed! I have a few questions that hopefully you can answer for me:
1. how do you communicate to users that this is happening and that they want to let you use their CPU/GPU? I know that the pirate bay did something like this just a few weeks ago for alt coin mining. A lot of people where very unhappy about this and felt it was very invasive.
2. (kind of a similar question to 1) how do you ask the users if they want to opt in or not? I assume that there will be an option not to allow the site to use your computer? Otherwise you are forced to not use the site if you don't want this to happen.
3. If a user chooses not to opt in, what would their website experience look like? Would it still have adds then?
4. how will the resources of the computer be evaluated and used? For example if I am on a mobile device vs a desktop how will the website determine how much resources each can provide? And how will you ensure that the users experience is smooth since, depending on how much resources the website uses the computer might start to slow down.
Thanks,
John