Hacker News new | ask | show | jobs
by tjoff 3197 days ago
If this is not clearly opt-in I wish those responsible for using it on their site a slow and painful death.

Performance and bloat in browsers are a huge problem and having this constantly running in the background (without consent) is an absolute nightmare.

2 comments

I agree that there should be some sort of notification but other than that, I actually find this idea quite sympathetic. If you read my site, you can pay me by mining for me. It requires no extra effort on your part -- no credit card or micropayment login etc., and the longer you spend on my site, the more you pay. The exchange of value seems more clear cut that ads.
I have tons of sites opened 24/7. If yours happen to be loaded and you try to exploit my machines resources I will be quite pissed.
That's fair.

I suppose a more polite version would run only when the tab is in focus. But as has been pointed out, this doesn't seem feasible because of the tiny amount of value generated so I think it's an interesting idea to explore more than anything else.

Browsers throttle not active tabs.
Surely it's horrendously inefficient? That means my costs are much higher than the benefit you get from me, and a lot of energy is wasted.
2-5 cents per 24 hours of a user being on your site seems like a bad tradeoff for the downsides.
2-5 cents per 24 hours seems fairly equivalent to ads, actually.

Ad CPM (or more appropriately, RPM) seems to average somewhere around $2.50 (that's per thousand impressions). If these thousand users were on the site for 24 hours, that would be $20-$50, a more realistic scenario would be users on a site for a few minutes, generating comparable revenue to ad impressions.

On my desktop (which, not coincidentally, is where you'd have the best results trying to mine cryptocurrencies), I would honestly prefer this over tracking cookies, obnoxious and intrusive ads, extra network connections, and all that crap. And I run an ad-blocker, so this will let you get some revenue while ad RPM will be 0. On my phone or laptop using battery power, you're not going to have any success mining and I'm not going to want this. (I also run an ad blocker on those, so...yeah).

Your comparison doesn't take into account that 24 hours here means the user had to keep your tab open for 24 hours to make 2-5 cents.

That's nothing like ads.

Also, if the payment was higher than fractions of a cent, people would start "freezing" the site the moment it loaded - just as, back in the day, we disconnected our phone line modems as soon as the page we needed finished downloading, to avoid paying the phone company for time not spent transferring data.
With US electricity prices.

German electricity prices are north of 40ยข/kWh. This is significantly more expensive.

I calculated the site owners profit, not the cost to the user.
network calls for tracking and ads is already a huge performance problem on most sites, but it is still a thing
No reason not to treat it just as badly as attempts to mine bitcoin off your CPU. Both of those waste your resources, for someone else's profits, without your consent.
Devils advocate here.

Isn't just visiting the site giving consent to allow the sandbox (browser) to be utilized as the site directs?

This is an extreme case, granted, but it's still within the bounds of the sandbox.

Perhaps we'll have a new browser setting soon to throttle this type of thing instead of having to go whole hog and turn of JavaScript.

The implied consent is based on trust. The browser is my user agent, it is meant to interpret the data that it gets from HTTP stream the way I want it. I let it do the things as specified in the received data (i.e. by you), because I trust that you're not an asshole and will not abuse that power.

Unfortunately, there are plenty of assholes on-line, who decided to abuse the default behaviour - so now we have ad blockers and reader modes.

Ultimately, it is (by intention and design of the HTTP protocol, and computer networks in general) up to me what I do with the data - if, how, and which parts of it I decide to process.

It is giving consent, in some sense. But make a popular website use visitors' browsers to launch a DDoS attack and you'll find that "anything goes as long as it's the bounds of the sandbox" doesn't really apply.

Apart from that, people can easily take a different view altogether. When I visit a site, I download some bits. Doing so I don't consent to anything -- what I do with these bits is up to me.