Previous versions worked with the permission denied, which is generally a good idea to have simple response bots with minimum permission scope to minimize risk of the server being retroactively scraped in case their tokens get compromised. I assume its inability to assign a reply broke the response flow.

I think ideally it should have some sort of else condition to just post the message (as it was before) in case it was unable to attach a reply to the post.

Figured it might be better to make a new issue with those.

First, twitter gifs stopped worked altogether, while they worked fine on the previous version:

(this is the same gif I used as example on the previous issue)

Second, the bot still posts its temporary message on some image posts, which do embed properly. If there's no way to avoid the message without checking the API first, might be better to just scrap it altogether as it's not very useful and even increase the likelihood of discord API not responding and the message just getting stuck there.