It was lying about the Apollo developer for me. He lied, he got caught, and then said (paraphrasing), “wow, he’s a terrible person for recording our conversation without my knowledge! I don’t want to work with him anymore anyway!”
I don’t mind if reddit wants to make some money on their API, but giving app developers barely a month to respond, having insanely high prices, throwing away the relationships they built with app devs, and not responding to community feedback around the issue at all was all too much.
It was the AMA that was the last straw for me, on top of everything before. It had been going downhill, but that was where I lost all hope it would improve.
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.
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.
The reason for the Reddit protests could have been justified, but the CEO’s response couldn’t.
He messed up, doubled down, and then continued to mess up. I don’t know why the rest of the team let him keep talking
It was lying about the Apollo developer for me. He lied, he got caught, and then said (paraphrasing), “wow, he’s a terrible person for recording our conversation without my knowledge! I don’t want to work with him anymore anyway!”
The nature of bad faith is that there is no right answer.
deleted by creator
That’s what sold it for me.
I don’t mind if reddit wants to make some money on their API, but giving app developers barely a month to respond, having insanely high prices, throwing away the relationships they built with app devs, and not responding to community feedback around the issue at all was all too much.
It was the AMA that was the last straw for me, on top of everything before. It had been going downhill, but that was where I lost all hope it would improve.
That is capitalism man 🤷🏽♂️. The CEO is emperor.
Truth. Lemmy by design resists the influence of capital by being federated.
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.