News for hackers. Stuff that matters.
Re:Making a case for JavaScript, in-browser Mining by mido22 on Thursday February 15, 2018 @08:35AM (#16383836)
I think it is not a bad idea, imagine the mining is taking place only when the page is active and (max) 5 - 10$ on your electricity bill split among all the publisher, a much better alternative to ads if you ask me.
Re:Making a case for JavaScript, in-browser Mining by ulrikrasmussen on Thursday February 15, 2018 @08:41AM (#16383870)
Except it doesn't really play well together with battery-powered devices.
Re:Making a case for JavaScript, in-browser Mining by tazard on Thursday February 15, 2018 @08:55AM (#16383960)
How about disabling on battery devices then?
Re:Making a case for JavaScript, in-browser Mining by berkes on Friday February 16, 2018 @03:12AM (#16390742)
This is what I -somewhat- did in the example: I've disabled it for mobile. I don't think browsers have an API to detect what power-source the underlying machine is using, though.
Re:Making a case for JavaScript, in-browser Mining by berkes on Saturday February 17, 2018 @03:28AM (#16399714)
Turns out that the disabling did not work.

It is possible to detect mobile and disable it completely, but for now, because it's mostly demo material, I'll leave it enabled for mobile too. In a real-world scenario you'd probably show a message or explain why a mobile user cannot use it. That would certainly give you credits.

Re:Making a case for JavaScript, in-browser Mining by amelius on Thursday February 15, 2018 @09:02AM (#16384004)
Then everybody would unplug their laptops to save on their energy bill.
Re:Making a case for JavaScript, in-browser Mining by ChrisSD on Thursday February 15, 2018 @09:08AM (#16384044)
Is there a battery API for websites? The old one was deprecated because it caused too many issues (e.g. with fingerprinting).
Re:Making a case for JavaScript, in-browser Mining by gruez on Thursday February 15, 2018 @09:19AM (#16384123)
But the $5 in electricity costs would only earn $3 (random guess) of cryptocurrency, making the whole scheme a convoluted and very inefficient money transfer mechanism.
Re:Making a case for JavaScript, in-browser Mining by philipodonnell on Thursday February 15, 2018 @09:38AM (#16384272)
You'll probably want to have more than a random guess to claim that the money spent on electricity has a negative ROI.
Re:Making a case for JavaScript, in-browser Mining by gruez on Thursday February 15, 2018 @09:54AM (#16384438)
mainly because:

* javascript miners operate at a fraction of the efficiency of native miners (I don't have exact numbers, but I vaguely remember somewhere between 1/2 to 2/3)

* "professional" (ie. non-javascript) miners use high end CPUs, whereas the typical user might be on a i3 or ARM device. this matters because monero mining gets a significant performance boost from a bigger cache.

* "professional" mining pools have fees of ~1%. coinhive has a fee of 30%.

* mining is competitive market, where profit margins are low.

I actually didn't know that coinhive's fee was that high. that alone means $3 of every $10 is "lost" as transaction fees.

Re:Making a case for JavaScript, in-browser Mining by philipodonnell on Thursday February 15, 2018 @10:10AM (#16384579)
If you aren't specifying the cost per KW/h and the financial benefit per KW/h, then you are just making assumptions about how the finances work within the context of the current market structure and participants.

None of these things leads to the conclusion that there isn't an arrangement whereby a website visitor can dedicated x seconds to mining and end up paying a reasonable amount in incremental electricity costs for doing so while providing a third-party with a sufficient financial benefit to compensate for the cost of the content consumed/service provided.

Re:Making a case for JavaScript, in-browser Mining by blocksceptic on Thursday February 15, 2018 @11:37AM (#16385352)
Even if it makes sense today, if the approach became commonplace, it would become a lot less effective, as it would require a commensurate and sustained increase of the value of the relevant cryptocurrency for the $0.02/hour that is currently generated by one user to not drop to $0.0002/hour once 100x as many users are participating.

This barely makes sense today, where are your hard numbers showing how this will work if we try to fund journalism by throwing a coinhive script onto nytimes.com?

Tech people love these sorts of things, because it allows us to pretend we've solved a tough social problem (how do we pay for journalism) with a neat cryptographic hashing algorithm, when in reality we've just invented a horribly inefficient way to add hidden micro-transactions to our end user's power bills.

Re:Making a case for JavaScript, in-browser Mining by philipodonnell on Thursday February 15, 2018 @01:01PM (#16386078)
If we are talking about whether a specific existing technology will make this all work, then I agree, I have no hard data to back that up.

But the article is talking about the idea of a cryptocurrency which is mined in the browser as a potential area of exploration for a way to allow a publisher to directly monetize their users electrical resources in return for products or services.

Most of these comments are looking only through the lens of what exists today and assuming that the only implementation is a direct you-mine-coin-you-pay-with-your-coin-who's-value-to-USD-fluctuates. There is no reason a system would need to do that.

It would be just as feasible for a publisher to grant access to the service based on the time the miner is running above some speed threshold not its total cumulative speed, even if the cumulative speed is what is generating value for the publisher. The threshold becomes the fixed price, and fixed prices across customers who provide variable levels of value to a company are common.

Re:Making a case for JavaScript, in-browser Mining by gruez on Thursday February 15, 2018 @11:56AM (#16385537)
https://pastebin.com/raw/get88jbH

best case scenario (xeon): you pay a 15% fee to transfer your electricity costs the site owner

worser case scenario (atom): you pay a 64% fee to transfer your electricity costs the site owner

Re:Making a case for JavaScript, in-browser Mining by philipodonnell on Thursday February 15, 2018 @01:05PM (#16386121)
I'm not contesting you, I agree, these don't seem like compelling financial transactions. There's just no reason to assume that such a system has to be a mine-and-then-pay-with-what-you-mined-in-USD-equivalent even though that's all that exists today.

More useful would be a 'pay by letting us consume some fixed amount of electricity by doing some mining with your browser'. The difference between what you paid for electricity and what the company is providing you in products/services determines your cash cost, and is different for every person.

That's all POW cryptos are anyway, buying electricity and turning it into a coin that then sells for cash. The worst case would be if you had to pay in cash because its so slow, so then it became just paying with the coin directly, so why not go back further and pay with the electricity directly and let the publisher deal with mining and coins and such?