-
Notifications
You must be signed in to change notification settings - Fork 625
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
The Matterbridge process is failing to transcribe correctly the embedded URL in the original Telegram posts #1525
Labels
Comments
Hi, thanks for the screenshots, they help, but I really need a debug log and the matterbridge version before I can help. |
Hi, the same Problem also occurs when relaying from Telegram to Whatsapp.
|
Fixed by #1765 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
The Matterbridge process is failing to transcribe correctly the embedded URL in the original Telegram posts.
Looks like the URL is simply transferred within the post's text and the Markdown 'envelope' is missed, so that the URL is no longer a hyperlink. It looks messy and won't be usable as a link, unless you know and copy/paste the appropriate text string, etc. If you use the text Markdown in the Telegram post, it won't show correctly - just the actual URL. But, on transfer to Mattermost, the Markdown text-link shows correctly (as you'd expect).
If you use the Telegram hyperlink CTRL+K function, the text-link shows OK in Telegram, but you get problems on Mattermost. Apparently, the text following the Telegram hyperlink gets added to the URL and, if you click it, you get a 404 Error.
Is there any chance that the Matterbridge API (or whatever) can be modified? If not, then users must be warned of distortion, etc.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Is there any chance that the Matterbridge API (or whatever) can be modified? If not, then users must be warned of distortion, etc.
Screenshots/debug logs
If applicable, add screenshots to help explain your problem.
Use logs from running
matterbridge -debug
if possible.Environment (please complete the following information):
matterbridge -version
- again unsure sorrygit rev-parse HEAD
- I don't know what this means.Additional context
Please add your configuration file (be sure to exclude or anonymize private data (tokens/passwords))
The text was updated successfully, but these errors were encountered: