I made a post here: https://lemmy.world/post/16949903

Hi. I raised an Issue on the crawler’s repo a couple of weeks ago. Still waiting for a response though …

Yeah, maybe. I’ll leave it with you …

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.

I wouldn’t do this personally, but if I did, I think I’d at least pipe the results to head -n 1 to only act on the first result.

‘subscribe to anything’ is handy, too. I’m subscribed to this post, for instance, so get notifications of new top-level comments.

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 …

For lemmyverse, the issue for it is here: https://github.com/tgxn/lemmy-explorer/issues/184

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.

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

Please use your mander account to inform OP that their instance is wildly behind .world - see here

The delay and eventual deletion of comments and votes will have an obvious effect on mander’s “hot” and “active” algos.

If you look at this post on mander, it’s not got any of the comments, so there’s no point anyone using a .world community to answer OP’s question.

Hello. This data is sourced from lemmyverse.net, which uses its own crawler, distinct from the lemmy-stats one. The underlying issue is likely the same, so I’ve filed a bug here (past experience suggests that the dev won’t be that quick responding to it though)

The instance I’m on is defederated from links.hackliberty.org. I’m not certain why, but I looked at it to find it’s a place for conspiracy theories, including ‘9/11 Truth’ stuff, so it’s probably that.
There looks to be a bit of indecision about the right instance for a new ‘privacy’ community, so I’m just mentioning this in regard to that.

That’s kinda funny, in a way - unsophisticated prevention for an unsophisticated attack.

Everyone trying to use the Internet normally suffers due to this kind of stuff.

Nothing yet for today (Sunday), because the crawler at lemmyverse has failed. More info is here: https://github.com/tgxn/lemmy-explorer/actions/runs/9434433542/job/25986550190 - it’s bailed because there are 6011 communities missing from that run compared to the previous one. I’ve seen that number before, which suggests it’s a single instance with that many communities which is failing to give a response.

EDIT: the midday run worked though.

lemm.ee have upp’d to 0.19.4, and presumably turned on the Image Proxying thing - this is what I get for: https://lemm.ee/post/34040618

{"error":"unknown","message":"Request error: error sending request for url ([http://127.0.0.1:8080/image/original?proxy=https://ichef.bbci.co.uk/news/1024/branded_news/be3c/live/2a45fdb0-20ee-11ef-a3ab-e73c00cc3104.jpg)](http://127.0.0.1:8080/image/original?proxy=https://ichef.bbci.co.uk/news/1024/branded_news/be3c/live/2a45fdb0-20ee-11ef-a3ab-e73c00cc3104.jpg)): operation timed out"}

I’ve had that problem too (messing around with test instances) - for anyone else wondering why: it’s because the RSA keypair for me@mydomain has changed, and remote instances fail to validate message headers signed with the new private key, because they’re still using their copy of an old public key.

That’s great to hear. There’s zero API at the moment though, let alone a stable one. PieFed is a monolith, without the backend / front-end split that necessitates an API.

It easy to add one, pending the addition of some missing features and a code reorganization that needs to happen anyway. At that point, hopefully some interested app developers will also be involved, to shape the API into something they may wish that other app’s APIs were like.

It seems to be quite a lot for the server it’s hosted on though (which is not the snappiest). There are, of course, still areas in the world where - for one reason or another - people still are effectively on dial-up speed-wise.

Buster should turn their attention to the size of the images uploaded to servers like this: 1.1M is arguably overkill for this one.

Yep, if you visit London as a Northerner it’s very clear where the money is going. In retrospect, the Northern legs of HS2 were never going to happen - the money saved being diverted to fix London’s potholes was the icing on the cake.