Hi, I’m Christina, cofounder of Hack Club. We just announced this news to our community, and this post is from one of the teenagers in Hack Club. It’s an accurate description of what’s happened, and we’re grateful to them for posting. Slack changed the terms of a special deal we were given last year to charge us for staff and volunteers (not for every teenager coding), and we built programs around that special rate. Then this spring they changed the terms to every single user without telling us or sending a new contract, and then ignored our outreach and delayed us and told us to ignore the bill and not to pay as late as Aug 29
Then, suddenly, they called us 2 days ago and said they are going to de-activate the Hack Club Slack, including all message history from 11 years, unless we pay them $50,000 USD this week and $200,000 USD/year moving forward (plus additional annual fees for new accounts, including inactive ones)
For anyone reading this, we would really appreciate any way to contact people at Salesforce to discuss time to migrate because deactivating us in 5 days destroys all the work of thousands of teen coders at Hack Club and alum unnecessarily. We are not asking for anything for free. This was an underhanded process by the sales team to raise our rate exorbitantly from a qualified educational 501(c)(3) charity serving young developers or destroy all their projects, DMs and work forever. If Salesforce’s goals have changed- ok. Give us a reasonable amount of time to migrate- and don’t club us over the head like this. We have had an 11 year great relationship with Slack- and have introduced the company to many many future engineers and founders. My email if you can help us: christina@hackclub.com
>> Then, suddenly, they called us 2 days ago and said they are going to de-activate the Hack Club Slack, including all message history from 11 years, unless we pay them $50,000 USD this week and $200,000 USD/year moving forward (plus additional annual fees for new accounts, including inactive ones)
> This was a mistake.
Calling a customer and extorting them for $50k USD this week and $200k USD per year going forward is not "a mistake."
It is a business decision which your organization made and did not expect to be held accountable for same.
> We appreciate you, Hack Club ...
You have a very different definition of "appreciate", unless you are using it in the accounting sense[0].
(I'm a mod here - your posts didn't get flagged! HN's software was filtering them because posts by new accounts are subject to a few extra restrictions.
Fortunately a user vouched for your third try, which restored it, and I've marked your account legit now, so this won't happen again.)
It's not a mistake that you're only reachable when your bad business practices are so heinous they go viral. You are an executive at a company that saves money by not offering customer support except when there's bad PR or a lawsuit.
Are you going to be fixing that your billing system is not human-reachable, or are you just going to be fixing this one incident while leaving the broken system as-is for everyone who didn't go viral?
This is the new way of doing business. Rip off as much as you can until there is enough publicity around your bad behavior such that it may affect your bottom line.
And then say sorry to convey some kind of human connection in the hopes you will be forgiven and the bottom line can be raised again.
Since this was a public facing mistake, will there be a post mortem including details about the blast radius, how many customers were affected and what steps are being put in place to ensure this never happens to a customer again?
I get automated billing mistakes, but a real human reviewed this case and demanded the money and the timeline. At that point, that is just a business practice.
The community here is very forgiving of software bugs, but why did the rep act that way? To paraphrase Warren Buffet, what are the incentives that directed that led to this outcome? Why did the rep in this case act so viciously?
If Hack Club did pony up the $200k the rep would probably be compensated in some way. That would increase the propensity of a rep to strong arm with short deadlines and hold their 11 year chat history hostage even if it’s not the appropriate pricing for a non-profit.
Since this is bad for Slack and Salesforce’s brand I imagine they’ll be putting in new mechanisms to disincentivize this in the future. When it comes to the rep getting paid they’ll become an expert at how to do it properly.
> Since this is bad for Slack and Salesforce’s brand I imagine they’ll be putting in new mechanisms to disincentivize this in the future.
You are dreaming... look at all of the other posts on topics like this. It's going to continue to be business as usual until you have the social capital for a post that gets to the front page of HN or similar status elsewhere.
While I'm encouraged by this response, I still feel a sense of fear that this fix is a one off, if you could speak to how this could even happen and how mistakes like these would be prevented in the future I'm sure the community would appreciate it.
I cannot guarantee that we won't make another mistake as we and our customer base grows. We're fallible!
In this particular instance, this was the result of an oversight in our billing process, and we are returning Hack Club to its previous nonprofit pricing. We will be reviewing our billing and communications processes to provide nonprofits clearer guidance and adequate grace periods as they grow.
Out of curiosity, will you be facilitating them exporting their chat history? Like obviously you see that this wasn’t just a billing error, this was extortion under threat of losing eleven years worth of data.
If you see this massive screwup as just a price issue that can be fixed by lowering their bill, you’ve missed what’s happened here. Your company has entirely obliterated any trust here, and the way to fix this is to acknowledge that and do everything necessary to help them migrate their data to a place where you aren’t holding a gun to their heads.
Yeah, I don't care about some non-profit or whatever. I care that the company thinks it's a-okay to demand from their customers 10x their yearly bill on the spot and to commit to 4x that yearly or else their data will be deleted in a few days. That's not an employee acting out of band, it's obviously their modus operandi.
By this you mean making sure something like this won’t happen to ANYONE ever again, right?
I hope so and I hope that you will post about it so that you can somewhat recover from this certified PR disaster.
I had previously considered advocating for your product but sure as hell won’t as long as this situation isn’t thoroughly solved. It also prompts me to look into your other business practices before ever considering speaking positively about you again.
As I said in another reply, I cannot guarantee something like this won't ever happen again. We're fallible for sure. But I can guarantee we'll keep trying and improving.
This was the result of an oversight in our billing process, and we are returning Hack Club to its previous nonprofit pricing while we work with them directly to ensure their workspace remains fully accessible. We will be reviewing and modifying as necessary our billing and communications processes to provide nonprofits clearer guidance and adequate grace periods as they grow.
I can see how the bill itself was a mistake, but the real scary thing to me is the timeline. Seven days from action required to deletion of all your data isn’t reasonable under any circumstances.
Let's be real, when an entity like Slack says "delete all your data," they actually mean they will add a flag in the database to make it inaccessible to those who aren't purchasing bulk data for data mining and llm training. The data will persist regardless.
Nah, this was one of those evil customer service reps who will do anything to make thier employer look bad. No corporation would ever leverage data custody to extract a quick balloon paymemt. Devilish customer service reps reading from false scripts are the real problem.
Hey. I think we all accept that all companies are inevitably fallible. What companies can be consistently good at---but very few take the effort to excel at sadly---is customer support communication. Honestly, reading TFA, it's still conceivable that putting Hack Club in the wrong pricing tier was an honest error on your part, but the communication was horrible to say the least. As others already pointed out, seven days to pay-up or your data goes poof sounds more like ransomware than a company trying to meet a customer half way.
And ofc, it has C-level attention now because it blew up on HN. Sorry but this screams damage limitation. For every Hack Club, you wonder which other non-profits suffered this "mistake" but didn't have the social media reach to get C-level treatment.
(Speaking as someone who spent this week being gaslit by Amazon and Google support. :mad: )
We all work at companies and know how it works - you get away with what you can. You bet wrong and nobody will believe otherwise. If it was a mistake, it’s fireable.
Although transparently self-serving, this seems like a perfect time to say, "Hey, this couldn't happen to you at Mattermost because we A) have a free tier, and B) allow you to export your data."
There is about as much ownership here as a squatter in a two-bedroom apartment. They are apologizing because they got caught, not because they genuinely believe they messed up.
Thank you for addressing this issue. Could you also provide feedback on the accusations that data export is only available for high-tier pricing plans and requires Slack's explicit approval?
You mean like it has become a mistake when the story about it broken up and went viral?
But if Hack Club did not complain about it, you would have happily took and kept taking their money?
That kind of a "mistake"?
In all seriousness, why should anyone believe what you are saying?
It seems to me that your story about a "mistake" is just as plausible as this kind of behavior simply being Slack's business strategy. Be ambiguous. Change the terms of the sale after the sale. Try poking. See which tactics works. If someone bites, take advantage of it. If they complain, call it a mistake and do damage control. Collect profits. Rinse and repeat.
Honestly this rep and/or the rep's management should be held accountable. This is an oversight that comes from end-of-quarter pressure but it doesn't make it excusable.
This. The fuckup sounds like it started on the Slack account team's end (or their sales leadership, if it was pushed from above), so that's where consequences should start.
It wasn’t a mistake, your sales incentives led to this behavior and you got caught off guard by the negative publicity.
Here’s exactly what happened: A human account manager had to meet their 3rd quarter sales goal and sent the demand for more money. It’s less than two weeks from the end of the quarter, do you really think nobody on HN is in sales and also facing the same pressure?
This is such a transparent lie that I’m surprised you took the time to post it.
It isn't two weeks until end of quarter. Like many businesses, Salesforce's fiscal calendar runs Feb 1 to Jan 31. Slack's did, too, before the acquisition. Q3 ends on Oct 31.
The time to complete the paperwork on a $200k/yr deal is longer than 2 weeks. Especially if the customer is expected to fork over 4000% more than what they were paying.
I would suggest emailing Benioff directly, an EA will screen the emails and route them to the appropriate person but I believe the charity angle might get it in front of him, and probably get the fee waived
When I worked there, weirder emails ended up getting addressed.
Since this was a public facing mistake, will there be a post mortem including details about the blast radius, how many customers were affected and what steps are being put in place to ensure this never happens to a customer again?
Please don't pile on like this when someone is showing up to fix something. I'm sure you didn't mean to (at least I hope not) but it's one of the nastiest effects a community like this one can have.
People should be welcomed and commended for posting like the GP, not shamed and hammered.
Slack obviously didn't care about the problem until it started causing them PR issues, now that they're doing the standard Social Media corporate damage control we have to hold any criticism of the issue and their response? How many other clients have they done this to that haven't gone gone public or created a PR problem for $27bn Slack?
The question is at what point the community response stops being beneficial and starts being harmful to the community itself.
I'd say this thread being high on HN's frontpage for many hours* has been beneficial. In addition to calling attention to Hack Club's predicament (and who doesn't love Hack Club?!), it gave a chance for many HN members to post their own relevant experiences, which it turned out there were a lot of—surprisingly many.
But in the later stage of this process, when the thread has basically done its job, drawn attention and generated a response, I think it's harmful to escalate even further and get into a tar-and-feather treatment of poor sods who wander in to offer a "sorry" or "we'll fix it". The dynamic at that point goes from "let's rally together and help these awesome kids, plus hey, something similar happened to us" to something darker and meaner. The former is good for this community, the latter is bad for it.
My point is that we should assess this based on how it affects us. That's handy, because that's information we can access, whereas we can't actually peer into $BigCo to find out whether what happened was a regrettable mistake or a nefarious grab they got caught at.
As long as I'm going on about this I want to repeat what I said in the cousin comment (https://news.ycombinator.com/item?id=45293388): the distinctive quality of internet indignation is unprocessed, opportunistic rage: unprocessed because it is pre-existing in a person (<-- and we all have this) for whatever original reasons that haven't been metabolized yet; opportunistic because it waits for justifiable occasions to lash out, and then lashes out with vengeance. This is not a great way to handle one's rage—it's a recipe for repetition instead of growth. How do I know that? I know it by self-observation, and I believe that anyone who wants to can know it by self-observation.
It's particularly important to know this in a group context. When a group joins together to vent rage—because an occasion justifies it, even though the driver in each person may be very different—that's when a group turns into a mob. This happens easily because it happens without awareness and no one intends it. This is when we become our ugliest, so we should pay attention to signs of it in ourselves and in our groups, and learn to respond differently. Not easy, of course, but a good use to put an internet forum to!
* something, btw, that the community corrected us about - we initially downweighted the thread, which was our mistake. Fortunately we like getting corrected by the community, so it was an easy fix.
The job isn't finished if a complaint has to go viral every time slack has an oversight and threatens to delete nonprofit chat data within 7 days. The comment you're calling unprocessed rage and tar-and-feathering just said it's more than a simple mistake. If anything your comments have been harsher to individuals.
Yeah I see how I could have given that impression, now that you say it. We do try to be careful not to single out or pile on specific users, but there's always more to learn about that.
I think there's a reasonable question about whether this was really an accident or something deliberate that they walked away from after bad PR.
Fixing the immediate problem is only step one. It's reasonable to ask for accountability and that they tell us about what they're changing going forward.
I use hanlon's razor here. Or perhaps a Bus Factor. Someone envoying for this situation got laid off or left, there wasn't proper documentation to track the issue, someone else picked up a warning in their feed and they launched out an email as they'd normally do, without reading into the context of the situation.
Their envoy is out of the loop so when Hack Club tries to respond they are at best rejected as some spurned rouge customer, and at worst completely ignored as they fail to reach anyone who has the power to properly look into it. So they have to go nuclear and make things public just to get the attention of a billion dollar corporation.
The fix, if any of this speculation is accurate, is indeed cultural. One counter to the current culture of tech trying to lay off as much as they can and letting Customer Service rot on the wayside. These PR crises were long determined as an "acceptable risk" of such cuts.
I don't think our engineer quoting Rob upstream has anything directly to do with this (maybe Rob does, but that's too speculative even for this post), but I do think we need to bring some shame back to corporate America. This is indeed endemic at multiple companies, not just Slack. I hear this is one of many reasons companies prefer to deal with Chinese companies; these kinds of CS slip ups just doesn't happen in their culture as regularly as the US.
I don't know about "accountability" - that word tends to get weaponized, and I'm not sure who is accountable to internet commenters or why we internet commenters feel they are accountable to us. But of course it's fine to ask what happened, what will be changed, etc. That's orthogonal to the rage thing though.
Well, e.g. I am at a nonprofit using Slack and would rather not get rugpulled in the future. So I'm particularly interested in any evidence that Slack can give that this was an isolated, unintentional circumstance and won't happen again.
I don't see how my comment above could be interpreted as any sort of personal attack or tar-and-feather behavior towards the person I replied to. This is a discussion about a bad business practice at a major company, and that is what these concerns are voiced against, not any one individual person who is acting as a spokesperson.
I interpreted it that way based on lots of past experience with the dynamic I wrote about upthread. I believe you that you didn't intend it to come across as hostile! The problem is that intent doesn't communicate itself, especially in short critical comments. The way I usually put it is "the burden is on the commenter to disambiguate" (https://hn.algolia.com/?dateRange=all&page=0&prefix=true&que...)
I apologize for using your comment as a place to hang a whole generic thing about mobs and whatnot—I certainly didn't mean it about you personally (or even your post) - it's a shared group phenomenon for sure, and I could have made that clearer.
From what I can tell the "tar-and-feather thing" is outrage directed at Slack and its CXOs, rather than the poor guy who happens to be reposting a message from the CPO.
Please don't let your moderator's concern for injury to individual people blind you to the fact that the outrage triggered by outrageous conduct is directed at the outrageous company and its officers, rather than at individual folks who aren't in a position with any real power.
As an internet commenter, I expect vendors to be accountable to us precisely because we provide them free marketing in exchange for, well, attention of us, and our fellow commenters and readers.
In my days of heading R&D for a regional social networking site, we discovered that first ~100k of our users were both the most valuable ones, due to the extent of their interaction with the site, and due to the fact that their risk tolerance for our /new/ product meant they would also tolerate future products. As such, that "first wave" of community around a product - is - the wave the creates the market for the product.
In case of Slack - they were taking that goodwill for granted. And the community's outrage called that bluff. It highlighted to other readers (like myself, I don't use Slack anymore so never paid attention to the ownership change) that it's now part of Salesforce (and that's a negative signal for me, might be positive for others); that it got pretty dubious business practices (as others in similar situation to OP have spoken up); and that none of the CXOs' committed to meaningful (from my and community's perspective) responses - post mortems; blast radius; accountability; data export.. which means either they don't have the power to make such commitments (wouldn't be the case pre-acquisition), or don't want to make them. Another negative signal.
HN moderation is routinely put in front of the most interesting dilemmas! Your response is, of course, sensible. Let's hope that if Slack does something similar to another non-profit, then it will rise again on the top of the front page, so that it doesn't end up being a story of "I got my free pass because I was lucky enough that the press talked about me", when others get a similar treatment, without the deserved PR nightmare that comes with it.
I mean, objectively, unless it was an honest mistake, which we can generously assume because this is HN, this was a really cheap shot, worthy of Broadcom and friends.
It's not your place to attempt to moderate perfectly reasonable posts just because the overall "feel" of the conversation seems off to you. The parent post is fine, stay in your lane.
As an aside, there's plenty of hardly subtle trolling you're letting by on the daily, usually the older the user somehow the more leeway there seems to be, so I'd suggest you focus your moderating attention on that.
> Please don't pile on like this when someone is showing up to fix something.
how do you know they're "showing up to fix something" and not simply servicing the "10% returns" end of a widespread scheme to shake down customers? This has every bit the look of "shake all the low-paying customers down as much as possible, if one of them manages to raise too much awareness, act like it was an isolated incident".
It matters a lot of this is an isolated incident or if this is par for the course; in the latter case, responding to those customers that were lucky enough to go viral is just part of the scheme proceeding as planned.
I don't know, of course. What I do know is the effect of repeatedly assuming the worst about other people and pounding them with unprocessed rage, which is what internet indignation is all about. The effect is that it poisons community. Since we want a good community, we should avoid doing that here.
I suppose people get automatically annoyed because who the owner of Slack is. It is reasonable to assume bad practices if the company is too large to care, have multiple prior bad incidents etc - that is why people automatically assume guilt with companies like Oracle, Comcast, Salesforce etc etc. If the company in question was a small 50 person outfit or unknown, people might assume it was an honest mistake or at least give benefit of the doubt.
Not saying it is right or wrong - just pointing out that people's patience is in short supply when it comes to mega corps, simply because of their very bad track records...
I agree that we shouldn’t pile on and assume the worst. However, multiple comments have asked what Slack will do to ensure this doesn’t happen again, which is important pressure to put on the corporation so that they can show (and not just tell us) that they truly are committed to fixing this problem.
Yes, and that's the frustrating part of it all. I'm tired of turning the other cheek for companies that are ransacking us financially and exhausting us emotionally. It shouldn't take a public drama for a business to be proressional. Clearly leaving it as "we'll fix it, oppsie" isn't far enough.
I dont know that we should assume the worst but you are assuming the best, that's what irks me more here. my position is that we should be skeptical and demand (politely, civilly, that is all fine) more information about what is the nature of this mistake, why did it happen, and what do we know about the same mistake happening elsewhere? the parent post was just "this is a mistake, we're fixing it, giggles", I would argue that's insufficient.
Every HN user is a person regardless of where they work, and everyone here is posting first as a human being, same as you and I are. That's how we all need to relate to each other. Work affiliations don't obviate that, and there's no substantive point or question that can't be posted this way.
Here's the thing: the post says it was written in haste so I imagine they wrote it before they spoke to anyone at Slack. There is no way to verify malice.
It would have been better to first reach out to Slack and get a confirmation and document that. This way we would have evidence and Slack could not pull the oops card.
Moreover, relying on social media visibility to decide which mistakes get corrected and which don't is a really terrible system, whether intentional or unintentional, and I really don't like supporting companies where that becomes the case. At least in part because I'm not really the type to make the fuss; I'd rather just avoid the risk in the first place.
Hi everyone — Denise Dresser here, CEO of Slack. As Rob shared, this was our mistake. An oversight in our billing process caused the issue, and I’m truly sorry for the concern it created. As soon as our team learned about it, we corrected it and restored Hack Club’s nonprofit pricing.
Christina - we have reached out directly and are committed to working with Hack Club to ensure your workspace remains fully accessible and that you have everything you need to keep inspiring the next generation of coders. We’re reviewing our billing and communications processes so this doesn’t happen again.
> Hi everyone — Denise Dresser here, CEO of Slack. As Rob shared, this was our mistake. An oversight in our billing process caused the issue ...
An "oversight in our billing process" does not explain why one of your representatives demanded of a long-term customer:
However, two days ago, Slack reached out to us and said
that if we don’t agree to pay an extra $50k this week and
$200k a year, they’ll deactivate our Slack workspace and
delete all of our message history.
> As soon as our team learned about it, we corrected it and restored Hack Club’s nonprofit pricing.
The demand is reported as being made on 2025-09-16.
The post detailing same is dated 2025-09-18.
This HN submission is dated 2025-09-18.
Is it your position that "[as] soon as our team learned about it" is defined as when this HN submission was created and received so much attention?
To quantify what I mean by "immense", as a former developer advocacy leader at a large public company, I once modeled HN impact and would estimate this story to be equivalent to a low-to-mid 8 figure marketing spend.
The mistake wasn't just in the billing process (also, that's a HELL of a mistake), but in how awful your communication and customer service was to let it get this close to disaster (including a viral post).
Could you break down a bit more why this happened? From an external perspective it really sounds like some sales rep decided to pressure a non-profit to make their quota
Hell of a "mistake" to bill a nonprofit 4000% of their typical amount, with a side order of "we're deleting your shit unless you give us about one American truck in cash in 3 days."
Did you happen to review the linked post? TFA would've let you know they're moving off your platform because you sent their entire org into a free-fall panic with your error. Probably already lost it but, IMHO, a VERY generous bill credit MAY get you that client back. Maybe.
Edit: And like, I dunno, I wouldn't just tell someone how to run their business but I feel there should be more oversight in general before your company sounds out threats like that? Like I'm not saying my employer has never jacked somebody up when they're acting goofy, course we have, but that's a PROCESS that involves a LOT of people's sign off, where this reads like your billing script just posted an amount due to a client paired with a demand for money on an EXTREMELY tight deadline for ANY organization, really, complete with the aforementioned threat of deletion.
Like, maybe you should queue those and have an intern do a sanity check? I have a strong feeling you shouldn't have TOO many of these unless this mistake wasn't much of a mistake, right?
They're shaking everyone down, it's been going on for years. They want huge sums of money to maintain chat history. I'm watching orgs left and right move to teams, not because it's better in anyway, but because it's basically free.
"This experience has taught us that owning your data is incredibly important, and if you’re a small business especially, then I’d advise you move away too."
The OA who wrote the Web page that we are discussing has nailed this I think. They will go far.
i posted a comment saying as much but deleted it. I had a client 8-9 years ago where Salesforce showed up with a bill in the millions and said "pay up or your org/instance and all your data is gone". "Shakedown" is exactly how the client described it.
If you try to use the Slack APIs to scrape the data you will *quickly* run face-first into the insanely restrictive rate limiting they recently enacted to combat their customers using AI tools they aren't providing and able to monetize.
That being said, we were able to get full data exports in the past when we were merging two companies into a single slack instance. YMMV
When the org I was at moved away from Slack (due to costs) we used this method and wrote a little Python script to convert the main channels' JSON dumps into PDFs so we had a usable backup of channels.
Please do not include PDF and usable in one sentence. Setting up some simple Postgres with sonic for fuzzy search would be _usable_, but PDF is like migrating from Slack to Teams.
In this case we didn't need a long term solution for searchable data on Slack.
We did the migration in stages, basically this:
- Provide access to Teams
- Create all of the new teams / channels there
- Make Slack read-only but still keep the lights on
- Allow folks to search and reference historic data as needed with Slack
- Ensure everyone was moved over to Teams and felt ok enough using it
- Remove access to Slack
- Perform Slack export / PDF creation of important channels
- Attach Slack PDFs to important Teams channels
- Cancel Slack subscription
In the end, most people never even needed to use the PDFs because they got everything they needed out of Slack before access was removed, but they are there for peace of mind and a last resort.
We also took this as an opportunity to stop using chat as a source of truth for long lived information. Anything that should be stored long term made its way somewhere else (Jira, Confluence, etc.).
As a product, I like Slack a lot more than teams. Chatting is easier, the apps are better, reminders and scheduled messages, workflows, etc. Threaded conversations are much easier as well, and aren't artificially restricted to certain types of channels.
At a high level though, Salesforce is often seen as a predatory company. Prices are high and they will squeeze their users for every nickel (as demonstrated here). They will also monetize your data in ways that you probably don't want.
Teams chat is pretty bad, I agree. But it does have these benefits:
- Free if you're already in the Microsoft ecosystem, which most companies are.
- Microsoft is probably a better steward of your data.
- Teams video / audio calls are much much better than Slack huddles.
- That's pretty much it tbh
I'd bake them into a Sphinx static site. That gives you a free client side search index along with better navigability than sheets of paper. And you can target PDF if you still want it.
Well as per the article (and my own experience), the free tier only gives you public channels. The paid tier gives you everything: public/private channels, group chats (called MPIMs), and one-to-one DMs.
So yes, it breaks "privacy" (not that you should expect privacy when using a work Slack account).
IIRC, you have to do something called a "compliance export," which just like any other compliance feature (SSO, HIPAA BAA, audit logs, etc.) usually requires the highest plan. It's designed to add some extra friction so admins can't just add themselves to a DM from the main UI like they could with a channel, but it is possible.
We had dozens of channels with almost 10 years of business information in them.
Over time the business gravitated towards putting anything long lived into other sources but since migrating off Slack was essentially a kill switch on our data we wanted to make sure we had ways to access this historic data if needed.
There's no way non-developers were going to parse JSON files for text. We wanted a quick and dirty way to attach the archived PDF file for a channel as a file attachment to the new Teams channel. It gave everyone peace of mind that they could find anything later.
It all worked out in the end and was worth the few hours of dev time to make the 1 off script.
Btw I wasn't the one responsible for making the tech choice to use or leave Slack for Teams. I was the one who was tasked to help with the migration and help make things as streamlined as possible for the business to switch.
One of the biggest pain points was going back to a bunch of Google Drive, Jira, Confluence, etc. sources and finding + updating the links to Slack to be screenshots of the conversation. Another one was converting a bunch of Slack app / webhook integrations over. Teams is absolutely horrendous for this compared to Slack.
Mattermost is great, we've used it at a few places and it's very flexible.
Extensibility and integrations with learning management systems, as well as owning all your data, makes it sound like a great option in particular for an education-oriented organization.
And I imaging the AWS or GCP costs for hosting it won't be as high as what Slack wants.
You'd think so, but I've been hosting MM for about 6 years, and it's definitely gotten more user- and admin-hostile in that time. They've restricted really vital improvements to paying customers (basic stuff, like having a functioning search), removed existing features (like video calls) and started shoving in more advertisements and nags to upgrade to a higher tier.
The fact that they've ramped that stuff up so much in the last couple years does not bode well for the future, in my opinion.
My installation isn't associated with a business, it's just a chat board for about 30 people, so there's no question of me being willing to pay $300 a month for the privilege.
I'm sticking with Mattermost because there's no better option, and I've got hundreds of thousands of messages I don't want to lose. However, it isn't like they don't try to extort you just because they're better than Slack about it.
For what it's worth, Zulip has a Mattermost data import tool, and communities are an important use case when we set product direction.
While I can't promise we won't ever change our exact monetization strategy, we're not venture-funded, and thus are immune to the usual enshittification pressures. https://zulip.com/values/ has some context.
Is that using Jitsi or whatever it is? I thought that was third party? I actually set that up for work before realising that we all hate voice/video calls and would just prefer to type. :P
Hi, update here (this is Christina, Hack Club cofounder): looks like Hack Club is staying on Slack.
Thanks to all of you for the appreciation and support for Hack Club, and for listening to what we were going through. The support has been amazing. Hack Club has so many cool teenagers coding awesome projects, making friends and solving problems together, and it's great to see so many people championing them. We are glad to stay on Slack and want to do so much more with them together going forward.
Thanks to Denise and the Slack leadership team for reaching out here on hn, and in a call directly with me and Zach today. And thank you for restoring Hack Club's terms with improvements. We really appreciate it, and we're glad to be able to stay on Slack.
I just want to add that it was great to get to know Mattermost and the team- and the hack club engineers were actually pretty excited to move there. It's an amazing product and for it to be open source is awesome.
Definitely like to judge folks based on how they fix (systemically!) problems. That said, did any kids in the club voice concerns about staying with an organization which had such a [potentially] severe incident?
We don't know (but the norm is) if the original contract had a sunset clause.
Almost every special rate I have ever negotiated had specific clauses about when the rate will end, even if there was no specific date there's always something about "rate is reviewed annually" or similar.
I am constantly surprised by the number of people with "manager " in their title who don't know how to read a legal document.
The other thing is you cannot build anything sustainable by depending on the charity of a single company.
If a special rate that better fits an organization's usage patterns is "charity", then any rate that is not extracting the maximum amount of money from the customer is also "charity", no?
To some degree, reduced rates for non-profit organization and schools are not offered because large companies want to be nice, but because they want to catch future customers.
> If a special rate that better fits an organization's usage patterns is "charity", then any rate that is not extracting the maximum amount of money from the customer is also "charity", no?
Maybe, but that's not what happened here. It wasn't "a rate better suited to an organisation's usage patterns", it was, more precisely "A heavily/1% reduced rate."
No reasonable person can have the expectation that a discount of $195k on a $200k bill is going to continue forever!
No one is ever going to pay per-seat for tens of thousands of teenage volunteers. If you're an unusual customer (nonprofit, with lots of volunteers and program people in the slack) you might end up with a long term special deal recognizing those circumstances (charging you for employees but not others).
The biggest issue is the abrupt change in policy. Slack had wanted Hack Club's patronage and had supported it. (Shoot, getting Slack visible to tens of thousands of future decision makers instead of Discord where these users all naturally congregate was a major win!)
To abruptly demand a massive immediate payment after a month's worth of mixed signals, from a small nonprofit, is messed up.
> it was, more precisely "A heavily/1% reduced rate."
It's more a tacit admission by Slack that their pricing model can't possible work for orgs that don't match a strict employer-employee model.
Nobody would agree to pay per-seat for every customer who uses a support tool, for example (which is much closer to the model this nonprofit is operating)
Saying that only the 50 workers need to pay $100 a year, and not all the program participants, is a perfectly reasonable amount of money to pay for a chat server.
It doesn't matter that an alternate method of counting would be a lot more. They paid a reasonable amount for what they got.
$200k for this service is a joke, not the 'real' price.
No, you don't. You have lawyers to assist managers in legal matters. But you can't simply throw a contract at a lawyer and ask "What do you think?" All the terms need to be understood by the manager. It is however reasonable to ask a lawyer "What does this say in normal language?" and "Is there any provision in this thing that sticks out as being really out of line or would trip us up if we had to litigate it?" Understanding a contract is not difficult. I've negotiated contracts with some of the largest companies in the world over my career and it only worked because I was also reading the contracts and interacting with the lawyer as a partner.
In EU a vendor can amend a contract but it gives the client the opportunity to breach that contract without consequences.
On a smaller scale it happens on a monthly basis with telecomms - almost never with rates, but they amend privacy policy and stuff - as a customer a change in the contract gives you an opportunity to say you're not accepting new contract, within certain timeframe, and walk away.
I guess this is simmilar - they told them they are changing the contract, and under new circumstances they will have to pay this and that, but they are free to walk away and pay nothing.
Well, you can amend a contract, but you need to send the new conditions, and it gives the other party option of not accepting the new contract, which means either amending party needs to accept continuation under old contract, or dissolution of the contractual relationship with no fees/damages/etc for the party that didn't accept new contract.
The part that I find egregious is that apparently Slack didn't even send a new contract.
If your rates were raised and you have not received new contract, if you can drop the service at that point, they can't collect including any cancellation fees.
If you want to continue using the service, that's a bit trickier.
"We can change the terms at our discretion" is a line that gets the book thrown at you in court, at least in EU, and that's the start of the humiliation conga for whoever tries to claim such a clause.
You cannot insist on a clause that lets you change the contract at your discretion and having the resulting amended contract be valid without acceptance by the other party.
Hi, this is meant to be a friendly question so apologies if it comes out wrong. Why does Hack Club coordinate over Slack? Wouldn't a free platform such as Matrix, Jabber or IRC be more in the spirit of an educational environment? Also, as I see it, wouldn't it be cheaper?
You mean a chat company that raise $1.3 billion (!!!) and got bought for nearly $28 billion (!!!) is acting greedy?
Slack is IRC with bells and whistles. Like yes I get that group chat is a necessity for today’s workforce. But it is still just group chat, a solved problem from a technical point of view.
This makes me sad, maybe the next hackathon should be to engineer a scraper/RPA frankenmonster that scrolls through all slack history one page at a time, scrapes/screenshots all conversations and port them to another piece of software.
Everything that is not forbidden by the law is allowed. Is there a law specifically granting you the right to data held by another? Can my electric company legally withhold hourly usage data of mine even though they have it?
I know GDPR provides rights for access and portability, but I'm not sure if you have portability rights for content you didn't create (like messages sent to you).
> Then this spring they changed the terms to every single user without telling us or sending a new contract, and then ignored our outreach and delayed us and told us to ignore the bill and not to pay as late as Aug 29.
Last year Salesforce launched Agentforce and gave everyone a free year. Dreamforce is coming up next month, I wonder how many companies are going to find themselves in a similar situation to yours...
“For anyone reading this, we would really appreciate any way to contact people at Salesforce to discuss time to migrate”
You said someone had called you. Why is that person not your point of contact? Was it your account executive? Are they not returning your calls? When they called you with this ultimatum, what was their response when you asked why you weren’t given longer notice?
> Thank goodness you took the time to let us all know this....
Be honest; how many times have we seen this? company, org or person flat out rejects an open source solution (which, most importantly, would actually work for them!), gets charity from the proprietary supplier and then complains when that charity comes to an end?
How many more times must we see it?
When working FOSS applications are rejected in favour of a proprietary product, well, there should be some pain for that decision.
If, as a technical decision maker (manager, founder, whatever), you make an unusually poor decision, you should get blowback for it.
For a long time there was literally no need for any decision maker to go with a proprietary chat solution. Anyone deciding to go with Slack, from this point onwards at any rate, deserve all the scorn they get.
Probably worth it and possibly a great lesson for others.
Back in 2006 everything was self hosted, and chat was - everyone sharing each others AIM accounts around the room. Everything should probably go back to self hosting, including our servers.
The data and searchability is slacks main selling point. A lot of people don't get that.
I've been using slack for years, since they didn't have video chat or any of that.
There are countless chat apps, including IRC. Slack's offering is that I can find messages or files on some subject from years ago with little effort in a matter of seconds. The history is the product IMO. The free 90 day version is worthless IMO, and barely better than IRC etc.
Slack's name is supposedly derived from "Searchable Log of All Conversation and Knowledge".
I strongly disagree. The company I work at (sub-50 people) has never paid for Slack over our entire history (founded in 2009).
It's chat and it works fine. That's all it needs to be for us. We don't need to switch to IRC or one of the other countless chat apps.
We're never going to need to be indignant that Slack is suddenly asking us for more money and then rush to migrate. When they shut down the free tier, we'll take our ephemeral chat somewhere else.
I think the lesson is more to not to pay for ephemeral chat. If Slack will let you chat for free with 90 days history, don't get sucked into the paid version if you can at all avoid it.
I’ve not heard of getstream. Is your service open source and all data easily extracted?
This post serves as a cautionary tale about how privately owned walled gardens, no matter how pretty, leave you in a precarious position. I suspect being in control of their data and having an open source escape hatch is what’s driving the adoption of Mattermost.
we power chat for over 1b users. you are very likely using our chat (strava, nextdoor, match, adobe, patreon, and many others)
closed source but you can export your data when you want to. mattermost is an open source slack. we are more of an API/SDK to build your own in-app chat/messaging as you want it.
Hi, I'm Christina, (Hack Club cofounder). In addition to all of Hack Club's hackathons, technical challenges and afterschool clubs, we also run a fiscal sponsorship and that $11.4m includes the funds of all the groups that we sponsor.
Our actual budget in 2023 was more like $5m, and we usually raise between $3m-$7m a year in donations.
Then, suddenly, they called us 2 days ago and said they are going to de-activate the Hack Club Slack, including all message history from 11 years, unless we pay them $50,000 USD this week and $200,000 USD/year moving forward (plus additional annual fees for new accounts, including inactive ones)
For anyone reading this, we would really appreciate any way to contact people at Salesforce to discuss time to migrate because deactivating us in 5 days destroys all the work of thousands of teen coders at Hack Club and alum unnecessarily. We are not asking for anything for free. This was an underhanded process by the sales team to raise our rate exorbitantly from a qualified educational 501(c)(3) charity serving young developers or destroy all their projects, DMs and work forever. If Salesforce’s goals have changed- ok. Give us a reasonable amount of time to migrate- and don’t club us over the head like this. We have had an 11 year great relationship with Slack- and have introduced the company to many many future engineers and founders. My email if you can help us: christina@hackclub.com
reply