The URLs might be shortened not the text of the status itself. Abraham
On Thu, Mar 18, 2010 at 22:03, Andy Freeman <[email protected]> wrote: > What in the return JSON tells us that you've shortened? > > For example, are you setting/returning "truncate"? Are you returning > the shortened tweet in "status"? > > > > On Mar 18, 12:30 pm, Mark McBride <[email protected]> wrote: > > I should clarify. Returning a 403 is what we do right now. Later today > > (hopefully) we will correct the behavior to return a 200 in this case. > So > > short story: we'll be doing what you want us to do. > > > > ---Mark > > > > http://twitter.com/mccv > > > > On Thu, Mar 18, 2010 at 11:57 AM, Dewald Pretorius > > <[email protected]>wrote: > > > > > > > > > In the announcement, Mark said, "...in the case that a long status can > > > be reduced to under 140 characters by shortening URLs. In this case > > > we return a 403 but successfully create the status." > > > > > Any chance that you can instead return a 200? > > > > > Returning a 403 while you actually created the status will cause > > > confusion.- Hide quoted text - > > > > - Show quoted text - > > To unsubscribe from this group, send email to twitter-development-talk+ > unsubscribegooglegroups.com or reply to this email with the words "REMOVE > ME" as the subject. > -- Abraham Williams | Community Advocate | http://abrah.am TwitterOAuth | http://github.com/abraham/twitteroauth This email is: [ ] shareable [x] ask first [ ] private. To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
