871–880 of 1001 posts
Slack just publicly apologized for this and said it was a mistake and they will be returning hack club to the previously agreed upon plan. Hack club staff are currently discussing whether or not to go ahead with the migration to mattermost anyways. (- a hack club member)
Earlier quoted context omitted.
If you have a bunch of coders, just scrape the data. Then turn your back on this greedy maw. We recently moved to Mattermost for the same reason. Not looking back.
Zulip is awesome too. On prem.
You all are amazing. Thank you so much to everyone who helped raise awareness and advocate for Hack Club. That wasn't the goal of my post yesterday (I mostly wanted to pre-empt #hackclub-leeks because I knew GitHub activity would show up :stuck_out_tongue:), but wow - you made a huge difference, especially @mahad's blog post that went viral. Thank you.
I have some great news. @Christina Asquith and I just got off a call with Denise Dresser, CEO of Slack.
She was incredibly apologetic for putting Hack Clubbers in this position and very generously offered to donate Slack Enterprise+ to Hack Club with a 5 year commitment. We think this is the best option, so we're going to move forward. Additionally, she is going to join us in-person at #athena-award's 200-person hackathon in NYC in November!
We hope this will be a great start to a renewed relationship as Hack Club has benefited tremendously from Slack's 11 year partnership. We're very grateful.
This means that all of Hack Club's history and bots will be preserved. Additionally, it will open up the path for a special Hack Club OAuth login flow to reduce friction for new Hack Clubbers and APIs to build better moderation tools.
Thank you to the enormous outpouring of support. There have been so many kind messages, emails, and even alumni from years ago reaching out. It's meant the world as we've navigated this difficult situation. @here
It's not like Slack is even that well-designed anyway. By design, it results in conversation fragmentation, with similar conversations happening all over the place. Once you have more than ~5 employees, people have a hard time keeping up. My dream work chat app: 1. Conversations happen adjacent to internal documentation, with agents constantly writing and updating the docs based on natural human conversations 2. Crea…
Found the manager. I would go mental without DMs
As a founder, if everyone is always DMing you, the knowledge is not shared with the team. You become the bottleneck for everything.
In sales, you end up having the #account-[customer] thread and about 4 or 5 DM groups with different internal people on them for each account. Lots of time bringing everyone up to speed when it could be more unified.
Sure, there are sensitive issues like employee conflict, salary discussions, etc. I'm not saying everything needs to be in the public. But I think DMs as they work in Slack cause more issues than they solve.
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.…
Hey, I'm Rob, the CPO at Slack (for real tho, this is my 3rd time posting this so please don't flag :pray:). This was a mistake. We're fixing it. We appreciate you, Hack Club, along with all of you that are Slack users following along :heart:.
Yeah, right. Tell us more.
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.
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.…
It's not like Slack is even that well-designed anyway. By design, it results in conversation fragmentation, with similar conversations happening all over the place. Once you have more than ~5 employees, people have a hard time keeping up. My dream work chat app: 1. Conversations happen adjacent to internal documentation, with agents constantly writing and updating the docs based on natural human conversations 2. Crea…
This is close to a lot of what's happening at Glue. Threads are first-class, so you can start a thread within a group - let's talk about our GraphQL schema and that thread should live in the API Development group. You can also start a thread without a group - just me and another 2 coworkers need to discuss a specific point that would be noisy for everybody else. Glue AI can be invoked at any time in any context and y…
Earlier quoted context omitted.
(Hi - I'm an engineer at Slack -- reposting from our chief product officer Rob Seaman): "This was a mistake. We're fixing it. We appreciate you, Hack Club, along with all of you that are Slack users following along :heart:." https://news.ycombinator.com/item?id=45291980
When something happens on this scale, you cannot call it a "mistake." This is more than a mistake, it's a culture.
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.…
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…
The real fallout from today may be hard to take account of.
I can't be the only one who saw this situation unfold and decided "I'll be certain to self-host if I ever set up something like this"