4 ms·
> eh... slack has consistently said that large communities shouldn't use its services. That has nothing to do with Slack-like apps, and everything to do with S
by itistoday2 11y ago
> eh... slack has consistently said that large communities shouldn't use its services.
That has nothing to do with Slack-like apps, and everything to do with Slack.
> Go talk to the hundreds of FOSS communities that use IRC. they have all fixed the persistence / search problem
I am part of many FOSS communities on IRC. None of them have "fixed" that problem. There might be one or two that archive the channel somewhere. That is no substitute for real in-app persistence and search.
- mugsie 11y agohttp://eavesdrop.openstack.org http://eavesdrop.openstack.org - all channels, all meetings, in a nice index and searchable format (i.e. google search with site:http://eavesdrop.openstack.org http://eavesdrop.openstack.org <query>) There is a reason slack has a problem with that - scaling is hard. There is also the advantage of not having silos - if I have a problem with a dependant library I can "/j #libname" and ask a question, instead of searching for what slack, or slack like tool they use, signing up, installing whatever app is needed to access it, and asking the question (and remembering what app they used, so I can keep it open for issues that run over a few days.)
- icebraining 11y agoFrankly, itistoday2 is right - the fact that I have to open an external website and open the multiple pages for the days I've been away, instead of simply scrolling up and continuing the discussion, makes for a terrible experience. Detachable screen sessions make up somewhat for it, but they're still pretty limited (you might have /joined the channel only later), and it requires a personal service running, that must be attended to & etc.