• scytale@piefed.zip
    link
    fedilink
    English
    arrow-up
    40
    arrow-down
    2
    ·
    2 days ago

    Ninja edits. A 30-second grace period to edit a comment before it’s marked as edited. It’s for fixing typos.

    • tal@lemmy.today
      link
      fedilink
      English
      arrow-up
      6
      ·
      edit-2
      2 days ago

      I edit my comments like mad, but I think that showing the last modification time, which is presently done, mostly solves the problem in a better way than just a binary “edited or not” flag with a delay.

      I believe that the reason you need to show that a comment has been modified is to deal with two problems:

      1. Putting a popular comment in place, letting it accrue a lot of upvotes, and later editing it to contain wildly different content. This gives the new content unwarranted credibility.

      2. Writing a comment, waiting until someone responds, and then editing the parent comment so that their content is placed in a different light.

      Having a comment last-modified time does a better job of solving #2 than a binary “edited or not” indicator (since one can see whose comment was edited most recently).

      One can’t always infer enough information to address #1 from just a last-modified time, but generally, one that’s way out-of-whack from surrounding comments in modification time is a red flag.

      I think all of the clients I’ve seen just show the last-modified time, and I don’t know if the API exposes both original and last-modified time.

      searches

      Apparently yes.

      https://www.socialfetch.dev/docs/api/v1/lemmy/post/comments/get

      You have the “publishedAt” and “updatedAt” times.

      So clients have all the information they need to know how long a comment stood between initial publishing and last modification. You could maybe just have clients show the delta between publishedAt and updatedAt. That’s a superset of what a boolean “edited after grace period” indicator shows.