aka freamon

Codeberg: https://codeberg.org/freamon?tab=activity

Anything from https://lemmon.website is me too.

  • 7 Posts
  • 172 Comments
Joined 6 months ago
cake
Cake day: March 27th, 2024

help-circle




  • There’s a user here, who was ‘101’ at reddthat, then piefed, then feddit.org, and was 911 at lemmynsfw, and is currently 911 at programming.dev, who posts a bunch of articles over a week or so, then deletes their account and moves on to another instance. They’re up to something, surely. (the only real downside to this behaviour - that I can think of - is that new instances won’t be able to get their posts, because Lemmy doesn’t return posts for deleted users)











  • Oh. I subscribed to this post because I hoped someone would be able to give an answer too.

    It’s been a day, so before I forget and on the basis that some answer is better than none at all, I’ll have a crack:

    400 Bad Request isn’t much to worry about, it doesn’t mean anything is malfunctioning and it can happen for a gazillion reasons. One is you’ve joined a new community and someone Likes a comment you don’t have (particularly if it’s nested in other comments you also don’t have). Another is if someone Likes a post or comment by a user on an instance that you’ve defederated from (your instance is defed’d from lemmygrad and hexbear whereas lemmy.ml isn’t)

    As for 499, that seems to be a client issue, and that client mostly seems to be beehaw, who are stuck on an old Lemmy version and being increasingly wonky (in the other direction, they often reply in HTML rather than JSON and randomly decide that their communities’ inboxes don’t exist, so I wouldn’t worry about stuff from them either)







  • Seems like ‘posts’ works okay, but it’s ‘comments’ that don’t (and overview is a mix of both).

    API call to see posts:
    curl --request GET --url 'https://lemmy.world/api/v3/user?username=beebarfbadger&sort=TopDay&page=1&limit=1' --header 'accept: application/json' | jq .posts[].post.published = 2024-09-26T15:35:33.998368Z (today’s top post is today)

    API call to see comments:
    curl --request GET --url 'https://lemmy.world/api/v3/user?username=beebarfbadger&sort=TopHour&page=1&limit=1' --header 'accept: application/json' | jq .comments[].comment.published = 2024-03-03T05:09:45.255807Z (this hour’s top comment was in March)

    They probably know about it, but if not it’s probably a good idea to report the bug here: https://github.com/LemmyNet/lemmy/issues