this post was submitted on 12 Feb 2026
254 points (96.7% liked)

Selfhosted

60542 readers
668 users here now

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:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details.

  8. AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] stuner@lemmy.world 4 points 4 months ago (1 children)

I think the problem is that the license grant (that has been in place for a decade) is not that clear.

You are licensed to use compiled versions of the Mattermost platform produced by Mattermost, Inc. under an MIT LICENSE

  • See MIT-COMPILED-LICENSE.md included in compiled versions for details

You may be licensed to use source code to create compiled versions not produced by Mattermost, Inc. in one of two ways:

  1. Under the Free Software Foundation’s GNU AGPL v3.0, subject to the exceptions outlined in this policy; or [...]

I read it as releasing the binaries under MIT and granting people an AGPL license for the (non-enterprise) code. Some read it as not granting you the full AGPL rights.

To me, the fact that they advertise Mattermost as "open-source" and the statement on the "reciprocal license" above indicates that Mattermost also reads this as an AGPL license grant. However, they don't seem to be interested in fully clarifying the license situation. But, I think they would have a very hard time to argue in court that this license doesn't allow AGPL forks. And I haven't seen any evidence of them acting against any of the existing forks.

[–] boonhet@sopuli.xyz 6 points 4 months ago

AGPL is restrictive so actually having MIT is a backup option weakens the AGPL license. And in particular having the ability to ship closed source binaries if you wish to, under a commercial license, means AGPL means jack shit here to those who want everything to be copyleft