jdev - 2022-10-30

i guess i had too much emphasis on the message styling and figured markdown was the first implementation

i'll think about an xep proposal for message styling with multiple styles available/possible, where the styles are based on published specs/libs

No, it's not compatible with markdown (though it borrows some styles from it).

I would like to point out that you can separate the user-facing format from what is sent on the wire. 393 does not, but xhtml-im and 394 does allow that, so you could have the user write markdown or whatever they want in their client and then convert it for transfer over the wire, after which it can be displayed the same way regardless of what it was in the beginning.

e.g. see other systems where you enter markdown or wysiwyg and then it's transported as HTML on the wire

that would work well for asciidoc, since it can convert to html by default

point being it does not need a XEP

i understood

Zash: that's exactly why many people were opposed to 393 (including me), 394 is really nice solution, I would love to see gaining popularity.

Vote with your keyboard.

Implement the change you want to see in the world!

yes I know, but I have only 10 fingers and 24 h a day.

Don't forget your toes!

I have XHTML-IM and not 393 nor 394 for now.

and focusing more on pubsub than rich text messages

but the day will come, and we'll make a revolution

24 hours? when do you 𝑠𝑙𝑒𝑒𝑝?

( https://xmpp.org/extensions/xep-0457.html > * )

to be honest I have 25h in my day today.

touché

you guys have days?

winter is coming

Polar nights? :D

close enough

just to be sure

stream header init, if i set to=example.org

and the stream header response is from=im.example.org

i end the stream, right?