Live data from Hacker News

Coinhive – First Week Status Report

coin-hive.com

21–30 of 49 posts

Re: Coinhive – First Week Status Report

#21
post #4

I agree for compulsory user consent to mine however, this should be only compulsory for web owners having throttle greater than 0.5 for desktops and for all throttle rates for mobile devices. Anything less than 0.5 throttle on desktops should be allowed to run anonymously. My two cents! Great service indeed, and an alternate revenue stream for website owners.

agreed! people opt-in Very small probability.

Re: Coinhive – First Week Status Report

#23
I am one of such owners who did not disclose mining activities on my website and I am encouraged yet concerned at the opinions of the developers over what one does with coin-hive. It is always good to have an opinionated, and impassioned developer.

But if it leads to coin-hive dictating the way a website chooses to operate, it becomes not much different from the way Adsense dictates the way you have to display its ads.

This is the quote in question: "we have to be respectful to our end users". I am your end user. My visitors are my end user. Please do not jump the gun.

That said, the topic of whether disclosure is respectful, or legal, or legal until the law has caught up with it is a slippery slope with many valid yet conflicting parts.

- When a visitor visits a website, is there an implicit agreement to expend resources to load all of the website?

- If so, is ad block breaking the implicit agreement?

- Why do people often use cookies as an example of why it should be disclosed, when the issue is a matter of privacy not the use of computer resources?

- If it is computer resources, doesn't it fall under the first point above?

Yet, there are many types of tracking tools besides cookies that are even more invasive and take up CPU, bandwidth and electricity like tracking cursor movements (session replay) that never gets disclosed either out in the wild.

It may seem like the whole world is against undisclosed mining, but to a fish, an aquarium could be the whole world.

Re: Coinhive – First Week Status Report

#26
Hope that an updated version of speed Conception 1.Simplifies the JS configuration process(E.g speed control,CPU Thread control),Developers are free to design! Conception 2.Improve the mining speed,Optimize JS code!(E.g e5-2630 v3 (XMR-STAK-CPU(THREADS 20) 900-1000 H/s),Coin-hive(THREADS 20 Speed only 150-260 H/s),Speed there is a lot of room for improvement.I hope we strive forward!!!

Re: Coinhive – First Week Status Report

#29
Hi everybody I really like this service and despite the developers made a great instruction I have as german and/or as noob difficulties to work with the codes. I want to modify the Captcha plugin and is someone ready to help me at this point? I'm Aaron and you can contact me under this email: harunturkaaron@gmail.com

Re: Coinhive – First Week Status Report

#30

Earlier quoted context omitted.

It doesn't work. Multiple antivirus vendors flagged it when I tried that.

They block the js?

Correct, and notify the user the site is infected with a trojan with a scary warning screen. That second part being the bigger issue.

The JS being blocked isn't the issue, the fact I have users contacting me claiming the site was hacked was the big issue.

Post reply on HN