As a side note ... I did see that the field in the web page is set to 30 characters ...
On note ... if you limit it to 30 chars, do you still give enough space for the GPS coordinates, etc. that people are using? Where is a good place to lobby to have it fixed to a larger size? 120 chars? Something big enough that a "standard" could be developed to store multiple format locations? (e.g. common name + Lat/Lon ...) Curious ... On Mar 2, 9:03 am, Matt Sanford <[email protected]> wrote: > Hi there, > > The API wiki (http://apiwiki.twitter.com/REST+API+Documentation) > shows that the maximum size of 30 characters in the description of the > update_profile method. There is currently a bug where it allows longer > data and then after a day or so truncates it > (http://code.google.com/p/twitter-api/issues/detail?id=315 > ). I have a fix ready and am hoping to get it deployed today. > > Thanks; > — Matt Sanford > > On Mar 1, 2009, at 09:59 PM, TjL wrote: > > > > > On Sun, Mar 1, 2009 at 9:15 PM, Scott C. Lemon > > <[email protected]> wrote: > > >> What is the current maximum size of the location field? I've looked > >> around and have not yet found a doc that tells me what to expect. > > >> I want to ensure that I am caching the entire location string ... > > > I'd like to know that too. > > > The Location field seems to get truncated after a certain number of > > characters, but not immediately. > > > I've put in a long Location and had it work for awhile and then > > suddenly I notice that it's been shortened. I'm not sure if this is > > due to some app that I'm using which is truncating it or if Twitter > > does. > > > If it is Twitter it seems strange that it works for awhile. > > > FWIW > > > TjL
