XSF Discussion - 2019-06-16

  1. rion

    who is author pf the SIMS spec?

  2. rion

    I don't understand why it uses <reference> element. Why not just put <media-sharing> right into <message>

  3. rion

    and aslo <reference> spec states "uri" is mandatory while SIMS doesn't use it for top-level <reference>

  4. Ge0rG

    rion: I think the idea of using reference is to be able to attach the image / file to a specific word / sentence in the message. Unfortunately, the reference XEP isn't finished yet

  5. rion

    Ge0rG: yep. that's what I guessed. but I believe it doesn't add much good UX. Usually I want just drag'n'drop some files on chat dialog to share them. and that's where I don't understand how to use references and if they needed at all here.

  6. rion

    well I can referene some preferred data source probably in uri in addition to <sources> amd just ignore the fact it's a reference

  7. Ge0rG

    rion: conversations made that stupid convention on top of XEP-0066, and then everybody else moved along

  8. Ge0rG

    rion: I don't have the slightest idea what the URI for a given message is, anyway.

  9. Ge0rG

    Maybe Movim was the client using SIMS?

  10. rion

    jabber:x:oob is quite a weird and mostly useless thing as for me. SIMS with all its metadata and transports diversity looks way better

  11. rion

    btw, what's status of this https://xmpp.org/extensions/inbox/message-retraction.html ?

  12. Ge0rG

    rion: I fully agree. OOB only gives you the url, no meta data, so you need to HEAD it to find out what it's about

  13. flow

    rion, Tobias is the author and the URI situation is unfortunate and should probably get fixes