Yeah, the Lemmy algorithm has changed in the last few releases and they are trying to promote more local content in people’s feed. But there hasn’t been a new version in a while, so not sure why it’s showing up for you now. Better late than never maybe. :)

Yes.

I think this update has been very problematic in many areas, and in hindsight, we should have waited a few more weeks to update.

Previous updates have not had major problems, but we knew this was a very big update with a big rewrite of how several things work (like federation), so it would have been smarter to wait longer than a week to update.

Unfortunantly there is no way to go back to previous version now, since the 0.18.5 to 0.19.0 update upgraded the database schema as well.

The developers of Lemmy are working on fixes. I know they reopened github tickets where federation was supposed to be fixed. And there are many other issues as well: https://github.com/LemmyNet/lemmy/issues

You can search there and see if anyone else has reported simular issues, and otherwise create a new issue and report the problems.

Next time we will wait longer to install major updates from 19 to 20 and so on.

Edit: Im also getting “Incorrect logon” messages while using the web interface, but it doesnt seem to have any effect. I dont get logged out. But another bug somewhere.

Thank you, very good to know.

My idea was to try and see what specific query is failing in the database and go from there, so currently enabling logging of failed postgres queries. Hopefully see something in those logs…

I would like to roll back but the database schema changes would mean having to restore a backup. And potentially end up in more issues just like you were thinking too.

I guess it’s best to wait for a fix, and I will also see if I can troubleshoot this myself a bit. I’m guessing it’s a database issue since I can see very long running update statements on every restart, and they may not be able to complete for some reason.

I did another restart and your comment shows up in the thread.

So seems to be some bug that makes it stop federating after it has polled the queue once.

Indeed, it hasnt federated. So the restart of Lemmy polls the queue and then it stops working again. :/

Yeah I think the way outgoing federation works now in 0.19 has been rewritten to use a queue. So no comments or posts should ever be lost with this design, but there seems to be a bug causing the software to not process that queue sometimes I guess.

I think it was Lemmy software stopping to federate for some reason, and after i did a restart of Lemmy, it federated everything in the queue right away. But its worrying that this can happen, and I assume its a bug somewhere hiding in the software still.

I did a restart of Lemmy software just now, so I guess that made federation start to work again. But Im worried now it will stop again at any time. Will post a question in AskLemmy and see if anyone else has similar issues.

I can see the comment on kbin now after restart of Lemmy software:

It really seems like outgoing federation is buggy in this version. :/

I tried a quick restart of Lemmy to see if posts and comments are federated now after restart…

It seems to have made comments federate, but its worrying that it can stop working in this version. I have posted on AskLemmy, will see if anyone else has similar issues.

Thanks a lot, it made me look at this thread right away.

I posted above, but I think its still bugs in 0.19.1 that was supposed to be fixed in this version…

This seems very related to the update of Lemmy software to 0.19.1.

There was a critical bug with outgoing federation in 0.19 that was supposed to be fixed in 0.19.1:

https://join-lemmy.org/news/2023-12-20_-_Lemmy_Release_v0.19.1_-_Outgoing_Federation_fix

I would say it seems the bug is not fixed…

We changed some settings and now the alternate user interfaces are back. Keeping an eye on server performance… :)

deleted by creator

Yeah I like it too, its awesome!

I had to disable it temporarily though since it was hammering the server for some reason, and we are not quite sure why.

Will post an update as soon as we know whats going on… :)

But hey, richest company in the world need to eat ok?

/s

Probably just a matter of prioritization I guess. The dev team for Lemmy have a lot on their plate now. I looked at the github repo and it’s a lot of issues… As with any big popular project.

But from what I’ve read, I think it’s scheduled for Lemmy 0.19 in about a month…

So far we have managed to not block any other instance and I hope that can continue. :) I don’t feel instance owners should make decisions for their users. Besides, it’s going to become possible to block instances on user level in Lemmy soon I think.