Earlier quoted context omitted.
I authored this blog post. There is a lot of merit to your criticisms of my decision making. I want to point out that communities are increasingly using Slack, and many of them are also in the thousands of users. Slack does nothing to discourage this, aside from posting warnings about archiving messages. The real problem is that they have an undocumented user limit. Like I said, I'm pretty sure we're the first commun…
I understand that you decided to use Slack. Maybe other communities are doing the same thing. But that does not mean Slack is under any obligation to support your use case, especially when they are pretty clear about what Slack is for. It's right there on the homepage: "Slack is a platform for team communication." A course with hundreds of thousands of students is in no way a "team."
We Tried Slack and Regretted It
111–120 of 192 posts
Re: We Tried Slack and Regretted It
#112It's pretty clear that Slack is not, and never will be, built for this use-case. Slack is for teams : small groups where everyone knows one-another by name, can be trusted with one-another's email-addresses and other contact information, can be trusted to only use @everyone triggers for important things, etc. A lot of Slack's features are built to assume this "small group with a shared purpose where everyone can be t…
I authored this blog post. There is a lot of merit to your criticisms of my decision making. I want to point out that communities are increasingly using Slack, and many of them are also in the thousands of users. Slack does nothing to discourage this, aside from posting warnings about archiving messages. The real problem is that they have an undocumented user limit. Like I said, I'm pretty sure we're the first commun…
Re: We Tried Slack and Regretted It
#113Re: We Tried Slack and Regretted It
#1145000 users, plus 300-500 new users per day. In a chat.
Convenient real time communication, that is not.
Re: We Tried Slack and Regretted It
#115Earlier quoted context omitted.
> Seriously? 5000 users, 10,000 messages is a "Use Case" now? Slack has millions of users and billions of messages -- working alright. 5000 users were seeing slowdonws for a SINGLE team -- not across Slack. And 10.000 is a limit put by Slack intentionally in place as a freemium boundary. All systems have breaking points, especially if they weren't designed for some specific use. You might as well ask "Twitter can't h…
I said that I would be embarrassed. Your opinion does not change that. You obviously seem to have lower expectations than me.
Re: We Tried Slack and Regretted It
#116Any irc or xmpp clients do not have these issues. products like Whatsapp and telegram don't have these issues.
Re: We Tried Slack and Regretted It
#117It's pretty clear that Slack is not, and never will be, built for this use-case. Slack is for teams : small groups where everyone knows one-another by name, can be trusted with one-another's email-addresses and other contact information, can be trusted to only use @everyone triggers for important things, etc. A lot of Slack's features are built to assume this "small group with a shared purpose where everyone can be t…
I authored this blog post. There is a lot of merit to your criticisms of my decision making. I want to point out that communities are increasingly using Slack, and many of them are also in the thousands of users. Slack does nothing to discourage this, aside from posting warnings about archiving messages. The real problem is that they have an undocumented user limit. Like I said, I'm pretty sure we're the first commun…
Any idea what their experience was like?
Re: We Tried Slack and Regretted It
#118Earlier quoted context omitted.
I understand that you decided to use Slack. Maybe other communities are doing the same thing. But that does not mean Slack is under any obligation to support your use case, especially when they are pretty clear about what Slack is for. It's right there on the homepage: "Slack is a platform for team communication." A course with hundreds of thousands of students is in no way a "team."
I might be misreading the post, but my interpretation was that the audience is other large communities, MOOCs, and other loosely affiliated organizations that may want to try Slack, not the Slack team itself. They're providing useful information for the former, particularly if several other organizations have made similar mistakes.
Re: We Tried Slack and Regretted It
#119It's pretty clear that Slack is not, and never will be, built for this use-case. Slack is for teams : small groups where everyone knows one-another by name, can be trusted with one-another's email-addresses and other contact information, can be trusted to only use @everyone triggers for important things, etc. A lot of Slack's features are built to assume this "small group with a shared purpose where everyone can be t…
I authored this blog post. There is a lot of merit to your criticisms of my decision making. I want to point out that communities are increasingly using Slack, and many of them are also in the thousands of users. Slack does nothing to discourage this, aside from posting warnings about archiving messages. The real problem is that they have an undocumented user limit. Like I said, I'm pretty sure we're the first commun…
I hope for their sake, The Odin Project (http://www.theodinproject.com) heeds this advice. They recently announced that they started a Slack community of 20,000 members, so they'll probably be hitting the message thresholds quickly.
Re: We Tried Slack and Regretted It
#120We have adopted Slack recently with a small 12 person (and everyone knows everyone) team and it works great. It really brings down distraction of people coming over to ask questions, they can just ask the question of a group and get it resolved by someone. We have Lync as a company wide (1000s) community messenger but for small teams this works great for collaboration of small groups. I am actually shocked that Micro…