Modify ↓
Opened at 2013-01-10T17:08:46Z
Closed at 2015-06-13T01:06:59Z
#1018 closed defect (obsolete)
Twitter DMs don't check for max length and show 403 errors in timeline channel instead
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | minor | Milestone: | |
Component: | Version: | devel | |
Keywords: | twitter DM | Cc: | |
IRC client+version: | Client-independent | Operating System: | Linux |
OS version/distro: |
Description
This message appeared in my #twitter_<accname> - Channel
<root> Error: Could not retrieve /1.1/direct_messages/new.json: 403 Forbidden (There was an error sending your message: Der Text Deiner Nachricht ist über 140 Zeichen lang.)
As a suggestion:
- This Message should contain a reference to the DM in question
- It would be nice if that messagt would appear in the Query with that DMs target:
<name>@twitter <name> xxxxx <myself> xxxxx...xxx <- Very long message <name> <root> Error: Could not retrieve /1.1/direct_messages/new.json: 403 Forbidden (There was an error sending your message: Der Text Deiner Nachricht ist über 140 Zeichen lang.)
Attachments (0)
Change History (2)
comment:1 Changed at 2014-05-14T04:01:11Z by
Component: | BitlBee → Twitter |
---|---|
Priority: | pony → minor |
Summary: | Twitter Error Messages a bit unclear → Twitter DMs don't check for max length and show 403 errors in timeline channel instead |
Type: | enhancement → defect |
comment:2 Changed at 2015-06-13T01:06:59Z by
Resolution: | → obsolete |
---|---|
Status: | new → closed |
Twitter removed this limit on their side, making this bug obsolete: https://twittercommunity.com/t/removing-the-140-character-limit-from-direct-messages/41348
Well, to be exact, the change applies at some point in "july", so not yet, but i feel like closing this now. Bye ticket!
Note: See
TracTickets for help on using
tickets.
Congratulations, your ticket has been upgraded to a minor-priority defect!