jdev - 2026-04-08

  1. Cynthia

    Hi

  2. snit

    Hi!

  3. Cynthia

    Would it be possible to apply Message Markup to a <DESC> in a vCard without breaking backwards compatibility? (and also, if anyone would like it)

  4. lovetox

    It's a string field you can put into whatever you like

  5. lovetox

    Just nobody will interpret it as markup

  6. Cynthia

    You mean no clients will interpret the markup?

  7. Cynthia

    Also it is a string field, yes. Which means it's impossible to put a <markup> in it

  8. snit

    well its markup so you'd have a separate markup element anyways

  9. snit

    if only markup had a way to tell you which element its being applied to....

  10. Cynthia

    XPath, but that would be complicated

  11. snit

    also seems like overkill

  12. snit

    i think i vaguely recall another xep just putting an empty element+namespace we want to apply to as a child of its own element, but i forgot which one or if i'm even remembering correctly

  13. Cynthia

    > i think i vaguely recall another xep just putting an empty element+namespace we want to apply to as a child of its own element, but i forgot which one or if i'm even remembering correctly What ↺

  14. snit

    like if you're referring to the body in a message, you could just put an empty `<body xmlns='jabber:client' />` (right?) element into your element, and if you're referring to some other element, it could be `<element xmlns='urn:xmpp:element:0' />`

  15. Cynthia

    > like if you're referring to the body in a message, you could just put an empty `<body xmlns='jabber:client' />` (right?) element into your element, and if you're referring to some other element, it could be `<element xmlns='urn:xmpp:element:0' />` Oh yeah that makes sense ↺

  16. Cynthia

    What if there are multiple elements of that type though

  17. snit

    i imagine that depends on the context, really. i wish i could remember which XEP i saw this in, assuming i'm not making it up

  18. snit

    you could, in the case of the body element (if we pretend it wouldn't be the default when nothing is specified), differentiate via `xml:lang` tags

  19. snit

    in other cases it might just make sense to apply it to all of the matching element

  20. snit

    OHHH i think i'm thinking of fallback indications which do this but only for the body and subject

  21. Cynthia

    Oh

  22. Cynthia

    Maybe there should be a standard rich text container

  23. snit

    that wouldn't be as backwards compatible though which is why i was recommending this way instead. a generic way to go "hi this element actually applies to this other one" would be cool, for the cases where you can't just make it a parent-child relationship

  24. snit

    this was actually one of the todos in the original mentions protoxep i picked up that i chose to conveniently ignore