4 ms·
The author's expectations just seem wildly unrealistic, I can't find much sympathy. Signed up for a pay service with a clear limit on the trial, yet was surpris
by dahart 10y ago
The author's expectations just seem wildly unrealistic, I can't find much sympathy. Signed up for a pay service with a clear limit on the trial, yet was surprised by the limit, even though he knew how many Slack users he had and knew or should have known how many messages per day they were already sending. Put his community (customers) of thousands on the Slack team, even though the advertising and economics only make sense for internal teams. He is trying so hard to make his own mistake sound like Slack's fault.
Also, previous discussion: https://news.ycombinator.com/item?id=9754626 https://news.ycombinator.com/item?id=9754626
- __jal 10y agoYou appear to be confusing the message archive limits with the number of user limits. The first is (loudly) disclosed. The second, apparently not.
- erelde 10y agoSlack doesn't advertise as a chat for thousands of users, but teams of 5 to 50, worse case 100 people. It's "lucky" they didn't hard code a limit.
- mcintyre1994 10y agoThey did hard code a limit, the API has a specific error for that. They just choose not to disclose it, and to advertise with the phrase "Slack is free to use for as long as you want for teams of all sizes."
- erelde 10y agoWell then I guess they expect the word "team" should be self explanatory... Maybe it's not.
- dahart 10y agoThis is a completely legitimate point. They are expecting "team" to be self explanatory, and it is a vague term that is not self-explanatory. If there's a size limit, it would be best if they stated that plainly. But, come on, you have to admit that an online community of thousands of people does not fit even the most charitable interpretation of the word "team".
- sgift 10y ago> But, come on, you have to admit that an online community of thousands of people does not fit even the most charitable interpretation of the word "team". That is basically what the whole thread and article evolves about. Are 10k people a team? Really? Sure, you can argue all day that technically it may be the case, the whole world could be my team, some kind of super team and so a service shouldn't make any assumptions and so on, but reality is that everyone who hears "team" has a pretty good idea of a ball park figure how many people that will be and that freecodecamp doesn't fit into this. So, in the end it's just playing around semantics "but, but, but ... you said of any size .."
- dahart 10y agoThe whole world is not a team. You can only say that if you're making an intentionally, consciously hyperbolic statement. I am not interested in long and un-ending pedantic arguments about the extreme corner-case definitions of words. I maintain that an online community of 10k people does not fit even the most charitable meaning of a working "team". If that doesn't work for you, then you're only setting yourself up for surprise. This argument that "any size" should really mean "any size" amounts to someone walking into an "all-you-can-eat" buffet and expecting to be able to sit at the same table for 2 weeks eating all meals for the price of one, and then complaining that the 'all you can eat' advertisement should overrule all other policies the restaurant has. It would be the same as someone seeing an ad for mini-golfing for $20 for a family of any size, and then bringing four thousand of your 2nd, 3rd, and 4th cousins, and demanding that the entire group gets in for $20. While there's a pedantic, technical truth to cousins belonging to your 'family', it doesn't meet anybody's common understanding of what an ad for family prices means, even the person trying to cheat the system. If the author truly didn't even suspect that his 10k users is a massive stretch of the idea of a "team", the message limits should have been a clue, but instead of acknowledging he was pushing the limits, he blamed Slack.
- Bartweiss 10y ago"For teams of all sizes" is pretty deceptive. Even if the limit was disclosed somewhere deeper, advertising with a fundamentally inaccurate line is unfortunate.
- arcticfox 10y agoWhile their language was poorly chosen, I think what Slack meant was that their free tier was under no additional restrictions than their paid tier for team size, which seems reasonable. And signing people up with an undocumented API that skips a big amount of signup friction seems like a recipe for running into undocumented limits. Would we be upset with Slack for not supporting 1 million user teams? 1 billion? 1 trillion?
- lawpoop 10y ago640k should be enough for anybody
- zellyn 10y agoAt a "team" size of 5000, the 10000-message limit means you each get 2 messages before things start disappearing. So I think the message limit pretty strongly implies a team member limit.
- Bartweiss 10y agoBut is the user limit only for the free version? As I read that support email it was simply a limit on the size of Slack teams across the board.
- dahart 10y agoYou appear to have not read the article. The very first complaint is about the 10k message limit warnings. The author then complains "Slack would aggressively archive messages, sometimes only minutes after they were sent." He's lucky the messages even went through. He asked Slack for guarantees, after the fact, on the free plan with no intention of paying Slack's rates. Even the user limit problem is silly. It's called a team and marketed for internal use, not as something you 're-sell' or offer customers. It's obvious that putting your users on a single Slack team is not going to scale to tens of thousands of people, as soon as you start using Slack. My point here is that the author did not do his homework before he moved his thousands of users to Slack, and your point falls squarely under this lack of effort.
- mulletbum 10y agoHis point, which you have missed, is that although the archive thing was a problem, it may been their own fault. However, the number of users allowed was not, plus paying for the service wouldn't change that the cap exists.
- dahart 10y agoMy point, which you have missed, is that the author should have uncovered this cap before moving his community. It was clearly on sketchy ground before he did it. You can't say anything about what paying would have done, because he had no intention to pay. And if he had paid the 0.5 million, I'd be willing to bet that Slack would attend to his needs. But none of that happened, so it's a straw man.
- Nomentatus 10y agoPlease share your method of uncovering, in advance, undocumented limits inherent in software; it's desperately needed. The guy left a free trial for another free trial; if he's at fault we're all at fault every time we change our go-to software. The lesson might be that "there be dragons" - you should guess that any "better" program or SaaS out there is less that half of what it says once unknown limits have been discovered.
- mabbo 10y agoIf the authors expectations were higher than they ought to have been, that was because the Slack marketing team set them so high.
- budu3 10y agoI think he's being a little bit to hard on Slack. He was really stretching a free trial offer beyond its limit. If he was a paying customer then I might have cut him some slack.
- simion314 10y agoWhat I understand is that author did a trial and hit technical limitations in the desktop and mobile applications, I think that paying extra would not had help. Probably the slack developers did not tested with such a large number of users, it reminds me when I worked on a rss feed application and we were testing with 40-50 popular feeds, then a client shows up with more then 1000 rss feeds , I end up grabbing his feeds and testing with all of those and optimize the application(We did not expect someone would had so many feeds).