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
Write a message on Telegram, let it be bridged by matterbridge to discord, for example "Hello humans how are you today"
On Telegram (e.g. using the "Web A" client at https://web.telegram.org/a/) respond only to a part of the message. (For example selecting the word "humans", right-clicking it, and selecting "Quote & Reply", then typing a message like "But I'm a robot-cat-ninja, not a human! 🤪", and sending it)
I think that PreserveThreading is involved in this issue.
Expected behavior
The second message should arrive just fine, either as a reply, or as a regular message (in the worst case).
Actual behavior: See above; an error message is logged, but the message is lost.
Screenshots/debug logs
The screenshots are specific to the "Web A"-client, and some clients don't support sending such messages. However, most clients support displaying these messages perfectly correctly; all clients display the main reply text, at least.
Environment (please complete the following information):
AutoWebhooks=true is fail.
There is a request to fix the problem, if the dkscord images are too important for you, you can fork it with the modification.
I hope the owner updates this repo when he has time.
Describe the bug
When responding to a partial message quote, matterbridge sends garbage to discord, and it fails. Excerpt from my logs:
To Reproduce
Steps to reproduce the behavior:
PreserveThreading
is involved in this issue.Expected behavior
The second message should arrive just fine, either as a reply, or as a regular message (in the worst case).
Actual behavior: See above; an error message is logged, but the message is lost.
Screenshots/debug logs
The screenshots are specific to the "Web A"-client, and some clients don't support sending such messages. However, most clients support displaying these messages perfectly correctly; all clients display the main reply text, at least.
Environment (please complete the following information):
version: 1.26.1-dev
(I'm using Explicitly announce the sender of each file in Telegram, simplifying moderation #2165)Additional context
The text was updated successfully, but these errors were encountered: