What inspired you to create Lemmy?
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
A bit late on this, but when can we expect the new rewrite of Lemmy's UI? It seems like a big task.
@dessalines yesterday, I asked around about the desired improvements to Lemmy and @bmp replied that conversation flows could be improved. Threads or comments aren't always explicitly showed and makes the user unsure about how to actually interact in the conversation.
Also, what are your next points on the roadmap? (If you have one)
First of all, thanks for the great work!
How's the onboarding of the new contributors going? I assume suddenly getting a huge influx of eager contributors might create a lot of fun "problems" that software developers don't usually get in their day jobs.
Related to that, besides the contributor docs on join-lemmy, is there any recommended reading before getting down to work on starting to contribute (already made or in the works)? I've been looking into helping out and getting better at Rust in the process.
Where did the Lemmy name originated from? How long was the development of Lemmy?
The name is explained in the docs. We worked in Lemmy fulltime for over three years now (and around one year before that in our free time).
https://github.com/lemmynet/lemmy#whys-it-called-lemmy
The first commit was in Feb, 2019, and of course we're still going!
A bit technical question: how do you manage to build performant comment trees on frontend?
What's your oppinion on lemmy being used by a few hundreds of people for quite some time and then recently exploding overnight with new instances and tens of thousands of new users. That certeinly changed some things...
- How do you feel about ads on the internet?
- What are your thoughts on the sustainability of FOSS?
I know about your decision regarding Threads but what are your thoughts on the blog post from the Mastodon CEO? https://blog.joinmastodon.org/2023/07/what-to-know-about-threads/ especially the address to the EEE concern
- 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?
Thanks for your amazing work, you guys are changing the world!
- The biggest ones I can think of, are the re-write of the UI in rust / leptos, and notifications using unified push. Those will both be a ton of work, and its going to be hard to carve out time to complete them.
- The back end has gone through plenty of refactors, and we place an emphasis on code maintenance, so its stayed up-to-date. The back-end and DB stack all seems future-proof so far, so I wouldn't change anything.
Thanks!
Why is selfhosted Docker such a mess?
And following up: since Lemmy-easy-deploy is so… well… easy, can’t you make that official as well?
Have an advance option where one could configure everything and one where all is done and automatically works for the somewhat less technical admins?
What is a mess about it? Its certainly much easier than installing without Docker.
Why is ALL administrative documentation all but absent? Why is there NO documented support for SMTP?
What documentation do you need other than knowing the config fields?
Is there any limitations with the database (postgres)?. I know postgres is one of the best (maybe even best) monolith database (running on one node) at the moment, but will the space be enough? With this in mind, has there been any consideration of migrating to a distributed database like ScyllaDB or CassanraDB to alleviate potential space constraints? On the other hand, if Lemmy doesn't intend to store data for long periods, maybe the capacity of Postgres would suffice. Any thoughts or plans on this? I appreciate your insights on this matter.