jdev - 2022-01-23

> xnamed, I'll leave comments later today/tomorrow jonas’: it's been 9 days and I'm still waiting, did you forget?

things came up

but thanks for the reminder

xnamed, stating the obvious, you're aware that XEPs are primarily written in XML, not markdown?

jonas’: no problem, if you need more time I can remind you again

looking at it now

Yes, I thought you will help with the XML part

right, you can mess with the md2xep tool which is somewhere in the util/tools directory

it is a bit opinionated about the exact markdown format, so I suggest that you use xep2md on an existing first to see what format it expects

`pandoc yourxep.md -t tools/2xep.lua` even ✏

other than that, please take a look at the xep-template.xml and the sections it has by default -- the introduction and motivation section are missing from your document, those are required to understand what you're doing.

in addition, this document definitely requires security considerations

I haven't written the whole document yet, I will try add the rest very soon

thanks

it's typically a good idea to start with the motivation section

it helps people understand what your goal is

I will do my best to make it clear. Thank you too jonas’

i wonder why does every messegner say "User x read this message"

when in reality everybody knows the device can never know if a human read a message, except the human explicitly tells the device via a button

the chat marker xep did somehow account for that and named the element correctly "<displayed>" and not "<read>"

as in the client can be sure he displayed the message on the screen

but not if the user really read it

i wonder why we dont communicate this fact to the contact, "Message was displayed", instead of "Message was read"

its subtle but it prevents users from complaining, that the client marked a message as read when they maybe had no time to read it really, but only opend a chat for example

I guess that (the reasoning behind it may be that) some of the users may be confused by "displayed", while "read" is already commonly used in mail clients and feed readers to mean "was displayed at some point".

We show "displayed" for <displayed> element, but "read" for <acknowledged> element