Just a post on !fediverse explaining the issue in a few lines. A link to the existing ticket. Ending with an open call for people who might be interested in forking the existing project.
Fixed now - a community called "wave" music caused a JSON deserialization error (because JSON uses " for its own purposes).
It's been 2 weeks since I raised the Issue for 0.19.4 / 5 instances on lemmyverse - given that there's been no response, we might have to give up with these lists anyway.
More and more stuff won't feature as instances continue to upgrade to 0.19.4, as lemmyverse.net doesn't yet support it (there was something like 582 instances listed yesterday on there, it's 572 now).
We'll have to wait until that dev responds, or maybe until Lemmy devs change their mind about not providing a nodeinfo 2.0 response for 0.19.4 instances.
EDIT: ah, me and Blaze were commenting at the same time, it seems.
The last time I raised an Issue, the dev did respond, but it was a full week later. Maybe just considered low priority vs. other stuff in his life, rather than unmaintained. Hopefully, anyway. We'll see ...
No, it's twiddling its thumbs waiting for the crawler at lemmyverse.net to start working again.
I submitted an Issue to the GitHub last time it failed, and the developer responded with some info. I didn't really understand it, tbh, but it looks to be the same problem, so hopefully it'll right itself again.
!nowhereelsetoshare has a broken outbox (no posts if you're the first person from your instance to visit). The Issue was recently fixed, so hopefully the fix will be included in 0.19.4 (and all instances on .3 upgrade to that when it comes out).
Just bad luck I think. The convo on the bug report suggests the problem stems from a user making a post, and then the user being deleted (voluntarily or involuntarily).
Trending Communities
Hot
This magazine is not receiving updates (last activity 0 day(s) ago).