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.…
Isn't changing the terms of a deal without even sending you a new contract pretty much illegal anywhere sane? Even between business entities?
Do you mind me asking if you'll be self hosting mattermost? If so they're moving to a 1000 User hard limit for self hosted instances. https://forum.mattermost.com/t/solved-is-there-any-limitatio...
That discussion also mentions: "Framasoft is maintaining a soft fork called Mostlymatter that removes the arbitrary user limits"
We're using teams in my new company, which is awful for textual communication (lacks threads in chats, groups are more like old forums than new IM). I've been experimenting with self-hosted Mattermost but it seems that it also requires paid license in some situations (e.g. does not have groups for some reason in the free version). I was unable to find another system. Would anyone recommend me something?
I get the sense that Mattermost is the same kind of eventually-get-you-paying play as Slack. Other threads are mentioning Zulip, which feels more old-school free as well as Free open source.
We should stop letting ourselves get suckered into these proprietary systems. Same with Discord. It may look great now, but there's still a company behind it looking to extract as much profit from it as possible, and eventually it will get enshittified. We know this. We've seen it happen dozens of times. We really should stop falling for it.
Open standards, easy migration, and servers you pay an honest cost for. Self-hosting, perhaps even. That's where we need to go.
Since you're a nonprofit that teaches coding, it could be a great time to consider self-hosting a FOSS chat tool. Suggestions: Campfire [0] or Zulip [1]. Also, if the data in chat is being held hostage, the org might be using chat wrong. Right tool for right purpose. If starting over, perhaps consider if it would make sense to put that documentation or whatever it is that will get "lost" from Slack into a wiki or rep…
Zulip is awesome. Super easy to self host. Upgrades go very smoothly. Their thread title concept is great (though they are relaxing its requirement lately). The only thing you don't get if you self host is the mobile notifications. This happened recently and it's a bummer but that's what they came up with to monetize the project, as is their right. Paying $5000 for chat is ridiculous to me when such good alternatives…
Still, crippling the self-hosted version feels like a red flag. Later on, they can easily introduce more features out of self-hosted version. That makes me feel more like ‘we’re business first, but we allow you plebs to contribute towards our success for free’ instead of ‘we’re business and we’re contributing into the community, and as a bonus, the community helps us back.’
Hi! An official announcement from Zach Latta has been made in the Hack Club Slack. We're moving to Mattermost now and we're trying to export all messages, DMs, etc. Disclaimer: I am a member of Hack Club's Slack and NOT a working personnel there.
Not sure if you saw this, but another user pointed out that Mattermost is moving to limit self-hosted instances to 1,000 users: https://forum.mattermost.com/t/solved-is-there-any-limitatio...
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.…
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.
I think what they did is slimy as hell, but it's hard to side with anyone using Discord, Slack, et al for doing community based support and building a knowledge base. This was not an issue in the era of forums, that supposedly were replaced with SaaS closed communities because of spam...
Zulip is awesome. Super easy to self host. Upgrades go very smoothly. Their thread title concept is great (though they are relaxing its requirement lately). The only thing you don't get if you self host is the mobile notifications. This happened recently and it's a bummer but that's what they came up with to monetize the project, as is their right. Paying $5000 for chat is ridiculous to me when such good alternatives…
Still, crippling the self-hosted version feels like a red flag. Later on, they can easily introduce more features out of self-hosted version. That makes me feel more like ‘we’re business first, but we allow you plebs to contribute towards our success for free’ instead of ‘we’re business and we’re contributing into the community, and as a bonus, the community helps us back.’
The problem with push notifications is that they need to go through the app provider and incur costs for it, that's not really their fault. If they'd not charge for it, they'd still go through their servers and would lose them money. So putting it behind a paid service you hook up to your self-hosted instance seems fair.
If you want to avoid it you'd need to build patched versions of the app and distribute them yourself to your users, so you pay Google/Apple directly for notifications instead of going through Zulip.
Do you mind me asking if you'll be self hosting mattermost? If so they're moving to a 1000 User hard limit for self hosted instances. https://forum.mattermost.com/t/solved-is-there-any-limitatio...
That discussion also mentions: "Framasoft is maintaining a soft fork called Mostlymatter that removes the arbitrary user limits"
Yes, I mean they are not difficult to remove, but I think it would be fair to add the context that they're going to have to fork it. E.g open source is not a panacea either, they will likely also struggle with postgres being a bottleneck for that number of users (particularly on search), the redis integration is not part of open core.