Edit: obligatory explanation (thanks mods for squaring me away)…

What you see via the UI isn’t “all that exists”. Unlike Reddit, where everything is a black box, there are a lot more eyeballs who can see “under the hood”. Any instance admin, proper or rogue, gets a ton of information that users won’t normally see. The attached example demonstrates that while users will only see upvote/downvote tallies, admins can see who actually performed those actions.

Edit: To clarify, not just YOUR instance admin gets this info. This is ANY instance admin across the Fediverse.

  • s4if@lemmy.my.id
    link
    fedilink
    English
    arrow-up
    65
    ·
    1 year ago

    Nothing private in fediverse except when you are selfhosting yourself.

    • vinnymac@lemmy.world
      link
      fedilink
      English
      arrow-up
      21
      arrow-down
      5
      ·
      1 year ago

      If post views are public that’s a fairly poor implementation on the developers part. I’m sure it will change over time.

      E.g. someone using your account to view illegal content in a community you are not a member of, and you being held accountable.

      • CmdrShepard@lemmy.one
        link
        fedilink
        English
        arrow-up
        2
        ·
        1 year ago

        E.g. someone using your account to view illegal content in a community you are not a member of, and you being held accountable

        Can you explain what you mean here? How would someone else be using your account without your knowledge?

      • s4if@lemmy.my.id
        link
        fedilink
        English
        arrow-up
        22
        ·
        1 year ago

        I think the in the current implementation, your post views is not public. But any data you have is still accessible to your instance admin.

        • vinnymac@lemmy.world
          link
          fedilink
          English
          arrow-up
          5
          ·
          1 year ago

          Not too bad then, at that point it just depends how they handle log storage on the instance you are visiting.

          Thanks for clarifying.

          • chris@l.roofo.cc
            link
            fedilink
            English
            arrow-up
            14
            ·
            1 year ago

            Nope. Everything you do is sent to all other instances. If you upvote your instance sends that upvote to the instance where the community lives and that instance broadcasts your vote to alle instances that subscribe to that community. Every instance operator can see the upvotes.

            • s4if@lemmy.my.id
              link
              fedilink
              English
              arrow-up
              1
              ·
              1 year ago

              At least your password hash not accessible by anyone but you… and your dm is also only accessible by your recipient and his/her admin… 😅

              • ninjan@lemmy.mildgrim.com
                link
                fedilink
                English
                arrow-up
                8
                ·
                1 year ago

                While you’re 100% correct Lemmy would feel pretty slow running on your normal computer unless you keep it online and powered on 24/7. Since Lemmy fetches new content continuously and being offline causes a big backlog which will take time to process. It also presents a few extra challenges since you need a domain and cert and a home static IP isn’t super common which means you need dynamic dns and have to set that up. Any restart where you get a new IP will be even slower since you need your updated A host record to propagate before your Lemmy instance can fetch the backlog. Those issues aside though you could absolutely just run it like any dockerized application on your normal computer.

                • HTTP_404_NotFound@lemmyonline.com
                  link
                  fedilink
                  English
                  arrow-up
                  5
                  ·
                  1 year ago

                  If your lemmy goes offline- there is a good chance it WONT catch-up.

                  Servers only retry sending content so many times. ActivityPub PUSHES, rather then pulls mostly.

      • Wander@yiffit.net
        link
        fedilink
        English
        arrow-up
        7
        arrow-down
        2
        ·
        1 year ago

        It’s not possible to make votes private is your care about no manipulation happening. Otherwise any self hosted instance could just communicate any made up amount of votes.

        • WIPocket@lemmy.world
          link
          fedilink
          English
          arrow-up
          2
          ·
          1 year ago

          Cant they? Sure, they would have to make up new users instead of simply saying a number, but what is actually preventing that?

          • lightrush@lemmy.ca
            link
            fedilink
            English
            arrow-up
            2
            ·
            edit-2
            1 year ago

            Without a common authentication scheme that every instance checks against… Probably anyone can do it. I don’t know how you’d even approach this. Signed messages via GPG with a common pubkey host? Some blockchain scheme for authentication that obviates the need for a central host? I’ve no idea.

          • Wander@yiffit.net
            link
            fedilink
            English
            arrow-up
            3
            ·
            1 year ago

            We can monitor actual active users that an instance has. Anything artificial in volumes enough to have an impact would be noticeable in some way to other instances.

            • lightrush@lemmy.ca
              link
              fedilink
              English
              arrow-up
              3
              ·
              1 year ago

              Can’t someone talk ActivityPub directly and do this? If the instance is responsible to authenticate the users, the instance can just directly talk ActivityPub to the rest of the network and tell it users and votes on the fly, without even Lemmy running there.