Replying here to an email that was sent to me instead of the list.
> https://nicoco.fr/inbox/spaces.html
I really do not want this and think interest in this will die out as
soon as the discord fad dies out. XMPP doesn't need to be a clone of
the $current_popular_thing to be successful.
This is not an attempt to be a clone of discord. If anything, I believe
Slack was the first chat network to popularize its "workspaces". Not
wanting it is fine, it's not like I or even the XSF have power to force
anything onto anybody. It is a recurring demand from end-users though,
mostly "power users" whom I believe often drive adoption to larger
audiences. Example, this mastodon post by the maintainer of Pelican
(open source static site generator)
https://pouet.pas.la/@[email protected]/114037448802034316
Its also made completely redundant by disco and the ability to have
multiple muc hosts running on a different subdomain: Eg,
specific.interest.muc.hostingprovider.tld
You assume that everyone self-hosts. I'm all for a federated network of
small servers, but everyone self-hosting does not seem realistic or even
desirable to me. A MUC service being a space is briefly mentioned in the
introduction, but I will update it to explain why this is not enough.
This works for Usenet.
I don't think this is how Usenet works at all. Do you need to host a
Usenet server in order to create a group? Also, I don't think I made it
mandatory in the spec to have a local part for the space JID, so a space
JID can very well be knitting.example.org, with rooms having JIDs such
as [email protected]. This is probably more annoying to
implement, except with XEP-0225 but for some reasons (maybe some are
valid?) it seems it was never implemented by any server.
-- nicoco
_______________________________________________
Standards mailing list -- [email protected]
To unsubscribe send an email to [email protected]
