Selfhosted
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
-
No low-effort posts. This is subjective and will largely be determined by the community member reports.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
view the rest of the comments
My understanding was (perhaps wrong?) that the "Mattermost Team Edition" is offered under the AGPL, and then the "Enterprise" Editions (starting with the "Entry Edition") have additional restrictions (including the 10k message limit in the "Entry Edition" that everyone's been talking about). They do a good job of hiding the "Team Edition" (it's almost like the don't really want to have to offer an open-source editions... 🤔), but it is there if you can find it. https://docs.mattermost.com/product-overview/editions-and-offerings.html#mattermost-team-edition
This seems like your standard open core/dual licensing, CLA controlled BS where open source is indeed treated like an inconvenience... Perhaps with more obfuscation than on average. Probably not really adding requirements on top of AGPL as such but they seem to be offering multiple releases under a more restrictive license either because they have the rights so they can do dual licensing or they keep certain components proprietary and don't offer those with the team/community editions.
So yeah, probably within their legal rights and I assume there is still a codebase/release that you can use under the terms of the AGPL but they do seem to be looking for ways to make it be used as little as possible.
I could be wrong if the AGPL and other open source parts aren't enough for actually compiling a functional version of this but this is what it mostly looks like to me.