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.
As this been fixed with all the checkins that came into the tree from instant bird ?
(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.
You need to log in before you can comment on or make changes to this bug.