We also added a new maintainer, @flamingos@feddit.uk!

No we dont have any benchmarking infrastructure. Maybe one of the instance admins will report some results later.

Sorry I said it wrong, reports do federate but only in a limited way. Particularly if you moderate a remote community you wont see the reports. Also the action of resolving a report is currently not federated at all. Both of these are fixed with the PR above.

This sounds like the same problem you reported before. Only thing I can think of is to get in contact with the maintainer of lemmy-cross-toolchains

I implemented reports federation recently, in current versions it is not available at all. So you may have to wait until version 1.0, though @MrKaplan mentioned that he plans to backport it to 0.19.x

Edit: Nevermind I was talking nonsense. Reports do federate, but only in a limited way. Particularly if you moderate a remote community you wont see the reports. Also the action of resolving a report is currently not federated at all. Both of these are fixed with the PR above.

Yes we renamed it.

Yes the current api v3 is also available in 1.0 alpha

What feature requests will be implemented after 1.0? Everything that’s open on the issue tracker really, as soon as someone works on it.

The final api version would probably be in 1.0-beta.0, which will still take a few months. But at this time you can already start to adapt for the major changes like combined endpoints, and give feedback if anything else in the api needs changing.

Yes we always release backend and frontend versions together.

On the other hand it gives an indication to client developers that such big breaking changes wont be a regular occurence. So they have a reason to upgrade and then keep using 1.0 long-term. I believe that practically all the needed breaking changes are already implemented, and remaining issues are mostly new feature requests which can be added as new api endpoints or parameters.

It’s like Blaze says, we are already working towards version 0.20 now which will have various breaking changes. There will be an announcement a while before the final release to let developers know about the changes. Also the current api v3 will still be available for backwards compatibility.

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

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.

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

No that’s a completely different issue.