Modern XMPP project discussion - 2026-04-22

> This of course also means their documentation is formatted like a chat log. Which is awful. This also means I will never join the project, as it is far too much effort to just see the docs. ↺

> It's a shame adhoc isn't in more clients because it really is the better solution for the types of things people use chatbots on discord, slack, etc for. Yup, forms are much better than sending passwords to a bot for logging in, for example. ↺

I don't think it should have been deprecated but the decision was made and there is probably no going back now

it's not like it is irreversible, is it?

I think that instead of the XEP-0071 XHTML-IM that uses a separate element we should just add an attribute `format` that can be MD or HTML. Using a separate element is a bad idea: this is bad for performance but also now we need to send a message in both body and xhtml elements. If a client can't support rendering of the HTML then a user will see raw tags but this should be not critical. In fact we can add support of the html and markdown to all FOSS clients in just a week.

BTW here is TG API that can be used for inspiration https://core.telegram.org/bots/api#formatting-options

MattJ: any further ideas what configuration I have wrong that is not letting migrate.modernxmpp.org connect to my server as destination?

stokito, what you want is close to https://xmpp.org/extensions/xep-0394.html

or, to be precise, what Telegram uses internally is close to that

for the bot API, they provide also parsing of html and markdown, which they will then translate into their internal format

Here's the docs for their internal format for reference: https://core.telegram.org/type/MessageEntity

If someone replies to a photo and I see >aesgcm://example.com/xxxxx reply here this instead of the photo, is that - because something is broken - because an XEP is not supported - because of something else..?

Excellent question. Probably none of those reasons

It's not broken because the client did it intentionally (it chose to quote a link to the photo)