jdev - 2022-09-12


  1. pep.

    When doing MSN in MUC, a new resource joins, I don't advertize any of the other occupants expect other resources of the same account? possibly with @jid set to be more explicit, or not at all?

  2. MattJ

    pep., correct (possibly)

  3. MattJ

    If you do the multiple <item> thing, you may want to update their presence to anyone who is permitted to see that

  4. pep.

    When doing MSN in MUC, a new resource joins, I don't advertize to any of the other occupants expect other resources of the same account? possibly with @jid set to be more explicit, or not at all?

  5. pep.

    Should I ensure one of the items is placed first or sth, for clients not handling this? (It's not like MSN was declared anywhere really..). Won't a client interpret weirdly its own presence coming back to it for no reason?

  6. MattJ

    We haven't seen any problems from that

  7. pep.

    Ok

  8. nicoco_

    may I ask what is MSN in this context, for my own education?

  9. MattJ

    Multi-session nicks, or the ability to have multiple clients of your own connected to the same MUC with the same nick

  10. pep.

    nicoco_, https://xmpp.org/extensions/xep-0045.html#terms-general it's somewhere in there

  11. MattJ

    Originally this wasn't defined by XEP-0045, but as people connecting from multiple devices concurrently became more popular, it was added on

  12. pep.

    "Multi-session nicks are not currently defined in this document."

  13. pep.

    Somebody(tm) should write an informational spec someday

  14. MattJ

    Before this (and still sometimes today in IRC) you would see MattJ-laptop and so on

  15. Ge0rG

    There is also https://wiki.xmpp.org/web/Multi-Session_Nicks

  16. pep.

    oh

  17. Ge0rG

    It's also the worst-named abbreviation in XMPP land.

  18. nicoco_

    thanks, I figured it couldn't be 'the microsoft network' but did not manage to find the acronym's meaning

  19. MattJ

    Ge0rG, so you've forgiven CSI so easily?

  20. nicoco_

    >Somebody(tm) should write an informational spec someday please ping me when you do, I'm interested 🙂

  21. pep.

    Come on I'm sure we could run a contest of badly named specs

  22. Ge0rG

    MattJ: CSI is the second-worst name, and I'm not forgiving it because there at least we had a chance to prevent it from happening

  23. MattJ

    pep., we are. It's called the Standards Track ;)

  24. pep.

    :DD

  25. pep.

    We should have a "Badly named XEPs of the year" thing

  26. Ge0rG

    pep.: with the number of XEPs published per year, we might end up with an automatic winner

  27. pep.

    What's x/item@nick for exactly? I know it's used as the target for some operations (kicks, bans, etc.), but is it useful when included in a presence update for example?

  28. pep.

    I know some servers (prosody?) use it to reserve it, but I doubt that's the originally intended use-case

  29. pep.

    It could be used as a replacement of /nick maybe :P

  30. MattJ

    It's used for role change operations, because moderators aren't allowed to see real JIDs of occupants

  31. pep.

    Ah right

  32. MattJ

    Prosody's behaviour is because some clients were also using it it for affiliation changes

  33. MattJ

    and the side-effect of including both is that it gets treated as an affiliation change, but with the specified nick as the nick to be reserved for that affiliated JID

  34. MattJ

    (that's (too vaguely) defined here: https://xmpp.org/extensions/xep-0045.html#grantmember )

  35. pep.

    “if a nick is provided, that nick becomes the user's default nick in the room if that functionality is supported by the implementation” heh

  36. pep.

    Is MUC-PM support required btw

  37. pep.

    One could return service-unavailable error message right?

  38. pep.

    Even though I'd want some other way to designate people that isn't realjids.. I might have another look at unique-id and try to do everything with that

  39. MattJ

    The XEP at least allows it to be disabled, so sure. Just implement it in a way that it cannot be enabled :)

  40. pep.

    Ah wait, there's a config option already right