138
What brought you to Lemmy?
(lemmy.ml)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 25 Sep 2023
138 points (94.8% liked)
Asklemmy
43944 readers
496 users here now
A loosely moderated place to ask open-ended questions
Search asklemmy ๐
If your post meets the following criteria, it's welcome here!
- Open-ended question
- Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
- Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
- Not ad nauseam inducing: please make sure it is a question that would be new to most members
- An actual topic of discussion
Looking for support?
Looking for a community?
- Lemmyverse: community search
- sub.rehab: maps old subreddits to fediverse options, marks official as such
- !lemmy411@lemmy.ca: a community for finding communities
~Icon~ ~by~ ~@Double_A@discuss.tchncs.de~
founded 5 years ago
MODERATORS
What if Reddit and the government paid billions to the creators to fork over the servers and to make the source code and apps proprietary?
Unlikely considering their source of funding comes from various European governments.
Also, it's not very easy to make open source closed source. The original Lemmy code and documentation is already out there. The only thing they could do would be to add new features that are all closed source. (This is what reddit does, as their old code is open source.) At best, it would be a fork of Lemmy with closed source elements.
It's been established that you can't call backsies on open sourcing your software.
They could make new updates to lemmy proprietary, but what's out there is already out there.
Maybe not even that. Lemmy is released under the AGPL3. This means that modified versions of Lemmy have to also be released as free software under the AGPL3 or a compatible license. To release a derivative work under an incompatible license you would need to own the code or be given permission by each contributor to do so. For any contribution where you can't make a deal with the author, you would have to rip it out of the codebase entirely. Note that this is true for lemmy devs as well. If there is no Contributor License Agreement that states otherwise, they cannot distribute the work of other contributors under an AGPL3-incompatible license.
Right, I was thinking the "collective authors"; and to be fair, a small contribution could be replaced if tracked properly. If there's no CLA and there are a lot of significant contributions by various individuals you're absolutely right that it becomes impractical to the point that it wouldn't happen.