Sometimes an API request returns {"comments":[]} and {"posts":[]} respectively, for a post and community, where posts and comments show up on the web frontend. Is that happening to any of you too? How do I handle it?
Edit: did some more testing, it’s most definitely a federation issue. If I query the instance that the post was made on for the comments, everything works fine. If I query my home instance, the result comes back empty.
Edit 2: As always, just after publicly showcasing my lack of programming abilities, I discover it’s been me the entire time. Make sure to await promises and to fetch posts from the correct instance, guys.
Pretty sure it didn’t work, but I can’t replicate it right now. Will need to see if it happens again
Edit: did some more testing, it’s most definitely a federation issue. If I query the instance that the post was made on for the comments, everything works fine.
Oh, I ran into that. There is a post on !lemmycode@lemmy.ml even.
You need to set the type_=All on fetching comments for a community that isn’t originated on your local server. You can just use that parameter when fetching comments from any post.
Lol, I was gonna say I’ve never experienced this before
I’ve had lemmy_helper crawling posts looking for missing comments for the same post on different servers, thousands of posts, and I haven’t seen this yet. Lemmy.ml is the most unstable server - it ever returns an HTTP status problem or some error message.
To be clear, I checked twice that my limit and page parameters are correct. I request page 0 with limit 10 and get nothing, while the post counts clearly say there are multiple comments and while the web interface shows them normally. Very weird
I request page 0 with limit 10 and get nothing
Lemmy API starts at page 1, page 0 is invalid?
curl "https://lemmy.ca/api/v3/post/list?limit=2&page=1"
curl “https://lemmy.ca/api/v3/comment/list?post_id=648889&type_=All&limit=2&page=1”page=0 returns {“error”:“couldnt_get_posts”} (or comments)
I meant page 1, sorry
