this post was submitted on 25 Jun 2023
61 points (98.4% liked)
Lemmy Support
4652 readers
1 users here now
Support / questions about Lemmy.
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
There could normally be some latency waiting on a server response, but you'll still get the feed even though it says pending. There is a problem where it can get stuck in a pending state, but I thought it was resolved in the recent 0.18.0 update for Lemmy. Though some admins are holding back until 0.18.1. Lemmy.ml has updated, but maybe both the local and remote instances need to have the new version. Kind of a bummer, I really want the fixes in 0.18.0, but I think the admin of my login instance is holding out for the 0.18.1 version.
They scraped captcha support in 0.18.0 and only opted to add it back in after massive instance admin protests. In the middle of a bot-wave, that was a major dick move. Captcha is not infallible, but it sure gets the majority of script kiddies out. The good thing is that the feature has already been (re-)developed and merged into the main app, so we know it's coming in 0.18.1, and that was the main dealbreaker for most instance admins.
I hope it has a short release cycle because 0.17.4 has some glaring bugs and I'm really hoping for some improvement. For example I'm getting missing posts which is kind of driving me batty. Then the sort orders don't work right which is also causing some angst. Though not to complain, I'm enjoying my time here and I'm willing to put up with some growing pains. It's just these issues are starting to get tiresome.
Missing posts seems to be something of a delay in federation, so I really hope that will change. Sort order works mostly for me, only "active" seems completely defunct, so I just don't use that at all.
From my instance I started to see all the posts and comments coming directly from lemmy.ml immediately after they updated to 0.18. I am still unable to federate correctly with lemmy.world and other instances because they didn't update yet so I'm confident that this problem will be largely fixed after we all update to the new version