On Fri, Oct 23, 2009 at 04:20:36PM -0700, Dewald Pretorius wrote:
Instead of all of us having to do fancy tap-dances, the proper
solution is for Twitter to issue an error response when a sent tweet
is rejected for whatever reason.
Yep, exactly. That's my big gripe about the whole thing.
On Fri, Oct 23, 2009 at 02:24:53PM -0700, AJ Chen wrote:
I noticed this behavior a long time ago (may be a month) and reported the
problem on this list, but it did not get any response from the api team. I
thought it was a bug, but just realized yesterday that the api probably
ignores 140+
I noticed this behavior a long time ago (may be a month) and reported the
problem on this list, but it did not get any response from the api team. I
thought it was a bug, but just realized yesterday that the api probably
ignores 140+ chars status update intentionally. but' I'm not sure this is
the
then, comparing the front part (without url at the end) of the status is
probably sufficient. -aj
On Fri, Oct 23, 2009 at 3:07 PM, Dewald Pretorius dpr...@gmail.com wrote:
You cannot compare the status sent with the status returned when the
status contains an URL. The returned status contains
Instead of all of us having to do fancy tap-dances, the proper
solution is for Twitter to issue an error response when a sent tweet
is rejected for whatever reason.
Dewald
On Oct 23, 7:58 pm, AJ Chen cano...@gmail.com wrote:
then, comparing the front part (without url at the end) of the status
+1 agreed
On Oct 23, 2009, at 7:20 PM, Dewald Pretorius wrote:
Instead of all of us having to do fancy tap-dances, the proper
solution is for Twitter to issue an error response when a sent tweet
is rejected for whatever reason.
Dewald
On Oct 23, 7:58 pm, AJ Chen cano...@gmail.com wrote:
On Tue, Oct 20, 2009 at 07:37:03AM -0700, James Tymann wrote:
Has anyone else noticed a change in the way that the 140 character
limit is enforced via the API? I noticed a change sometime between the
13th and the 16th that is now causing all my 140+ character posts to
be rejected by the API.
This is the new intended behaviour from what I have been told. All
tweets 140 in length will be silently ignored.
I'm guessing they don't throw an error here yet to not break any
existing clients until they have upgraded.
Eventually I'm sure we will be some sort of 400 error in the future.
For
