• Admiral Patrick@dubvee.org
    link
    fedilink
    English
    arrow-up
    2
    ·
    3 hours ago

    I read the PR. It seems more like a hacky bandaid rather than addressing the actual issue. But I digress.

    It’s also possible I misunderstood where/how the limit was being applied. My understanding was that it was limiting the response to 50 per depth (50 seems to be the arbitrary limit for most of the API’s list endpoints). What I really don’t want to do is have to paginate the request for the top level comments.

    e.g. if a post has 100 comments, and say, 60 of them are top-level, I much prefer to be able to get all 60 in one go. Depending on the total number of comments provided in the getPost call, I dynamically set max_depth higher (3-5) or lower (as low as 1) and fill in the deeper comments manually with a “show more” button. The exception is if linking directly to a comment where it uses the path to calculate the exact depth to fetch.

    finding one with a chain of over 50 in a row is even more rare. Such a thread would be clunky to display in the main comment tree anyways

    I’m working around that without pagination, but it’s a low priority fix since Patrick’s Law come into play. It’s like Godwin’s Law except it says that once a comment thread gets deeper than 9, it’s a slapfight that’s best avoided.

    • Die4Ever@programming.dev
      link
      fedilink
      English
      arrow-up
      2
      ·
      3 hours ago

      yea it would definitely suck if it only loaded 50 comments at a time, or 50 replies under a comment, but I think it’s fine as-is

      once a comment thread gets deeper than 9, it’s a slapfight that’s best avoided.

      lol for sure, 9 is already a lot