Thanks for the reply!
I agree there is no such thing as a free lunch, and that it should be expected that there is some way for a website owner to pay to keep the site going. But that is not the same thing as saying that a website owner should just insert that code and not notify them of whats going on. Aside from the fact that this will undoubtedly land them in legal troubles, if there is a demand for the content then people will opt in. Current website monetization schemes such as the surveys are annoying because it interrupts the end goal of getting to the site. Ads are distracting/annoying as you have already pointed out, so I love the solution you have come up with. But please, please do not underestimate the push back you will encounter if you encourage website owners to do this in anything less than a completely open and transparent way. Let the user decide if they are ok with sharing their device resources. if not, either ask for money or give them adds, but don't try and sneak it in and hope they don't notice.
For point 4, i was more specifically asking about the cpu/gpu capabilities of the device but yes the internet connection would also be an important factor. I like that idea of ongoing resource evaluation because if I visited one of these sites and my computer started to slowdown I would probably stop going to that site.
Thanks,
John
Hi John,
I agree that transparency is productive. Oyster enables websites to notify users in a simple way that their CPU/GPU resources are being used in the place of advertisements and paywalls. In the end it is the responsibility of the website owner to perform this at their own discretion, Oyster is completely decentralized and cannot compel nor block any action across the network. The treasure hunting algorithm maintains the economic incentives for nodes to commit the data to the Tangle, but it isn't a centralized force that can compel users to perform various actions. Even if it were programmed to be insistent on transparency (with notifications), the end user could simply remove that part from the javascript without consequence.