Earlier quoted context omitted.
There is an opt-in: http://cdn.crowdprocess.com/opt-in.html (only one website requested it so it's not in English so far). It's as immoral as advertising, maybe even less. In advertising you show up at a web page and see tons of things that you did not want to see or did not bring you to that web page, sometimes shift your focus and annoys you. It's the same with CrowdProcess, except instead of annoying you, we annoy…
> It's as immoral as advertising, maybe even less. You've actually managed to convince yourself that, haven't you? It isn't because: 1: the user is paying for the electricity being wasted by you. A tab left open could be significantly detrimental. 2: it will cause real problems for mobile users who will be wondering why their battery's flat.
Ask HN: What would you compute on 2000 badly behaved worker nodes?
21–29 of 29 posts
Re: Ask HN: What would you compute on 2000 badly behaved worker nodes?
#22Earlier quoted context omitted.
>>We actually ask websites to tell they're a part of this, but we cannot control what they do because they can simply display:none. You could certainly just check to see they're using it properly. Do a screen scrape or even have someone hit the page every month or two, ban anyone abusing it by not notifying users.
that may be harder to do efficiently than building the entire platform and we're an extremely small team. I'm sure some day we'll do it but can't prioritize that now.
If you can't prioritize something as important as running an ethical (and law abiding - take a very close look at the ramifications of unauthorized computer usage, which I think it could be argued you're doing with this platform) business, then you really shouldn't be in business.
Re: Ask HN: What would you compute on 2000 badly behaved worker nodes?
#23Hmm. It's not clear from your documentation, is it possible to use xmlhttprequest through the web workers and get the response? Because having thousands of systems as distributed web crawlers would be really really cool.
It's not possible, sorry. It's possible if you ask us to access a certain address, but to the outside world it's not allowed. It would be pretty cool to have distributed web crawlers but it would also be extremely dangerous if someone decided to use CrowdProcess to do a DDoS.
Re: Ask HN: What would you compute on 2000 badly behaved worker nodes?
#24What you're saying is that you have a botnet. Look at botnet owners.
That's actually pretty good advice, except it may be hard to find legal and moral things to run. We wanted to find the cure for cancer and not produce rainbow tables or do DDoS attacks.
Re: Ask HN: What would you compute on 2000 badly behaved worker nodes?
#25Re: Ask HN: What would you compute on 2000 badly behaved worker nodes?
#26Earlier quoted context omitted.
that may be harder to do efficiently than building the entire platform and we're an extremely small team. I'm sure some day we'll do it but can't prioritize that now.
Really? How many websites are signed up / do you expect to sign up? Can you not spare 5 minutes per site per month to make sure there's a notification and/or opt-in? Or come up with an automated way to check it. Or use mechanical turk and pay somebody $0.50 per site to check for you. If you can't prioritize something as important as running an ethical (and law abiding - take a very close look at the ramifications of…
The incentives must be: if you do not comply, your content won't be monetized (as would happen with ads).
Re: Ask HN: What would you compute on 2000 badly behaved worker nodes?
#27Re: Ask HN: What would you compute on 2000 badly behaved worker nodes?
#28Earlier quoted context omitted.
That's actually pretty good advice, except it may be hard to find legal and moral things to run. We wanted to find the cure for cancer and not produce rainbow tables or do DDoS attacks.
It's also hard to find legal and moral justification for constructing a botnet in the first place.
Re: Ask HN: What would you compute on 2000 badly behaved worker nodes?
#29I checked the FAQ, but didn't see an answer -- how do you prevent malicious actors from returning bogus data?