ian
August 13, 2026, 1:04pm
21
Inline webxdc is an often request feature:
A use case for allowing to show webxdc of static HTML + CSS in the chat with JS disabled is to provide an alternative for space-efficient and accessible stickers, animations and lightweight interactive CSS-only galleries and combinatoric logic. You can already achieve this with SVG+SMIL, but competence for creating such from scratch is high and it can’t be usually reused elsewhere.
Whereas, existing png & jpg thumbnails of a game or the current snippet from the doc or calendar app could be repr…
If we supported rendering HTML email (optionally inline) and chat URL references with parameter passing, such buttons could be implemented using <a href="openpgp4pfr:...">RSVP yes</a>.
We can’t initiate encrypted communication via mailto as it is missing the public key. This means it won’t work on chatmail.
You could possibly already @-mention other members within the group based on their key fingerprint or any unique prefix of it, just like it is done in git. No further data would need to be maintained and synchronized then.
However, I still believe that user ping mentions would be more durable if it was serialized as an openpgp4fpr or i.delta.chat URI (only with the fingerprint and address included) in the sent message. The Delta Chat interface would render such links as a clickable user pill wi…
No, it’s the other way around. The fingerprint of a profile won’t change, while the display name and the email address can be changed back and forth any time. Hence, embedding the fingerprint according to my suggestion would be a stable reference to the given person.
Introducing non-standard data attributes on <button> would be less interoperable.