I guess I need to look at the "protocol buffers" spec again. And some of the "binary JSON" formats. While we're dreaming, how about sending Streaming data *compressed*? ;-)
On Apr 15, 7:49 am, Raffi Krikorian <[email protected]> wrote: > a way to think about this is analogous to geo. people used to put geo > information in the 140 characters -- but now, we allow you to put it out of > band in a machine-readable way. we want to extend that functionality to all > types of meta data (links to URLs, etc.). > > 2010/4/15 André Luís <[email protected]> > > > > > Why shorten links that won't count for 140 limit and are not viewed by > > user? It will only add un-needed requests and waste values on the twiter > > shortener. > > > André Luís > > > On Apr 15, 2010 2:18 p.m., "M. Edward (Ed) Borasky" <[email protected]> > > wrote: > > > I'm thinking of something like the RFC process for Internet protocols. > > By the way, on a related note, once the "Twitter link shortener" I've > > been hearing rumors about is in place, can we have all the links in > > tweets sent from the API shortened with it? Profile images, user > > object URLs, etc. ;-) > > > Part of this stems from my concern over something I thought I heard > > yesterday about Twitter building its own "place" database. There are > > dozens of place databases - why does Twitter need another one? > > > On Apr 15, 6:05 am, Raffi Krikorian <[email protected]> wrote: > > > > please feel free to point us to standards that you would like us to > > > consider. we are really att... > > > > On Thu, Apr 15, 2010 at 12:09 AM, <[email protected]> wrote: > > > > > > ----- "Jud" <[email protected]> wrote: > > > > On Apr 14, 5:05 pm, > > James Teters <jtet...@gmail.... > > -- > Raffi Krikorian > Twitter Platform Teamhttp://twitter.com/raffi
