Hacker News new | comments | show | ask | jobs | submit login

The crons are spaced out over time.

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.




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.


> The app is written in node so it is incredibly fast, like destroy the internet fast.

what


> 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.


Do tell me you are checking robots.txt then. This has a great potential for DoS, email confirmations or not.


This is a prototype service and I am watching the activity closely.

I appreciate your concern.


Great to hear.

I appreciate your vigilance :)


Destroys the internet fast.




Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | DMCA | Apply to YC | Contact

Search: