jdev - 2023-01-02

  1. flow

    or vice versa :)

  2. Zash

    qy: Go for it, good way to start discussion if nothing else

  3. qy

    what's the prevailing opinion though?

  4. flow

    that's often not so easy to find out. You can ask around in the MUCs, but kicking of a @standards mailing list discussion is always a good idea. However, sometimes there won't be plently replies. So the next step is to create a ProtoXEP, potentially announcing it on the mailing list for feedback. And if that does not provoke a reaction, then submitting it to the council probably will ;)

  5. flow

    and there is of course the question why there is a lack of feedback: is it because nobody cares, or because everyone aggrees

  6. Zash

    Silent consesus and buggy proof of concepts

  7. pep.

    Yeah when nobody cares it's really hard to get any feedback.. council feedback is also very limited sometimes (for good or bad reasons) :/

  8. Zash

    Implement and ship it!

  9. Zash

    You'll get all the feedback once it's too late to change 😉

  10. pep.

    qy: something something introducing server handling of chat markers and adoption, maybe

  11. pep.

    Zash: exactly :p

  12. Zash

    You could have the server catch and strip 333 in some cases, advertised in disco...

  13. Zash

    I think there's a MUC module doing that in Prosody.

  14. Zash

    Another option is just stuffing something in PEP (ala XEP-0223)

  15. pep.

    I don't know if it'd be a huge overhead to send to one's account in addition to regular markers :x

  16. Zash

    XEP-0333 just doesn't require server handling, so I was very confused when someone offered to pay me to implement it in Prosody long ago.

  17. Zash

    pep., could be something automagically managed by the server

  18. Zash

    You could catch XEP-0333 stuff and store something in PEP.

  19. pep.

    It could be for sure. A client would have to check disco before that

  20. Zash

    Clients could then do it themselves if the server doesn't yet

  21. pep.

    By sending to their own jid

  22. pep.

    Hmm no

  23. pep.

    Storing in pep.

  24. Zash

    Sending everything to pep. to store

  25. pep.

    Dunno what I would prefer, mam or pep

  26. pep.

    Even though mam would definitely require server handling if one cares about markers not getting to the other side

  27. qy

    mam wouldn't sync live, but pep could

  28. pep.

    Yeah using MAM supposes the server filters if required

  29. pep.

    That's how you get live messages