We have web-based chat options, from Slack to the good ones like and .

But they take up a lot of resources, as they scale. Compared to dedicated servers and protocols, such as and , you end up throwing a lot of resources per user.

This makes me think that the web-based ones work for teams (as a shared space for ambient documentation and file sharing), but not as a public service.

Of course exceeds at scale due to federation. Like email.

I can't quite put my finger on it, but something about the UI/paradigm of web-based is really compelling.

A friend here once told me in person that Slack was just a UI shift, and IRC could be improved by copying that (my paraphrase, it was obviously more elegant than that).

If that were the case, we are really talking about the client. Because IRC is weird, and the more we can hide it, the sooner people can do boring business things.

Slack, et al, make boring business easy. 🤔

Re: boring business and chat, that is what web-based chat is about.

Is that what IRC or XMPP promote? I don't think so. Because boring business used to be everyone running office warez locally, and then needed a way to send files to another person that would be opened locally, and they just needed to communicate while they worked locally.

We don't have local workspaces anymore, that isn't the "state of boring business". Now we have online office docs, and chat is "presence".

All of this comes from my own experiments of hosting chat servers for teams and open to the public (two scenarios).

Web chat options are great for "teams", and by that I mean one or more groups that have habitual boring business interactions.

But the benefits of team chat options disappear for the public. Suddenly, sharing a file uses a lot of resources, with little benefit.

Which makes me think that an chat solution/#Mastodon interface change might be a balanced solution.


Team web chat is manageable. If your storage starts to fill, let folks know, add more disk, good to go. Grow a bunch, kick it up, because you are making money.

But in order to offer team web chat to a larger community, to provide the same level of service, you have to plan on scalable storage. Can anyone do that without monetizing?

OTOH, running platforms with less features, they scale really well. I can have hundreds of concurrent MUC on a dinky little server.

I'll put this out there: I don't consider to be a candidate for team chat.

* How does IRC develop?
* External system for archiving and search
* File sharing is weird
* Clients are weird
* Prefers commands over clicking

Super fun tech! But the teams that use it either depend on a third-party (which is fine in many cases), or have an engineer (or likely an IRC fan) to run the whole stack for them.

I run a for . It auto-updates, as does Ubuntu. Dope.

Sign in to participate in the conversation
Mastodon @ SDF

"I appreciate SDF but it's a general-purpose server and the name doesn't make it obvious that it's about art." - Eugen Rochko