4 ms·
On second thought, http://blog.twitter.com/2009/12/dns-disruption.html http://blog.twitter.com/2009/12/dns-disruption.html says twitter.com was redirected, yet
by tlrobinson 17y ago
On second thought, http://blog.twitter.com/2009/12/dns-disruption.html 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.
- timdorr 17y agoProbably cached DNS. A lot of providers extend the TTL, despite what you have it set at.
- randallsquared 17y agoA lot of providers extend the TTL, despite what you have it set at. ...which is very annoying when you're moving a business site. :/
- jrockway 17y agoIndeed. But the user's ISP is the problem, so technically you are not to blame.
- randallsquared 17y agoTechnically true, but it doesn't stop my client from being upset that their user claims my client's site is down. :)
- jrockway 17y agoIndeed. 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 :)
- randallsquared 17y agoI'm glad that I don't (directly) any more, either. :)
- wendroid 17y agoon third thought http://apiwiki.twitter.com/Things-Every-Developer-Should-Kno.. 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 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!)