Re:Show HN: Cron.io - Sharing a by-product. Should this be a...
by Erwin on Tuesday February 07, 2012 @03:41AM
(#3561019)
Alternatively you could get the user to validate ownership of a domain, i.e. if you want to run jobs at http://foo.com/something, tell them to create http://foo.com/cronio.txt with specific contents.
Google does something like this: http://support.google.com/a/bin/answer.py?hl=en&answer=6... -- their alternatives also include changing DNS to add a dummy TXT record.
Re:Show HN: Cron.io - Sharing a by-product. Should this be a...
by StavrosK on Tuesday February 07, 2012 @03:46AM
(#3561031)
> The app is written in node so it is incredibly fast, like destroy the internet fast.
what
Re:Show HN: Cron.io - Sharing a by-product. Should this be a...
by iambot on Tuesday February 07, 2012 @06:35AM
(#3561355)
> The app is written in node so it is incredibly fast, like destroy the internet fast.
haha I actually like that line a lot. Describes exactly how I feel whenever I'm using node.
Re:Show HN: Cron.io - Sharing a by-product. Should this be a...
by eps on Tuesday February 07, 2012 @02:58AM
(#3560929)
Do tell me you are checking robots.txt then. This has a great potential for DoS, email confirmations or not.
Re:Show HN: Cron.io - Sharing a by-product. Should this be a...
by coenhyde on Tuesday February 07, 2012 @03:04AM
(#3560939)
This is a prototype service and I am watching the activity closely.
I appreciate your concern.
This is actually why i took so long to launch the site. I've used the prototype version of this for a long time. The app is written in node so it is incredibly fast, like destroy the internet fast. That is why email confirmations are required and accounts are limited to 5 crons each. I will add a captcha on account confirmation shortly as well.