[Agreed3750]

According to the Slack HQ account on Reddit, the situation has been resolved: https://old.reddit.com/r/Slack/comments/1njuchb/why_is_slack...

>We made a mistake. >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 value the work Hack Club does to inspire and educate young people in coding and technology, and we regret the concern this situation has caused. We will be reviewing our billing and communications processes to provide nonprofits clearer guidance and adequate grace periods as they grow.

[DirkH]

I wonder if anything would have been done if there wasn't a public uproar.

[rybosworld]

The answer to this is nearly always "No"

[coder543]

> the situation has been resolved

Slack cannot unilaterally “resolve” this situation, and their proposed solution doesn’t seem to address the concerns that were raised in the first place.

[quacker]

Yes it does. They don’t have to pay $200k/yr + $50k immediately, and don’t have to spend the time, effort, and money on self-hosting and migrating away.

[jama211]

It solves it for this one client. It doesn’t provide any transparency on exactly how this occurred (like you would for say, a data breach) and provides no guarantees (only words) that this won’t happen again, or any guarantee that this isn’t happening to any other client right at this moment!

[alwa]

“to provide nonprofits clearer guidance and adequate grace periods as they grow.”

So… still $200K for a scrappy nonprofit, just a month’s lead time instead of a week. Got it.

[rollulus]

“Oh shit, we’ve been on HN #1 for a day, how do we control the damage”

[Havoc]

Classic "I'm sorry we go caught"