-
Notifications
You must be signed in to change notification settings - Fork 616
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
matrix: plain text messages should not have html formatting #686
Comments
What's the issue with having it for every message ? Is there any impact ? |
It's an optimization, it doesn't violate the spec or break clients, but it's common for clients to perform this operation to reduce the overall message size. |
I understand, but if it doesn't cause any issues, it's low on my priority list. |
Hi, I'm detecting the same thing, but it's more of a problem for me: FYI, I'm using riot (web and mobile client) for the matrix bridge. NB: I'm only using matrix and xmpp bridges, when I say "other bridges", I can only talk about xmpp, I'm assuming this is the case for all bridges from the screenshots (even though the screenshot about matrix/riot doesn't show this space between the RemoteNickFormat and the rest of the body). Apart from that, thanks for this great work, with docker, it took me less than 10 min to connect xmpp and matrix :) |
Fixed in master or dev build on https://bintray.com/42wim/nightly/Matterbridge/v1.14.0-rc2-3-g67f2c67#files |
The
formatted_body
field of a matrix message should only be present when the message contains formatting that can not be expressed by the plain textbody
field. However, this field is now being populated for every single matrix message being created.example message
example source:
I would expect the formatted body to only be present if the message contained formatting such as bold, italics, lists (numbered or bullet), etc.
The text was updated successfully, but these errors were encountered: