I only just learned today that, when someone from one instance gets banned from another instance, that person not only is no longer able to interact with the second instance, but people from the second instance actually can’t see anything the person said from the moment they got banned even though they’re still there. I’m disappointed to learn all my friends who got banned from my instance are still saying stuff and nobody told me, making it more akin to an instance forcing everyone to block them (because individuals blocking each other the same way work like this). And this is coming from the person who has fantasized about universalization of federation.

What’s something about the fediverse that was most recently unobscured but that you know now?

  • wizardbeard@lemmy.dbzer0.com
    link
    fedilink
    English
    arrow-up
    11
    ·
    7 days ago

    Instance admins can see your upvotes/downvotes, as in who specifically upvoted/downvoted something. As far as I’m aware, some front ends just make that information public.

    • ITGuyLevi@programming.dev
      link
      fedilink
      arrow-up
      2
      ·
      6 days ago

      Much like good old MySQL, it’s named for its creator and the last name My is pronounced ‘me’. At least that’s what I remember hearing or reading somewhere… I’m sadly too uncultured to know for sure (never made it that far around the globe).

  • conciselyverbose@sh.itjust.works
    link
    fedilink
    arrow-up
    42
    ·
    7 days ago

    That’s the entire point of bans.

    You don’t want to have to manually block all the spammers and shit posters a decent instance is taking care of for you.

    • moonlight@fedia.io
      link
      fedilink
      arrow-up
      8
      ·
      7 days ago

      I think it would be better if bans only applied to posting on an instance, and each instance/community would self moderate. If I go to a post, I want to see the whole discussion, and not have certain people hidden from me by my home instance. Let the instance hosting the community filter out spam.

      • conciselyverbose@sh.itjust.works
        link
        fedilink
        arrow-up
        16
        ·
        edit-2
        7 days ago

        Run your own instance or join a permissive one if you don’t want your instance to moderate trash away.

        What you’re describing is a massive downgrade, and also massively adds to the legal exposure of hosting an instance, because you’re serving everything any user of your instance sees. Being able to block bad actors isn’t really an optional feature. You’re effectively asking for your instance to be forced to serve you abusive content.

        • moonlight@fedia.io
          link
          fedilink
          arrow-up
          5
          ·
          7 days ago

          I understand the liability issue, I guess this is just an inherent tradeoff with how the fediverse works.

          I at least think there could be a two stage ban, ‘no posting here’ and ‘block everything’.

          Also, defederation could still be used for instances that fail to moderate, although I do agree that fully blocking a user is much preferable to the nuclear option.

          • conciselyverbose@sh.itjust.works
            link
            fedilink
            arrow-up
            4
            ·
            7 days ago

            It would be a waste of time when no one would use the half ban. They’re banning users because they don’t want to serve whatever they’re posting.

      • originalucifer@moist.catsweat.com
        link
        fedilink
        arrow-up
        4
        ·
        7 days ago

        you seem to be annoyed that a remote community can police itself.

        your local instance is using some other servers content, of course its going to adhere to the moderation of that remote instance (federated moderation).

        if you dont like the moderation of a remote community its your duty to make a new one somewhere else. this happens regularly when lemmy.world or .ml mods go overboard into fedora territory. if users agree, they will follow

        • moonlight@fedia.io
          link
          fedilink
          arrow-up
          2
          ·
          7 days ago

          That’s not what I’m saying at all. I’m saying it would be best if content on remote instances wasn’t censored when viewed on a local instance, even if that user was banned locally.

          I think this problem is hard to get around though with how all content has to be hosted locally.

              • originalucifer@moist.catsweat.com
                link
                fedilink
                arrow-up
                6
                ·
                7 days ago

                youre upset that a remote instance can police its own content. but youre confused why your local copy of their data gets modded… you just dont like the fact that a community can police itself and that that moderation flows to remote copies of their community.

                if you really want to circumvent this, you would spin up your own instance and prevent federated moderation. but you have to admit that youre ignoring the wishes of that remote community to moderate their content.

                e. now that i think about it, if you get banned at the instance level, well, youre SOL. because they are rejecting you/your addition to their content.

                • moonlight@fedia.io
                  link
                  fedilink
                  arrow-up
                  1
                  ·
                  7 days ago

                  Please re read the original post and my comments. That’s not what I am saying.

                  I’m saying that ideally moderation SHOULD be handled by the remote instance that hosts the community, and that the local instance should faithfully reflect it without censoring it.

  • boatswain@infosec.pub
    link
    fedilink
    arrow-up
    35
    ·
    7 days ago

    If you’re having problems with a lot of people you like being blocked by your server, it’s probably a good sign that you should change your server. That’s kind of the point of being able to do that.

  • ℕ𝕖𝕞𝕠@slrpnk.net
    link
    fedilink
    arrow-up
    27
    ·
    7 days ago

    You can use emojis in your display name.

    If you run your own instance, you can do a lot more, like set your account creation date to a century ago, or even run a script so it’s always your cake day.

  • kamenLady.@lemmy.world
    link
    fedilink
    arrow-up
    25
    ·
    7 days ago

    When you delete your comment, it’s not actually deleted. When you try replying to a deleted comment, it will show the original comment above the textarea for your reply.

    At least my client ( sync ) does that.

    I always overwrite my comment with “deleted” or similar, before deleting.

    • Appoxo@lemmy.dbzer0.com
      link
      fedilink
      arrow-up
      6
      ·
      7 days ago

      I think that got fixed.
      Probably something to do with federation. I’d look at it maybe 24h later.
      But for anyone else knowing this open secret and seeing the content…Damage was done.

  • Rimu@piefed.social
    link
    fedilink
    English
    arrow-up
    25
    ·
    7 days ago

    Anytime someone says “it has to be that way because that’s how federation works” they’re wrong. It can be however we want it to be, it’s just a choice.

  • slackassassin@sh.itjust.works
    link
    fedilink
    arrow-up
    21
    ·
    7 days ago

    “All” is not necessarily all. Others on your instance, or you, must subscribe to other instance’s magazines for them to show up.

  • SavvyWolf@pawb.social
    link
    fedilink
    English
    arrow-up
    16
    ·
    7 days ago

    If there’s a post or something on another instance but not your one, you can enter the full URL into the search bar and it will fetch it and make it available on your instance (unless defeds get in the way).

    Works on both Lemmy and Mastodon.

    • burgersc12@mander.xyz
      link
      fedilink
      arrow-up
      3
      ·
      edit-2
      7 days ago

      If you want to go straight to a community, hit the search icon and type it in the format [email protected], this has helped a lot, but was only mentioned in a changelog like a year ago.