You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Occasionally when running this bot and sending a GIF or URL in the target server the bot will log this, even though nothing was manually updated. My best guess is that it sees what Discord does automatically (e.g. rendering the link to the GIF into the GIF itself or adding an embed for a URL) as a message update, and it simply sends the identical source and updated message as a message update log. A simple example was https://github.com, which renders in a text channel with an accompanying embed, where the Logger Bot logged a source message of https://github.com and an updated message of https://github.com as well. Any chance there's a simple fix for this?
The text was updated successfully, but these errors were encountered:
I should emphasize that this is not universal; in fact, if I send the same message again (https://github.com), it seems that the message update log is no longer triggered, but some other URLs and GIFs trigger the log. Maybe that has to do with a caching process, I'm really not sure.
@mlhynfield As I already wrote in another open issue, I haven't updated this code for over half a year because I don't have time for it, so the code is quite outdated and may not work, you can fork it and fix it so that everything works as it should.
Occasionally when running this bot and sending a GIF or URL in the target server the bot will log this, even though nothing was manually updated. My best guess is that it sees what Discord does automatically (e.g. rendering the link to the GIF into the GIF itself or adding an embed for a URL) as a message update, and it simply sends the identical source and updated message as a message update log. A simple example was https://github.com, which renders in a text channel with an accompanying embed, where the Logger Bot logged a source message of
https://github.com
and an updated message ofhttps://github.com
as well. Any chance there's a simple fix for this?The text was updated successfully, but these errors were encountered: