this post was submitted on 13 Aug 2023
10 points (85.7% liked)
Lemmy.world Support
3232 readers
3 users here now
Lemmy.world Support
Welcome to the official Lemmy.world Support community! Post your issues or questions about Lemmy.world here.
This community is for issues related to the Lemmy World instance only. For Lemmy software requests or bug reports, please go to the Lemmy github page.
This community is subject to the rules defined here for lemmy.world.
To open a support ticket
You can also DM https://lemmy.world/u/lwreport or email [email protected] (PGP Supported) if you need to reach our directly to the admin team.
Follow us for server news ๐
Outages ๐ฅ
https://status.lemmy.world/
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
This being the default answer for all issues kinda prevents any discussion of any issue that might be unrelated.
The API problem is that you do (ignore the ampersand issue for a moment):
curl 'https://lemmy.world/api/v3/community/list?type_=Local&sort=Old&limit=1&page=250010&show_nsfw=true' | jq .and it will return a response for a page of Communities it can't possibly have. It's a never-ending list that can't be indexed.
The thing, it returns without issue - there's no connectivity problems that DDOS attacks would cause.
Are any other instances affected?
No. Just .world. Every other instance returns an empty array when the end of the list of Communities is reached. We'd know if they didn't, because they'd break web crawlers too.
How peculiar. Could they be running a custom Lemmy build?
I think there was a change to the API in a recent release of Lemmy, that .world hasn't accounted for correctly. I'm guessing because this post has the two most common responses to tech questions about .world: silence from anyone who could actually answer, and the usual "it'll be them DDOS attacks".
That's odd. You'd think they'd want to address it. It's bad for visibility. @[email protected]