Lemmy maintainer
If you install with ansible it should be included by default. You can check if your nginx config contains the cache lines. There is also a line you can uncomment to see the cache status with each request.
https://github.com/LemmyNet/lemmy-ansible/blob/main/templates/nginx.conf#L71
Did you try to setup caching? That could reduce server load a lot.
This would be neat to generate forum avatars, to show something similar to your real face.
The post yes, but not the comments at depth > 50.
No the max comment depth is generally lower now. However this doesnt affect comments created before upgrading.
Changing post.url from varchar(512) to varchar(2000) really messed up database performance so lemmy.ml became unusable. Turns out that column statistics are removed when the type is changed, so we had to run analyze as part of the migration. Seems like a bug in postgres.
https://github.com/LemmyNet/lemmy/issues/4983#issuecomment-2446945046
Dont think I did, it was really a team effort. And in the end the working solution was suggested by @phiresky@lemmy.world, thanks for that!
It will be rejected by the api (or by federation).
Correct, I suppose the ban button could be hidden from the ui in that case.
The average peasant in medieval Europe would certainly never see an African person in his lifetime.
Some people get faith and hope from Christianity. Or Islam, or Buddhistm or others. Nothing wrong with that.
Maybe there never was a real Jesus.
In case of Lemmy most initial users came from subreddits that were banned, specifically communist ones. But that is unlikely to work for Ibis, as people banned from Wikipedia have many alternatives such as setting up Mediawiki. Other people who joined Lemmy early were excited about the technology, and open source in general (which is why those topics are still so popular). So open source and fediverse enthusiasts are more likely to join.
Besides Ibis is still in a very early stage, so far there are not even any mod tools or account settings. So for the moment its more important to get programmers, designers, testers and other contributors to develop the project. Once some of these major features are implemented, it will make more sense for general users to join. But I dont have a specific plan for growth, hopefully growth will simply happen organically over time like it did with Lemmy.
Do you think all of lemmy.ml is a single person? In this case its just the decision of a single moderator, nothing to do with admins.
What a shame, I spent a lot of time working on syncthing-android (probably around four years). But in the end I stopped for the same reason, it’s very demotivating to be so reliant on a corporation like Google which is entirely indifferent or even hostile to open source apps. Every year with the new Android version there are new required features or mandatory changes to implement, and if you don’t comply they don’t allow publishing new app versions. That’s not a big deal for commercial apps with fulltime developers, but it’s a lot of work for small apps maintained by volunteers. And it’s never anything that would benefit syncthing-android or it’s users, just busywork that takes away from bug fixes and feature development.
The good thing about open source is that someone else can always pickup and continue the work. Google’s shenanigans were what drove me to server administration and backend development, which finally led me to work on Lemmy. The experience with syncthing-android definitely taught me a lot about how to run a popular open source project.
Right I will also have to make a template with these common parts of the release announcement. Instance blocking is not implemented yet, but it uses the same federation library as Lemmy so that will be easy to add when its needed.
If there are still problems you should open a new issue. We cant leave issues open forever because they go stale and dont account for new features. By the way we are planning to implement multi-communities.