If I type the below message, then I see it in my chat window as-is but the peer gets plain text w/o any formatting.
italic bold
They get:
italic bold
They return one to me with the formatting, but I get it plain-text. What’s missing?
What protocol is this on? Is the peer also on Pidgin? If so do they have the Tools -> Preferences -> Conversations -> Show formatting on incoming messages preference enabled?
We use XMPP only. Pidgin only.
The option is on. I believe it is the default that we never change.
I just verified the setting works as expected sending from 2 XMPP accounts on different servers in the same Pidgin instance.
You may want to check the Help -> Debug Window on the receiving side looking for a line like the following. You can see the formatted messages in the <body xmlns='http://www.w3.org/1999/xhtml'> block. If it’s not there the server could be stripping them out.
(00:24:41) **jabber:** Recv (ssl)(522): <message from='rw_grim@jabber.org/pidgin2' type='chat' to='grim@pidgin.im' id='purple978d4637' xml:lang='en'><active xmlns='http://jabber.org/protocol/chatstates'/><body>Hello! How are you?</body><html xmlns='http://jabber.org/protocol/xhtml-im'><body xmlns='http://www.w3.org/1999/xhtml'><p>Hello! <span style='font-weight: bold;'>How</span> <em>are </em><span style='text-decoration: underline;'>you?</span></p></body></html><stanza-id xmlns='urn:xmpp:sid:0' id='dyv_NyldcInznay9xyQvE9BN' by='grim@pidgin.im'/></message>
The only difference between the clients for which it works and for those for which it does not is that it works for the clients on the LAN or VPN but does not work across the public Internet.
I can’t see the contents of the messages in the log because we have OMEMO enabled, and the log dumps the encrypted body which is genius.
Could you reach out to the OMEMO dev and try to coordinate at least some level of cooperation, so that your app and their lib make sense of each other?
gkdr has basically retired as far as I know.
By public internet do you you accessing the server via the public internet or is another XMPP server in the mix here. If another server is in the mix, it’s possible that they are not sending the body with the formatting.
In this context, the public internet is a packet carrier. There is only one server.
It’s worth double-checking this assertion because there is recent activity in lurch github under that account, and the current state of affairs is absurd.
It is OMEMO that strips the formatting. Should it even interfere with the contents of XMPP messages?
There is not enough words to express the state of IM softwares in this world.
It could be, I haven’t tested that personally so I don’t know.
You should understand that without a working privacy plugin there is very little need for another IM client. It takes very little effort to reach out to the lurch dev and explain to them what they should or should not do. If you don’t give a damn that’s your right but I just wanted to put things into perspective: there are already too many working messengers out there as it is.
We are all volunteers here. People work on stuff because they want to there is no other motivating factors. It is unlikely that I’ll be able to convince them to pickup work on something they are already unmotivated to work on.
1 Like
I do not insist on anything, only put things in perspective. That was an informational message rather than conversational. Hope having another perspective on things helps volunteers prioritize their work because staying in silos narrows everyone’s horizon. We use maybe less than 10% of the overall functionality in Pidging and never opened 90% of its menus, but if it cannot reliably pass our IM’s among our users, then we consider it 100% non-working. And this applies to any software, not just Pidgin and not just IM.
The refusal of dev teams to fix basic show-stopper errors have spelled many softwares’ doom. It would be shame if Pidgin goes into obscurity as well because it cannot cooperate with OTR and OMEMO.