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).

With pleasure :)

You’re welcome :)

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.

Thank you, fixed!

In principle it’s finished, but last time we put it on lemmy.ml for testing there were performance problems and we had to revert. So far it’s not clear what caused those problems, so we need to try again somehow.

To decide if I should merge the linked PR or not (I did merge it).

Thats even more verbose so the second option is better.

@DemocratPostingSucks@lemm.ee @Deebster@programming.dev @al4s@feddit.org Thanks for the feedback! Personally I prefer the first option, but based on your comments I will merge the PR with the second option.

Good reply, like you explain this wouldn’t work. Just one thing:

Lemmy doesn’t aim to be an uncensorable platform.

https://join-lemmy.org/docs/users/05-censorship-resistance.html

@threelonmusketeers@sh.itjust.works This. If youre interested to work on this feature or others, feel free to ask for guidance in the relevant issue, or in the dev chat.

No that’s not merged yet, still needs more feedback from plugin devs.

The key is refreshed after 24 hours so it will work if you wait a bit.

There were optimizations related to database triggers, these are probably responsible for the speedup.

https://github.com/LemmyNet/lemmy/pull/4696

No that’s a completely different issue.

Yes something seems to be broken, but so far we don’t have any idea what it might be. On Monday we will deploy the 0.19.4 release candidate which has various performance improvements, hopefully that will help.