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
Thanks for creating Lemmy! I like it a lot :) Do you have any ideas/plans on a privacy and user focused algorithmic view? If Lemmy wants to be big, I think we need something like this.
I would love a way to optionally post a location while choosing specificity, i.e. United Kingdom vs Newcastle etc. That way I can filter communities and posts to just those in a location I like.
I think it could lead to some really cool interactions and ways of looking for things.
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.
Disk space is definitely not an issue for us w/ postgres, or any text data really. The entire wikipedia english text data, is ~20GB. Images are the main disk-space concern for servers.
A backup of lemmy.ml's DB is only ~1.8 GB currently, and that's 3+ years of data.
We have no plans to move away from postgres, and lose all of its features and performance.
Will you implement an sorting algorithm that would show more content from small, neglected, unknown communities/instances on the main /all/ timeline so that they are more discoverable and will be seen rather than only showing the most-liked posts from huge communities/instances?
Any thoughts on the "federated community" discussion? I find both positions to have merit, but I think I'm leaning towards community aggregation as an option.
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.
What do you think of owls?
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.