-
-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't confirm bans for messages without text #198
Comments
This way, we can also avoid ambiguity in case that different users send exactly the same message. Having the same text, they will have different internal IDs. |
This is not the accurate assumption of how it is currently working. Both message ID and user ID have already been passed in; see Line 706 in 40c3b74
The issue is about a different thing—failed text extraction should not fail the confirmation flow. The reason we need to extract this text and not just use msg_id from the callbackData is the ability to handle admin reports made not just by the |
The ticket was closed automatically by PR, but please give it a try and confirm. I think it will work the way you expected, as the change was rather trivial. |
Every time I try to confirm bans for messages with no text (blocked by one of the meta checks), I get this:
error: failed confirmation ban: failed to get clean message: no original message found in callback msgsData
. The problem is probably that the messages are internally identified by their text. But this doesn't have to be that way for the messages with buttons created by the bot itself.Can we embed some kind of ID to the buttons, so the message doesn't have to be identified by the text, if it's created by the bot itself, not forwarded to the admin group?
The text was updated successfully, but these errors were encountered: