Modern XMPP project discussion - 2025-02-20


  1. m,

    I guess you may have read some very old articles. I recommend you to use Gajim.

  2. pep.

    > Also Hats are good for that, waiting for the support in ejabberd :) Fwiw I'm still suspicious what we're gonna fit in hats. I hear all kind of things. It's probably gonna be a nightmare UX-wise

  3. MattJ

    I agree completely, which is partly why I did what I did to the XEP and made a simple implementation

  4. MattJ

    To me "hats" should be a protocol for showing badges/etc. in the UI

  5. MattJ

    Some people want (much) more than that, which is something that happens to unimplemented protocols

  6. MattJ

    For example, hats as access control. I think it makes sense at some level, but you probably want your access control groups to be a separate layer, and hats are just for the UI part

    💯 1
  7. Squeaky Latex Folf

    Interesting

  8. Squeaky Latex Folf

    What would such separate layer look like?

  9. Kris

    Most likely one that also groups channels into collections, aka "spaces" (but that is a terrible term).

  10. Kris

    Technically it can be a pubsub node 🤷

  11. Squeaky Latex Folf

    > Most likely one that also groups channels into collections, aka "spaces" (but that is a terrible term). Does that even exist?

  12. Squeaky Latex Folf

    I only know of Gajim's workspaces

  13. Squeaky Latex Folf

    But idk if any other implementation

  14. Squeaky Latex Folf

    Or let alone protocol that assists in such thing

  15. Squeaky Latex Folf

    > Technically it can be a pubsub node 🤷 Elaborate. I can't imagine what that would be like.

  16. Kris

    Some ideas exist, but nothing more concrete afaik

  17. Kris

    A pubsub node is basically just a data storage you can subscribe to. You can store the channels and ACL in there for clients and servers to read.

  18. Squeaky Latex Folf

    Hmmm

  19. pep.

    > Most likely one that also groups channels into collections, aka "spaces" Yeah I don't know if ACLs should also go with spaces. That can still be a separate thing. Again, putting everything into everything, not a good idea IMO :/

  20. pep.

    We can think about how they may interoperate but we don't have to make them the same thing

  21. Kris

    I think both is channel metadata and can be treated as such

  22. pep.

    I think I'd rather think of the global thing at the space level. I still want to be able to use extended affiliations at the channel level without a space, probably

  23. pep.

    Maybe something that overrides local behaviour when using spaces. I don't know how exactly

  24. Squeaky Latex Folf

    This is all theoretical right? Is there any indication of a draft on how 'spaces' or 'extended affiliations' may work as a protocol?

  25. pep.

    Yeah it's theoretical. There isn't much about spaces in form of near-implementation or spec. The closest is gajim but that's more of a local-only UI thing than something that brings together channels and ways to advertise / administer them

  26. MattJ

    Actually Kev has been doing some work on it recently, I had some lengthy discussion with him about how it could fit with GC3