Modern XMPP project discussion - 2025-06-26


  1. Masked Witch

    Am I misunderstanding something here (it is quite possible I am)? According to https://docs.modernxmpp.org/terminology/ we should use "Group chat" or "Channel" instead of "Chatroom", correct?

  2. Zash

    Masked Witch, that is the intent, yes

  3. Masked Witch

    Ok, thank you for the clarification

  4. edhelas

    Yes but in some part of the UI it can describe both

  5. edhelas

    Like the merged list of Group chat and Channels should be called .... ?

  6. Masked Witch

    Maybe add somewhere that channels are public group chats? 🤔

  7. Masked Witch

    Or maybe call the merged list "Group chats & Channels", if there is enough room?

  8. Zash

    Maybe put (small, private) group chats among 1:1 chats.

  9. Masked Witch

    Hmm, that might get a bit confusing, especially with whispers ending up there as well

  10. opinionplatform.org

    Shouldn't it list another term for muted (non) "participants"?

  11. Zash

    The idea being that 1:1 chats have more in common with group chats, e.g. being a group of 2

  12. Masked Witch

    Thinking more about it, that would help with some edge-cases like Matrix one-on-one chats over Slidge. Currently they show up under "Chatrooms", due to how Matrix is, and that would help reduce confusion with newcomers using Slidge

  13. Masked Witch

    Why is "chatroom" considered a historic term we should not use anymore? I don't think it's a great term, but it makes as much sense to me as "channel"

  14. pjoter

    maybe the word chatroom is too _suffocating,_ and introverts might react negatively to it

  15. Menel

    At one point you have to choose some name. If it's "as much" then there is the answer. One was choosen

    👍 1
  16. edhelas

    My choice in Movim was Chatroom are GroupChat + Channels

  17. pjoter

    on the other hand, i think that terminology should be a 4th or 5th order problem in the current reality

  18. opinionplatform.org

    Why say "chat" when it's only "text"?

  19. Menel

    Because that's how language evolved.

  20. opinionplatform.org

    English especially has multiple meanings for words, but calling online venues "rooms" just seems like incorrectly tying it to something physical.

  21. Menel

    > Why say "chat" when it's only "text"? Sound like this joke form like "Why is it called fast food and not "regret on a tray?" (etc)

  22. Menel

    I've don't try to find formal logic meaning in language. Language is what happens in a society

  23. opinionplatform.org

    I'm not quite as picky as some people, like RMS, but do think there's a time to push "better" usages. I think some people encouraged ties to physical things to push to "don't copy that book/music/video" mindset.

  24. alexkurisu

    > Why is "chatroom" considered a historic term we should not use anymore? I don't think it's a great term, but it makes as much sense to me as "channel" I have a similar question for "Roster" vs "Contact list" and especially "Avatar" vs "Profile picture"

  25. alexkurisu

    I'd even argue that "Avatar" is not a historic term and has never been so

  26. Menel

    Nobody knows what a Roster is, that's why

  27. Zash

    Isn't "roster" a sports term?

  28. alexkurisu

    > Isn't "roster" a sports term? I believe it comes from sports but used outside of it, yeah

  29. alexkurisu

    Any list of people enrolled for something can be called "roster"

  30. Zash

    "buddy list" is trademarked XD

  31. jjj333_p (any pronouns)

    tbh i think its approprite to call it a "contacts list" or "friends list"

  32. Menel

    English isn't my first language, and I've never heard anything similar beside Rooster. But I immediately understand "Contact list" I think that's the reasoning behind the terms...

  33. alexkurisu

    > "buddy list" is trademarked XD Chumroll :)

  34. jjj333_p (any pronouns)

    tbh it works more like a "friends list" imo, but in some ways those terms are kinda interchangable

  35. Zash

    alexkurisu, "avatar" seems to have been written into the docs around this time: https://chat.modernxmpp.org/log/modernxmpp/2021-09-06 and https://chat.modernxmpp.org/log/modernxmpp/2021-09-07

  36. alexkurisu

    > English isn't my first language, and I've never heard anything similar beside Rooster. > But I immediately understand "Contact list" > I think that's the reasoning behind the terms... But then you have chatrooms in your "Contact list" …

  37. alexkurisu

    > English isn't my first language, and I've never heard anything similar beside Rooster. > But I immediately understand "Contact list" > I think that's the reasoning behind the terms... But then you have chatrooms in your "Contact list"…

  38. alexkurisu

    Chatrooms are not people, so this looks weird

  39. Arlington Hughes

    > > Isn't "roster" a sports term? > I believe it comes from sports but used outside of it, yeah It's actually a military term for a list of personel schedule for duty rotation (e.g. "duty roster"), but it apparently comes from the dutch "rooster" for table list. https://www.etymonline.com/word/roster

  40. Zash

    https://docs.modernxmpp.org/rationale/ has a bunch of reasoning for the choices, linked in a footnote somewhere

  41. alexkurisu

    It only has reasoning for chatrooms rename

  42. Zash

    https://docs.modernxmpp.org/rationale/ has a bunch of reasoning for some of the choices, linked in a footnote somewhere

  43. Arlington Hughes

    > It's actually a military term for a list of personel schedule for duty rotation (e.g. "duty roster"), but it apparently comes from the dutch "rooster" for table list. https://www.etymonline.com/word/roster And apparently it comes from an old word for gridiron (the rows of lines being analogous to a list of people).

  44. alexkurisu

    By the way, i was just re-reading the client UI guidelines and maybe it should recommend using an UUID as a resource, like current RFC does?

  45. Menel

    Isn't the *UI* recommendation: don't (show it)

  46. MattJ

    alexkurisu, resources are already changing with Bind 2.0, which will very likely be rolled into the next XMPP RFC when that happens

  47. MattJ

    But as Menel rightly says, the *UI* recommendation is simply not to show it, so the format technically doesn't matter at that level