Of course it is a bug.
On Oct 26, 4:33 pm, Kevin Menard nirvd...@gmail.com 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.
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 d...@fishtwits.com wrote:
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.
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 s...@mobileways.de wrote:
According to my tests, messages will not be truncated anymore!
Instead, you will get the
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
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 s...@mobileways.de wrote:
Hi,
I just figured out that when calling statuses/update
