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

Can't read the page because the twitter shoutbox gives an error...


Amazing that anybody would actually put 3rd party API code on the main execution path for rendering their site. What's the best case result? That your website renders correctly after only a 1 second pause?

This sort of widget is best lopped off entirely, or if you think it's absolutely essential, it's something that you load from javascript after all your resources have finished loading and rendering.

Never put your users' experience into the hands of a 3rd party. Other people's code is, nearly without exception, non-debugged, brittle garbage. Wrap it in four layers of try/catch and for the love of jebus, keep it out of your critical path.


Hell is other people's code?



And here's the straw that broke the camel's back:

    file_get_contents(http://api.twitter.com/1/statuses/user_timeline.xml?screen_name=williamMalone) [function.file-get-contents]: failed to open stream: HTTP request failed! HTTP/1.1 400 Bad Request in /home/content/w/i/l/willieohwillie/html/twitter/twitter-cacher.php on line 86

    Fatal error: Cannot use string offset as an array in /home/content/w/i/l/willieohwillie/html/header.php on line 319
Add some error handling and skip showing your timeline when this arises and be on your merry way.




Consider applying for YC's Summer 2026 batch! Applications are open till May 4

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

Search: