Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

On second thought, http://blog.twitter.com/2009/12/dns-disruption.html says twitter.com was redirected, yet the API still worked.

Since the API uses the twitter.com domain name, unless I'm missing something the only way that's possible is if the API was being man-in-the-middled.

Something doesn't add up.



Probably cached DNS. A lot of providers extend the TTL, despite what you have it set at.


A lot of providers extend the TTL, despite what you have it set at.

...which is very annoying when you're moving a business site. :/


Indeed. But the user's ISP is the problem, so technically you are not to blame.


Technically true, but it doesn't stop my client from being upset that their user claims my client's site is down. :)


Indeed. If your site is down because of the user's error, but they can still get to your competitor's site, then that's bad for you. It might not be your fault, but you still missed out on a potential sale.

All I can say is that I am glad I do not make money from the availability of websites :)


I'm glad that I don't (directly) any more, either. :)


on third thought

http://apiwiki.twitter.com/Things-Every-Developer-Should-Kno....

Post a status update and get the resulting status back as JSON: curl -u username:password -d status="your message here" http://twitter.com/statuses/update.json

what it doesn't tell you is that it sends the pw in the clear (unless you count base64 as crypto!)




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: