• @uberstar
    link
    33 years ago

    Not a lot of people are fans of “necroposting” (if memory serves right, it means to post on a thread after being inactive for a long while). Worst yet, it’s probably less likely you’ll gain any responses from the same people that have posted in a thread long ago or from anyone really. I think if the time limit is not too long and not too short (so as to cover both bases) like say… 3 to 7 months till the post becomes archived, then it’d be acceptable. However, it’d be cool if instance maintainers get to control that feature since I’m sure they won’t be all agreeing on the same limit.

    Is there a time limit the lemmy devs/admins have agreed on so far?

    • @Liwott
      link
      43 years ago

      Worst yet, it’s probably less likely you’ll gain any responses from the same people that have posted in a thread long ago or from anyone really.

      The person commenting an old thread should be aware of that, so I don’t see what forbidding them to comment helps with.

      It also depends how a newly commented post is highlighted in usrrs’ feed.

      • @uberstar
        link
        23 years ago

        The person commenting an old thread should be aware of that, so I don’t see what forbidding them to comment helps with.

        See, the thing is, not everyone keeps that in mind before posting in an old thread. I’ve also made the assumption that the user expects a response from the og posters and/or OP, which might not necessarily be true.

        • @Liwott
          link
          23 years ago

          I do understand that, but forbidding everyone to answer the thread seems like a radical solution for this mild problem. Maybe a more appropriate solution would be highlighting the age of the post and of the last comment.

    • @nutomicOPA
      link
      33 years ago

      So far there is nothing like this implemented, thats why i’m asking. And yes the (default) time to close threads automatically is also an important question.