Engineer, surfer, and long time Star Citizen backer.

  • 2 Posts
  • 14 Comments
Joined 17 days ago
cake
Cake day: October 31st, 2026

help-circle
  • QuadratureSurfer@piefed.ziptoAsk Lemmy@lemmy.world•Delete
    link
    fedilink
    English
    arrow-up
    4
    ·
    1 day ago

    TL/DR: Archival instances might, but most (even Lemvotes) won’t hold onto that.

    Anything you post or do is shared out to a much wider audience. You might be using a Lemmy account, but interactions are shared with Twitter-like instances (Mastodon) as much as they are shared with other Reddit-like (Threadiverse) instances such as PieFed or Mbin, as well as other kinds of instances that interact with the Fediverse.

    Even Meta has a presence here on the Fediverse with Threads. You just don’t see a lot of Threads users toggling their account over to interact with the rest of the Fediverse, but there are a few who do. Granted, upvotes and downvotes aren’t displayed for most Twitter-like instances. So, I would say it’s unlikely that they are recording that.

    If you accidentally downvote a post or a comment that information will be sent out to every other instance which is connected (federated) with yours. As I mentioned before, you could set up an account to limit how votes are shared which would mitigate that. Some instances might even have a feature to delay voting for a very short time to allow for cancellations.

    So, would it stay in your public voting history? For any other instances that are set up for archiving and registering the history of the Fediverse, yes. But in almost every other case, no. Most fediverse instances will honor when you have cancelled an upvote or a downvote.



  • QuadratureSurfer@piefed.ziptoAsk Lemmy@lemmy.world•Delete
    link
    fedilink
    English
    arrow-up
    10
    ·
    1 day ago

    Since everyone else has already answered your main question, it’s also worth pointing out that all of your upvotes and downvotes are mostly public due to the nature of the Fediverse and needing to publish that info.

    There are ways to mitigate that, such as using PieFed and setting your votes to only count locally, or to only federate to “trusted” instances. Otherwise, another way to handle it is to use a “voting only” account and don’t make any comments with it.






  • Some things just don’t federate well across services. Here on the threadiverse we can all see each other’s upvotes and downvotes. However Lemmy users can’t see the likes/boosts of Mastodon users. Mbin/Kbin users can see boosts though.

    On the other side, Mastodon users can’t see the upvotes/downvotes of Threadiverse users, or even their own upvotes/downvotes that they may have received from the Threadiverse.

    So, while the fediverse as a whole may have 20 million users, sometimes the more common way that people engage is by simply liking/boosting/voting something. That information isn’t always supported by different services and it may look a little emptier than it actually is.

    Engagement on the Threadiverse may be a bit easier, because all you need to do is find a popular community and post in it.

    Engagement on the other side of the fence is usually found by following a popular hashtag, or mentioning users with a large following. They can still create posts in Threadiverse communities as well, but that’s not the typical route that they’re used to.






  • What exactly are your concerns with voting?

    On any fediverse software, ActivityPub is going to be sharing your vote records. PieFed gives you a little more control and lets you lock down those votes to only be shared with your own instance, with “trusted” instances, or with everyone.

    With Lemmy you can create an instance that forces it so that downvotes are not an option.

    With PieFed you have a little more control. You can create a community that accepts downvotes from:

    • Everyone
    • Nobody
    • Community Members
    • Local Instance only
    • Trusted Instances

    End users across both Lemmy and PieFed ultimately decide how they view content in their feed and whether votes factor in at all.

    Even if you disable downvotes on your particular instance/software, that doesn’t stop other instances from tracking upvotes/downvotes in their own way, locally. At most the main instance hosting the community won’t be federating out the downvote information from one instance to another.

    The way you describe topics in your anti-echo-chamber forum sounds like it fits better with the way PieFed handles Topics and flair on posts, but it’s different enough that I can sort of see what you’re getting at.

    As far as controlling how spaces/topics are organized, and looking at your chart, which instance would ultimately be in charge of that? Would it be the largest instance and smaller instances are expected to follow? What if a smaller instance organized the topics in its own way?

    The way PieFed handles this is that each instance is in charge of their own Topics. Users can only view the topics that their instance provides, although they can be organized in a similar way to one another.