I am concerned that Mastodon’s unary-vote system (favorites), and Lemmy’s binary-vote system (upvotes with downvotes) are mutually exclusive.

In a unary-vote system, a post’s vote count generally has little use beyond expressing the post’s absolute popularity/engagement, whereas, in a binary vote system, a post’s vote count can be used to gauge opinions, such as its level of quality, trust, or agreement. This difference in usage makes me concerned that the votes federated from Mastodon will water down the votes originating from Lemmy.

Currently, I can think of two possible solutions to this:

  1. Lemmy de-federates any votes originating from Mastodon (might be tricky as it would rely on all instances following suit)
  2. Add an option for the user to toggle within their settings allowing them to toggle off non-binary votes.
  • cum@lemmy.cafe
    link
    fedilink
    English
    arrow-up
    1
    ·
    11 months ago

    Not really. Also Lemmy’s and Mastodon work pretty differently. They may want to like something, but not up vote it. They may not even care about the voting system and not want to participate. Also on a technical level, it’d be messy to make the two compatible.

    • Kalcifer@sh.itjust.worksOP
      link
      fedilink
      English
      arrow-up
      2
      ·
      edit-2
      11 months ago

      They may want to like something, but not up vote it.

      Isn’t that the point of the “Add activity” (Section 6.6 of the ActivityPub Documentation)? I think it is equivalent to a “Favorite” in Lemmy.

      They may not even care about the voting system and not want to participate.

      This point feels moot, to me.

      Also on a technical level, it’d be messy to make the two compatible.

      They already are compatible, though, aren’t they? That’s the whole point of the ActivityPub protocol. Mastodon, of course, won’t accept downvotes since, afaik, that is an extension made to the protocol by Lemmy, but likes/favorites/upvotes should federate normally.

      • cum@lemmy.cafe
        link
        fedilink
        English
        arrow-up
        2
        ·
        11 months ago

        Well ActivityPub isn’t 1:1 interoperable all the time. Like you’re not going to see the upvotes/downvotes of a Lemmy post when viewing from Mastodon. Which this makes sense, since how would Mastodon even know how to handle that data, and it opens up all sorts of compatibility problems. What does interoperate is the post and comment content which is the important part. Also that you’re able to post/comment to other user posted content even if you can’t see all of that ActivityPub’s application data.

        • Kalcifer@sh.itjust.worksOP
          link
          fedilink
          English
          arrow-up
          5
          ·
          edit-2
          11 months ago

          Well ActivityPub isn’t 1:1 interoperable all the time

          It will be interoperable up to the base spec (assuming, of course, that both services adhere to the base spec).

          Like you’re not going to see the upvotes/downvotes of a Lemmy post when viewing from Mastodon.

          If both Mastodon, and Lemmy adhere to the spec, then they can interoperate. If Lemmy’s upvotes are federated as ActivityPub like activities, and Mastodon intereperets like activities as favorites, then there should be no issue. Downvotes will certainly not federate as Mastodon doesn’t use them, and they don’t exist in the base spec.

          What does interoperate is the post and comment content which is the important part

          Likes federate as well. See Section 6.8 of the ActivityPub spec.