Sure, I live in the UK and I live in constant fear of the mighty US drone army. Our laws (a great deal of which predate the existence of the US) have no meaning.
"Nothing stopping the developer from paying out to users as well" - this is absolutely ridiculous; of course a developer with absolutely no payment infrastructure is going to start relaying these ill-gotten gains back to users. It just doesn't work like that.
Why all the hate? So far it just looks like a monetization tool to embed in a Chrome extension. Nothing says it's going to run there by default. We have no info on the presence or absence of compulsory disclaimers. Nor do we have any info about the default quotas of daily processing per install.
If the extension provides value to the user, it might be a way to compensate the provider for the said value. The same way ads compensate the provider of apps. In either case, computing time and bandwidth are used.
Now, having said that, if it ran 24/7 and used GBs of bandwidth per day on a single node, I would definitely side with you. But if it was embedded in a way where you get extra value once you enable it, that's another question.
To be a little clearer, I'm only completely against this when it's enabled within an extension by default; therefore crawling the web without the end users' knowledge.
If it's something you can enable, then it isn't so bad. This should ultimately be a choice that the user makes.
I absolutely love this! I've just created an account and have sent an invite to my co-founder & designer to sign up!
Hopefully we'll be using this for our day-to-day tasks - it seems like a much nicer solution to finding out what we're working on than checking in with each other throughout the day on Skype...
Thanks for the kind words. That's exactly what I was going for :)
If you ever need help, have questions or for whatever reason, find it's not working for you guys, I'd love to hear from you. You can always reach me at john at dayboard.
To me, this just seems a little silly. I can't imagine how difficult it will be to maintain a persistent, user-friendly account with this method. An emailed link every time a user wants to log in? Just plain silly.
Passwords are still widely used, and for good reason. I partially accept your point of passwords not being very secure, but why not just spend some time implementing a 2FA login method, instead of this?