[twitter-dev] Re: New behaviour for statuses/update API call for 141+ char sized messages and duplicates?
Of course it is a bug. On Oct 26, 4:33 pm, Kevin Menard wrote: > Thanks for the info, Dave. > > Although, the fact that the current behavior does not match the API > docs does make it a bug. Whether that bug is in the implementation or > the docs is really what's up for grabs. > > -- > Kevin > > On Oct 24, 6:39 am, Dave Sherohman wrote: > > >http://groups.google.com/group/twitter-development-talk/browse_thread.. > > > These are deliberate changes on Twitter's part, so they are not bugs. > > Whether they are features depends on who you ask... > > > As it currently stands, you must either check the returnedstatusID to > > see if it's higher than previous IDs or compare the submittedstatusto > > the returnedstatus(ignoring URLs) to determine whether theupdatewas > > actually successful or if it was silently rejected by Twitter. > > > Hopefully, in the (very near) future, Twitter will start providing some > > indication in the response that will make it simple and reliable to > > determine when anupdatehas been rejected without requiring app > > developers to try to figure that out on our own, but, so far as I am > > aware, Twitter has not yet made any statement regarding this. > > > On Fri, Oct 23, 2009 at 08:53:16AM -0700, Kevin Menard wrote: > > > > Hi, > > > > I'm seeing the same thing that Ole is. Twitter is not truncating the > > >status, but rather returning the last correctly updatedstatus. > > > > -- > > > Kevin > > > > On Oct 16, 4:58 am, janole wrote: > > > > According to my tests, messages will not be truncated anymore! > > > > > Instead, you will get the most recentstatusupdateas a reply. > > > > > Is this a bug or feature? > > > > > Also, it seems as if the API now checks for duplicates in your > > > > "backlog" ofstatusesand not just you most recent tweet. > > > > > Previously, only the last tweet was checked: > > > > > - Last tweet "test" > > > > - Send new tweet with "status=test" will return the oldstatus(with > > > > the old status_id) > > > > > but if you had something like this: > > > > > Last tweet "Hello, world." > > > > Second last tweet "test" > > > > > Then you were able to create a new tweet with "status=test"! > > > > > This is not possible at the moment. > > > > > Bug or feature? > > > > > I'm getting a lot of complaints from my Twitter client users who > > > > apparently experience both of these new "behaviours" or "bugs" (long > > > > tweets fail, duplicates fail.) > > > > > Ole @ mobileways.de > > > > On Twitter:http://twitter.com/janole > > > > > On Oct 15, 8:26 pm, Josh Roesslein wrote: > > > > > > If you send a message longer than 140 twitter will truncate it and set > > > > > the truncate value on thestatusto True. > > > > > For duplicates it will just ignore thestatus. > > > > > > Josh > > > > > > On Thu, Oct 15, 2009 at 1:20 PM, janole wrote: > > > > > > > Hi, > > > > > > > I just figured out that when callingstatuses/updatewith a text > > > > > > longer than 140 chars, the reply of that API call will be 200 OK > > > > > > with > > > > > > the laststatusof the user. > > > > > > > Wouldn't it be better to return some sort of error message? > > > > > > > The same seems to be happening when sending a duplicate tweet. > > > > > > > Ole > > > > > > > -- > > > > > > Jan Ole Suhr > > > > > > s...@mobileways.de > > > > > > On Twitter:http://twitter.com/janole > > > -- > > Dave Sherohman
[twitter-dev] Re: New behaviour for statuses/update API call for 141+ char sized messages and duplicates?
Thanks for the info, Dave. Although, the fact that the current behavior does not match the API docs does make it a bug. Whether that bug is in the implementation or the docs is really what's up for grabs. -- Kevin On Oct 24, 6:39 am, Dave Sherohman wrote: > http://groups.google.com/group/twitter-development-talk/browse_thread...http://groups.google.com/group/twitter-development-talk/browse_thread... > > These are deliberate changes on Twitter's part, so they are not bugs. > Whether they are features depends on who you ask... > > As it currently stands, you must either check the returnedstatusID to > see if it's higher than previous IDs or compare the submittedstatusto > the returnedstatus(ignoring URLs) to determine whether theupdatewas > actually successful or if it was silently rejected by Twitter. > > Hopefully, in the (very near) future, Twitter will start providing some > indication in the response that will make it simple and reliable to > determine when anupdatehas been rejected without requiring app > developers to try to figure that out on our own, but, so far as I am > aware, Twitter has not yet made any statement regarding this. > > > > > > On Fri, Oct 23, 2009 at 08:53:16AM -0700, Kevin Menard wrote: > > > Hi, > > > I'm seeing the same thing that Ole is. Twitter is not truncating the > >status, but rather returning the last correctly updatedstatus. > > > -- > > Kevin > > > On Oct 16, 4:58 am, janole wrote: > > > According to my tests, messages will not be truncated anymore! > > > > Instead, you will get the most recentstatusupdateas a reply. > > > > Is this a bug or feature? > > > > Also, it seems as if the API now checks for duplicates in your > > > "backlog" of statuses and not just you most recent tweet. > > > > Previously, only the last tweet was checked: > > > > - Last tweet "test" > > > - Send new tweet with "status=test" will return the oldstatus(with > > > the old status_id) > > > > but if you had something like this: > > > > Last tweet "Hello, world." > > > Second last tweet "test" > > > > Then you were able to create a new tweet with "status=test"! > > > > This is not possible at the moment. > > > > Bug or feature? > > > > I'm getting a lot of complaints from my Twitter client users who > > > apparently experience both of these new "behaviours" or "bugs" (long > > > tweets fail, duplicates fail.) > > > > Ole @ mobileways.de > > > On Twitter:http://twitter.com/janole > > > > On Oct 15, 8:26 pm, Josh Roesslein wrote: > > > > > If you send a message longer than 140 twitter will truncate it and set > > > > the truncate value on thestatusto True. > > > > For duplicates it will just ignore thestatus. > > > > > Josh > > > > > On Thu, Oct 15, 2009 at 1:20 PM, janole wrote: > > > > > > Hi, > > > > > > I just figured out that when calling statuses/updatewith a text > > > > > longer than 140 chars, the reply of that API call will be 200 OK with > > > > > the laststatusof the user. > > > > > > Wouldn't it be better to return some sort of error message? > > > > > > The same seems to be happening when sending a duplicate tweet. > > > > > > Ole > > > > > > -- > > > > > Jan Ole Suhr > > > > > s...@mobileways.de > > > > > On Twitter:http://twitter.com/janole > > -- > Dave Sherohman
[twitter-dev] Re: New behaviour for statuses/update API call for 141+ char sized messages and duplicates?
http://groups.google.com/group/twitter-development-talk/browse_thread/thread/cd95ce07be341223/66c66de585383868#66c66de585383868 http://groups.google.com/group/twitter-development-talk/browse_thread/thread/3d6a727892710d5e# These are deliberate changes on Twitter's part, so they are not bugs. Whether they are features depends on who you ask... As it currently stands, you must either check the returned status ID to see if it's higher than previous IDs or compare the submitted status to the returned status (ignoring URLs) to determine whether the update was actually successful or if it was silently rejected by Twitter. Hopefully, in the (very near) future, Twitter will start providing some indication in the response that will make it simple and reliable to determine when an update has been rejected without requiring app developers to try to figure that out on our own, but, so far as I am aware, Twitter has not yet made any statement regarding this. On Fri, Oct 23, 2009 at 08:53:16AM -0700, Kevin Menard wrote: > > Hi, > > I'm seeing the same thing that Ole is. Twitter is not truncating the > status, but rather returning the last correctly updated status. > > -- > Kevin > > On Oct 16, 4:58 am, janole wrote: > > According to my tests, messages will not be truncated anymore! > > > > Instead, you will get the most recentstatusupdateas a reply. > > > > Is this a bug or feature? > > > > Also, it seems as if the API now checks for duplicates in your > > "backlog" of statuses and not just you most recent tweet. > > > > Previously, only the last tweet was checked: > > > > - Last tweet "test" > > - Send new tweet with "status=test" will return the oldstatus(with > > the old status_id) > > > > but if you had something like this: > > > > Last tweet "Hello, world." > > Second last tweet "test" > > > > Then you were able to create a new tweet with "status=test"! > > > > This is not possible at the moment. > > > > Bug or feature? > > > > I'm getting a lot of complaints from my Twitter client users who > > apparently experience both of these new "behaviours" or "bugs" (long > > tweets fail, duplicates fail.) > > > > Ole @ mobileways.de > > On Twitter:http://twitter.com/janole > > > > On Oct 15, 8:26 pm, Josh Roesslein wrote: > > > > > > > > > If you send a message longer than 140 twitter will truncate it and set > > > the truncate value on thestatusto True. > > > For duplicates it will just ignore thestatus. > > > > > Josh > > > > > On Thu, Oct 15, 2009 at 1:20 PM, janole wrote: > > > > > > Hi, > > > > > > I just figured out that when calling statuses/updatewith a text > > > > longer than 140 chars, the reply of that API call will be 200 OK with > > > > the laststatusof the user. > > > > > > Wouldn't it be better to return some sort of error message? > > > > > > The same seems to be happening when sending a duplicate tweet. > > > > > > Ole > > > > > > -- > > > > Jan Ole Suhr > > > > s...@mobileways.de > > > > On Twitter:http://twitter.com/janole -- Dave Sherohman
[twitter-dev] Re: New behaviour for statuses/update API call for 141+ char sized messages and duplicates?
Hi, I'm seeing the same thing that Ole is. Twitter is not truncating the status, but rather returning the last correctly updated status. -- Kevin On Oct 16, 4:58 am, janole wrote: > According to my tests, messages will not be truncated anymore! > > Instead, you will get the most recentstatusupdateas a reply. > > Is this a bug or feature? > > Also, it seems as if the API now checks for duplicates in your > "backlog" of statuses and not just you most recent tweet. > > Previously, only the last tweet was checked: > > - Last tweet "test" > - Send new tweet with "status=test" will return the oldstatus(with > the old status_id) > > but if you had something like this: > > Last tweet "Hello, world." > Second last tweet "test" > > Then you were able to create a new tweet with "status=test"! > > This is not possible at the moment. > > Bug or feature? > > I'm getting a lot of complaints from my Twitter client users who > apparently experience both of these new "behaviours" or "bugs" (long > tweets fail, duplicates fail.) > > Ole @ mobileways.de > On Twitter:http://twitter.com/janole > > On Oct 15, 8:26 pm, Josh Roesslein wrote: > > > > > If you send a message longer than 140 twitter will truncate it and set > > the truncate value on thestatusto True. > > For duplicates it will just ignore thestatus. > > > Josh > > > On Thu, Oct 15, 2009 at 1:20 PM, janole wrote: > > > > Hi, > > > > I just figured out that when calling statuses/updatewith a text > > > longer than 140 chars, the reply of that API call will be 200 OK with > > > the laststatusof the user. > > > > Wouldn't it be better to return some sort of error message? > > > > The same seems to be happening when sending a duplicate tweet. > > > > Ole > > > > -- > > > Jan Ole Suhr > > > s...@mobileways.de > > > On Twitter:http://twitter.com/janole
[twitter-dev] Re: New behaviour for statuses/update API call for 141+ char sized messages and duplicates?
According to my tests, messages will not be truncated anymore! Instead, you will get the most recent status update as a reply. Is this a bug or feature? Also, it seems as if the API now checks for duplicates in your "backlog" of statuses and not just you most recent tweet. Previously, only the last tweet was checked: - Last tweet "test" - Send new tweet with "status=test" will return the old status (with the old status_id) but if you had something like this: Last tweet "Hello, world." Second last tweet "test" Then you were able to create a new tweet with "status=test"! This is not possible at the moment. Bug or feature? I'm getting a lot of complaints from my Twitter client users who apparently experience both of these new "behaviours" or "bugs" (long tweets fail, duplicates fail.) Ole @ mobileways.de On Twitter: http://twitter.com/janole On Oct 15, 8:26 pm, Josh Roesslein wrote: > If you send a message longer than 140 twitter will truncate it and set > the truncate value on the status to True. > For duplicates it will just ignore the status. > > Josh > > On Thu, Oct 15, 2009 at 1:20 PM, janole wrote: > > > Hi, > > > I just figured out that when calling statuses/update with a text > > longer than 140 chars, the reply of that API call will be 200 OK with > > the last status of the user. > > > Wouldn't it be better to return some sort of error message? > > > The same seems to be happening when sending a duplicate tweet. > > > Ole > > > -- > > Jan Ole Suhr > > s...@mobileways.de > > On Twitter:http://twitter.com/janole
[twitter-dev] Re: New behaviour for statuses/update API call for 141+ char sized messages and duplicates?
If you send a message longer than 140 twitter will truncate it and set the truncate value on the status to True. For duplicates it will just ignore the status. Josh On Thu, Oct 15, 2009 at 1:20 PM, janole wrote: > > Hi, > > I just figured out that when calling statuses/update with a text > longer than 140 chars, the reply of that API call will be 200 OK with > the last status of the user. > > Wouldn't it be better to return some sort of error message? > > The same seems to be happening when sending a duplicate tweet. > > Ole > > -- > Jan Ole Suhr > s...@mobileways.de > On Twitter: http://twitter.com/janole >
