• brucethemoose@lemmy.world
    link
    fedilink
    English
    arrow-up
    2
    ·
    1 day ago

    Programming language isn’t a problem as much as the mechanics of the implementation.

    I mean, how does it work on Twitter? Do they have oldschool language models parse upvoted comments and automatically generate it? Basically the options are:

    • Involve some kind of ML model for partial automation, which is not going to go over well with Lemmy users.

    • Leave the UAC completely to mods, which is going to both overburden them and make power-tripping issues far worse

    • msprout@lemmy.world
      link
      fedilink
      English
      arrow-up
      2
      ·
      1 day ago

      On old Twitter, community notes was simply a function of raising a flag for tweets that got ratio’d. This would open those tweets up for Community Notes users to submit a fact check. Then, the fact check with the highest upvotes gets displayed as the default one.

      Now? Not sure. Elon is a sneaky fucker. But I do think it could be implemented as a simple comment queue that admins and moderators could set user roles to help with.

      • brucethemoose@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        edit-2
        1 day ago

        Getting ratioed isn’t an reliable indicator though (see this post).

        I guess there could be a “misleading” button that triggers a Community Notes section, but complicating the UI like that could push away many participants…

        Maybe there should be a button to “mark” a comment as a correction during the posts, and if it gets enough upvotes it becomes visible under the title? That could work. Some useful comments might not get properly marked, but I think many would.

        One issue is Lemmy comments are typically too long to fit under a title, so the “correction” comment would need its own structure: a short correction that fits under a post title, and context that lives in the comment section.