Friday, 21st January 2011
Is there a way of tracking shortened URLs with Twitter streaming API?
Think about it like this: the whole point of the Twitter streaming API is to get you the tweets as soon after they are posted as possible. If the API were to provide access to the lengthened URLs, it would have to delay emitting a Tweet on to the stream until a resolver had gone through each shortened URL in the tweet and checked to find what it redirects to. This would mean that the speed with which the streaming API could deal out tweets would be dependent on the speed of the third party servers that serve up the redirects. I doubt Twitter would ever want to implement this.
[... 159 words]What programming conferences are in Romania in 2011?
How To Web looked like an excellent conference last year. They haven’t announced dates for 2011 yet but I’d keep an eye on their Twitter account:
[... 79 words]