Why is lemmy licensed under the AGPL3? What prompted you to take that decision?
Announcements
Official announcements from the Lemmy project. Subscribe to this community or add it to your RSS reader in order to be notified about new releases and important updates.
You can also find major news on join-lemmy.org
Its a good hard copyleft license, and since its used in a network setting, the AGPLv3 over the GPLv3.
With instances already disappearing (eg. vlemmy), content is being lost. Are you considering a lemmy archive?
For communities that have been federated, their historical data, posts, comments, etc should still be available on other instances. So in a sense they're already archived.
Besides that, we have a backup / restore guide on the join-lemmy docs that show how to backup your DB, which every server should be doing.
Every instance automatically archives content from other instances that it federates with (though this doesnt include images). An archive sounds like a good idea, but we certainly dont have the capacity to take on another project. It would have to be done by someone from the community.
How much experience did you have with Rust when you started making Lemmy? What programming languages did you use before?
Just a little, on a few side projects. But lemmy was the one that I used to teach myself rust. Before I was mainly a Java developer.
Having a good idea + learning the new thing to program it in, is one of the best motivators for me, as I'm sure it is for a lot of devs.
A few questions:
- Why did you name it Lemmy?
- What have some of the biggest challenges been in developing a Reddit-like community platform?
- What's a big feature you hope to implement someday?
- https://github.com/lemmynet/lemmy#whys-it-called-lemmy
- For me at least, the DB has been the most difficult.
- Notifications / unified push is something I'd love to have, but given the limited time I have, its in the far future.
Why isn't there a feature to allow individuals to block whole instances?
What are your opinions on third party apps for Lemmy using ads on their free version?
Any regrets during your time working on Lemmy? Like implementing a feature and then later on thinking "Shit. This sucks, but I can't remove it now or it will fuck up everything later."
Why are Lemmy devs so opposed to a Follow Thread feature? (The feature request is always immediately closed on github with the message: not planned)
Users being able to opt in to receive updates whenever a thread receives an edit to the post, a new comment, or a reply to a comment thread would be extremely useful.
Thoughts on a GPL4?
Many examples indicate an even stronger license is needed, I will list a few
-
The current RedHat debacle
-
MuseScore's closed source Musehub (after being acquired by Ultimatw Guitar)
-
Google commiting copyright infringement by combining free (as in freedom) software with code under Apache license for Android
We clearly need a stronger, more all encompassing license.
I'm not too familiar with it, but I'm always open to moving to stronger copyleft-licenses, if the AGPLv3 is proving inadequate.
- What are your dream features or rework you would ask a magic genie? I mean nice features that require a huge amount of work
- If you were to rewrite Lemmy from scratch, would you do everything the same way or would you rethink something?
While I'm only a collaborator and not a maintainer, your second question is kind of reality already since there's a UI rewrite in a very early state to use leptos instead of infernojs.