Hi everyone,
As of this morning (CEST) we started seeing some errors in our logs
due to User objects in status messages representing retweets being in
compact form (id only) e.g.
curl api.twitter.com/1/statuses/show/25002162945.json | jeg -p
{
coordinates: null,
favorited: false,
self-reply: apparently, when asking the same status in XML format we
get all the fields, and other retweets seem to contain the full user
object, so this seems more of a glitch on twitter's side.
Again, if we have missed some change in the API spec, I'd be happy to
hear about it and I'm sorry for
Hi everyone,
I am noticing that my home timeline and that of a few other people is
returning some messed up stuff,
basically intemingling something that looks like a random sequence of
bytes to normal messages.
You can in theory verify this by accessing my home timeline
(@riffraff) and
* What is an annotation more exactly exactly?
First off let's be clearer about what an annotation is. An annotation is a
namespace, key, value triple. A tweet can have one or more annotations.
Namespaces can have one or more key/value pairs.
first, annotations are cool, thanks. But why
On Fri, Apr 16, 2010 at 8:51 PM, Marcel Molina mar...@twitter.com wrote:
More namespace nesting would of course increase people's ability to
taxonomize. It's a splippery slope though and we are trying to balance
expressiveness with simplicity. Providing for arbitrarily nested namespaces
On Fri, Apr 16, 2010 at 9:21 PM, dhavaln dhaval.b.na...@gmail.com wrote:
but this will create islands of information and information retrieval
based
on annotations will be difficult for other applications.
i.e. amazon.com:book-rating{isbn:34345434, rating: 5}
it should be easier for other
On Fri, Oct 2, 2009 at 12:18 PM, Chad Etzel c...@twitter.com wrote:
Thanks, Gabriele. Fixed!
glad to be helpful, but it's only fixed in one of the two sentences,
check the above one :)
Hi everyone,
I'm in the process of implementing a consumer for the streaming API,
but while perusing the documentation I noticed an inconsistency in
http://apiwiki.twitter.com/Streaming-API-Documentation
When a network error (TCP/IP level) is encountered, back off linearly.
Perhaps start at
