When you watch ads and get data-mined do your really now how much value you pay? I don't think so, it's safe to safe that all of us have no clue about the price we indirectly pay for services we on internet, most of it is just free in appearance.
>How much 'currency' will be mined? Will it be proportional to the goods/services I get to use in exchange? How long will the process take? What if my system fails midway during 'payment'?
The norms are not established yet since it's a totally new way to monetize content on internet however how much you will pay will probably be determined in hashes. Here an example with a new blockchain (Nimiq) of a micropayment you could do: http://coinmiq.com/mine/eyJ3YWxsZXQiOiJOUTI3IFJDNUIgOUU1QSBT...
>This just smacks of convenience for the implementers and as for the user, it exchanges a straightforward system for a murky deal.
I disagree, in my opinion it opens an entire new way to do micropayments on the web.
You call the current ad-funded 'you get the service free but we secretly monetize everything about you' a straight-forward system?
This seems way more direct to me. Want to consume content? Run code in your browser while you do so.
I would honestly prefer more services and content creators asking for reasonable payments and more integration of multiple, seamless, international payment options into sites and services. Currently a major reason I don't pay for some services I otherwise would is because the payment process is very clunky or downright broken.
Ah, gotcha. TBF, most of the discussion around this is about replacing ad-funded models with browser-based mining, not replacing direct payments.
> I don't pay for some services I otherwise would is because the payment process is very clunky or downright broken.
This is a great reason to look harder at in-browser mining.
Electrical utilities have far lower payment processing costs than SAAS payment providers like Stripe. They also provide a way of aggregating many microtransactions in a way that credit-card networks actively try to prevent.
This just smacks of convenience for the implementers and as for the user, it exchanges a straightforward system for a murky deal.