Modern XMPP project discussion - 2022-02-23


  1. Sam

    I wonder if anyone has thought about adding a word for "list of chat rooms"? It may be fine to keep the existing terminology (bookmarks) for this, but I'm not sure if other systems have a different word that would be more widely known?

  2. Sam

    Or does "Contact list" cover both the roster and this?

  3. MattJ

    I don't think "contact list" fits, but most clients would just call it "chats"

  4. Zash

    or "conversations"

  5. raucao

    or channels? https://docs.modernxmpp.org/meetings/2019-01-brussels/#group-chats-channels

  6. Sam

    That's fair, maybe just use the plural and don't have a name for the list itself

  7. Sam

    I was thinking about a dialog "Remove this channel from your bookmarks?" but maybe just "Forget this channel?" or something is fine

  8. MattJ

    I think "bookmarks" would be a forbidden concept

  9. Sam

    yah, I feel like the idea of bookmarks is familiar enough to people, but I also don't know of any other chat system calling saving group chats "bookmarks" so maybe it would just be confusing two concepts for most people

  10. MattJ

    It's obsolete for MIX, and for MUC it's mostly just to allow cross-client synchronization of joined MUCs

  11. MattJ

    Because that's what people expect (a chat being visible in one client and not in another is weird)

  12. Sam

    The bookmarks xep is obsolete in MIX, but you still have a concept of a list of channels being displayed in the UI.

  13. MattJ

    Yep

  14. Sam

    So continuing to use the word "bookmark" for that may or may not still be an option.

  15. MattJ

    Bookmark doesn't make sense in the way bookmarks are used today

  16. Zash

    "leave" vs "forget" seems fine as actions

  17. Zash

    don't have to name them as bookmarks

  18. Sam

    Sure, that's what I was trying to figure out. I think bookmarks may actually make sense and be fine "I joined these chatrooms, I bookmarked them, now they show up in my bookmarks list", but I'm not set on it either.

  19. Zash

    Suppose it gets weird with 1:1 not having those actions, but eh, whatyougonnado

  20. Zash

    Actually, being able to leave 1:1 chats in Matrix was weeeeeeeeird

  21. Sam

    Favorites? That seems like it would apply to either 1:1's or channels though, so maybe that's a separate concept.

  22. Zash

    There are a bunch of things that are different between 1:1 and MUC that shouldn't be. More of a xsf@ topic to figure out that tho.

  23. Zash

    Favorites/pinned chats, read-up-to-here sync, etc.

  24. Sam

    "Channels that I have saved show up in my channels list", "Channels that I have bookmarked show up in my bookmarks"

  25. Sam

    Yah, I dunno, maybe it doesn't matter.

  26. Sam

    Maybe I should just go see what <large chat companies> call this

  27. MattJ

    The fewer concepts we expose to users, the better

  28. Zash

    "Browse old chats"

  29. MattJ

    Bookmarks are just a backing store for joined chats

  30. Sam

    "Joined Chats" doesn't make a nice title above the list in the UI though. "Bookmarks" seems a bit nicer.

  31. MattJ

    So I don't see any reason to expose them to a user, other than join/leave (and maybe forget)

  32. MattJ

    "Bookmarks" means websites

  33. Zash

    "Active chats" ? Hmmm

  34. Sam

    Normally I agree that the "bookmark on join with autojoin=true, delete bookmark when they leave" works well, but I think in this client I'm going to do three tabs in the sidebar: the roster, a list of bookmarked chats, and an "Open Conversations" list with joined rooms and recent 1:1 conversations

  35. Sam

    But I'm not sure what to call the bookmarks one. "Recent Conversations" and "Contact List" work well for the other two.

  36. Link Mauve

    “21:53:42 Sam> I was thinking about a dialog "Remove this channel from your bookmarks?" but maybe just "Forget this channel?" or something is fine”, I’d call that action “leave”, since it seems most clients are converging to a UX where bookmarks are an implementation detail, and the backing store of the actual open rooms.

  37. Sam

    Sure, the action doesn't matter, that was just an example. It's the name of the list you're adding/removing items from that I'm unsure about.

  38. Sam

    (but yah, that makes sense, I won't make that mistake in the final copy)

  39. Link Mauve

    Clients seem to be removing that concept altogether.

  40. Sam

    Yes, but as I said, I am not planning on removing the concept for this client so for those that still haven't it seems worth having something consistent to call it :)

  41. Link Mauve

    You “just” have rooms open when you connect, and the list doesn’t particularly have a name.

  42. Link Mauve

    Ah, then your client is probably not modernxmpp. :p

  43. Sam

    Maybe not. I'm doing more the conversations route where you can start a chat from a full roster list or a list of bookmarks and only then do they go into the "recent chats" view.

  44. Link Mauve

    Sam, Converse calls that “Open chatrooms”.

  45. Link Mauve

    In my deployments, I’ve removed this header altogether.

  46. Sam

    These aren't necessarily open though

  47. Link Mauve

    Sam, I’ve never had a computer able to run Conversations, so I don’t know its UX.

  48. Link Mauve

    Sam, I’ve never had a computer able to run Conversations, so I don’t know about its UX.