Profile_bird

Hey there! itwtr is using Twitter.

Twitter is a free service that lets you keep in touch with people through the exchange of quick, frequent answers to one simple question: What's happening? Join today to start receiving itwtr's tweets.

Already using Twitter
from your phone? Click here.

itwtr

  1. You can try out the new iTwtr prototype at http://v2.itwtr.com/
  2. Started work on iTwtr 2.0. It's going to be a total complete rewrite, with a different approach: JsonP + client-side storage (no backend!)
  3. @bk_whopper Sounds like a bug. I think it's kind of a fundamental bug with how iTwtr gets its content. I need to switch some stuff around.
  4. @bk_whopper That's weird, you don't see any tweets at all, or it doesn't update with the very newest ones?
  5. @benkreeger That particular line can be safely commented out, but there are other PHP5 dependencies. Especially the SimpleXML parsing.
  6. That means I will approximate the friend timeline by using cron + API to include private profiles and those w/o profile images.
  7. So it's been a week since I posted v1.4. I've been playing with Jabber/XMPP tweet delivery. Way more efficient, but trickier to build. Soon!
  8. Just posted a "zombie tweet." It's in my iTwtr database, but it didn't make it onto Twitter.com. Probably due to being over my usage limit.
  9. Posted version 1.4. Release notes here: http://itwtr.com/1.4.txt
  10. Oh, right, a possible third route is that they might provide an *actual* friend timeline over Jabber. No clue when that might happen though.
  11. But the bottom line is that cron + API for everything won't scale up at all. Two possible routes: not-a-hosting-service or hacky Jabber.
  12. I could approximate a friend timeline, but it would still require cron + API for those with private accounts or no profile image.
  13. So I've been researching the Jabber thing. One other weird contingency is that it only broadcasts tweets from users with profile images.
  14. Posted version 1.3. Release notes here: http://itwtr.com/1.3.txt
  15. After testing a bit on another machine, it seems the long running API calls are due to Twitter and not my shared hosting.
  16. Posted version 1.2. Release notes here: http://itwtr.com/1.2.txt
  17. Still getting freakishly long connection times. One call took 100 sec according to cron notification. Not sure if it's Dreamhost or Twitter.
  18. Last night I was getting cron emails once a minute, complaining about 50+ sec API calls. Possible solution: bail after 5 seconds of waiting.
  19. The alternative is running a Jabber/XMPP server, but that method will only work for public tweets. Maybe that's good enough for most people?
  20. Coming to terms with the inherent scaling limitations of cron + Twitter API. A significant boost in users will probably break itwtr.