791212 - Twitter accounts shouldn't attempt to connect if the track field has a value > 60 bytes

Status: RESOLVED INVALID

(Thunderbird :: Instant Messaging, defect)

Description

[Florian Quèze [:florian]]

Some user reported today a twitter account that got disconnected with the confusing error message:
 "406 Not acceptable"

After some trouble shooting, it turns out the real issue was the track field that had a value longer than what the Twitter API accepts.

"Each phrase must be between 1 and 60 bytes, inclusive."
https://dev.twitter.com/docs/streaming-apis/parameters#track

So I think the best we can do here is refuse to connect the account, with an error message that's explicit about what the user needs to change to get the account in a state that can connect.

The alternative would be to try to crop automatically some of the tracked keywords, but I think that wouldn't be 'right', as the users would think that everything is fine, and not understand why some keywords never appear in the timeline.

Comment 1

[Ludovic Hirlimann [:Usul]]

As this been fixed with all the checkins that came into the tree from instant bird ?

Comment 2

[Florian Quèze [:florian]]

(In reply to Ludovic Hirlimann [:Usul] from comment #1)
> As this been fixed with all the checkins that came into the tree from
> instant bird ?

Instantbird, not "instant bird" ;)

And the answer is no.

Comment 3

[Patrick Cloke [:clokep]]

Bug 1445778 removed Twitter support.