Wow @blair_42 sounds much more animated in this replay.
RT @darrell: It’s pretty sad we’re still going after Apple, the company that’s doing the most for us right now when it comes to accessib …
@KG0BP Screw that guy. Augie is a service animal, so he takes priority.
Happenings For 2012-07-01 http://t.co/3zaAJu3Q
@wa4wga The purpose of the streaming API was so that clients wouldn’t exceed their 350 call limit.
@wa4wga I could see it in sent, but not home unless you have your client written so that it doesn’t eat API calls.
@wa4wga But then, most of the clients that employ it don’t have home stream. Just the other two buffers.
@wa4wga Great for mentions and DMs, not so much for home.
@wa4wga Yes. Twitter has a streaming API that will allow clients to grab tweets in real time.
@wa4wga From what I’ve heard, Twitmonger is trying to implement streaming for all buffers, and I think that only works sort of on Win7.
@wa4wga Yes that’s how it’s supposed to work.
@wa4wga I’m not sure. I’m not seeing it with the Qube, but haven’t tried Twitmonger.
@wa4wga No we don’t blame. He has been very forthcoming about this.
@wa4wga I haven’t used Twitmonger so it might very well live in XP.
@wa4wga The rest have been rip-offs of his code almost verbatem.
@wa4wga because Qwitter was written as a project by @mongoose_q while he was teaching himself Python.
@wa4wga The problem is that anyone who wants to write a new Twitter client needs to start from the ground up,
@wa4wga They all have major logic errors in their code that cause them to eat CPU cycles.
@wa4wga Uh, that sounds like a huge bug. But then, all these forks contain lots of them.
@wa4wga How many tweets did you have in the biggest buffer? Because it’ll grab the newest 200 at most.