Closed zoski closed 6 years ago
Same problem, checking the toot length and adding the tweet to the db.json file without tooting it would be a good fix I guess.
I think this was fixed by https://github.com/YoloSwagTeam/t2m/pull/20, could you confirm?
Yeah I did a fix, but there's been a huge refacto afterwards which may have not implemented this fix
Fix is still here after the refactoring (I made sure of porting everything) https://github.com/YoloSwagTeam/t2m/blob/master/t2m/__init__.py#L170-L184
Ho yeah forgot about that, so I think we're all good because I couldn't reproduce the error
Cool :)
Closing it for now, don't hesitate to re-open if you get the bug again (with the incriminated tweet if possible, like that we can diagnostic it)
TLDR
Message from twitter longer than the maximum toot size are always proceed event after they failed many times.
More in depth
Some messages from twitter like comments above a RT may be longer than 500 characters (the one bellow is 580 chars). For now, there is no verification of the length of tweet before t2m try to forward it to Mastodon. That lead to some messages to be blocked into t2m and never forwarded to Mastodon 'cause they are too long.
I edited the retweet.tmpl and removed the twit link to shorten the message but that's a temporary fix.
Trace