I’ve seen around 3 occasions of that this week, altho I have never seen anything like it before.

if I remember correctly they were:

  • smack talking a mod (FlyingSquid) for saying not to report the same comment twice, when they were different comments, and the report was spam
  • someone comparing .world with .ml in politics (as in there was a comment saying "this post will be overrun with .ml people, and then a comment going “but you are from .world”) (Maybe Im part of the problem? I have been called out for being a fascist because I questioned the “puching nazis” theme)
  • one more which I can’t remember.

Anyways, what is all that about? Are people really starting to hate on 50% of the lemmy population because of their instance?

  • @OpenStarsEnglish
    13•21 hours ago

    People are doing that here though - e.g. the user Blaze made accounts on basically every instance, and subscribed to every community. This gets around the limitation where at least one user of an instance must subscribe to a community before it will even so much as show up for others to also subscribe. Really the developers should have made better automation so that this was not necessary, but… anyway it works, for now:-).

    • Dark ArcEnglish
      9•20 hours ago

      (If true) that’s actually really terrible for federation performance, particularly because lemmy doesn’t do batch synchronization. So basically every comment, post, like, and community is being sent to all Lemmy servers as individual sequential requests. That’s a lot to handle.

      • @OpenStarsEnglish
        11•20 hours ago

        Supposedly that will change with v0.19.6 (A recent discussion about that here: https://feddit.org/post/3524876), but yeah it’s causing smaller instances such as Aussie.Zone to have delays of over 7 days.

        I also expressed disbelief that this info would not be bundled somehow - at least put together a package for everything that happened across the entire instance in one second, or one minute could be far better, for servers that can’t handle the per-second traffic?

      • @OpenStarsEnglish
        2•10 hours ago

        That’s nice! ☺️

    • Lvxferre
      1•19 hours ago

      I feel like ActivityPub implemented federation in a really weird way, and that’s what causes problems like @linearchaos@lemmy.world is reporting, or the issue that Blaze is addressing through multi-accounting. Perhaps we shouldn’t be sharing content across instances but only credentials.

      For example. If you’re registered to instance A, and B federates with A, then B would let you post from your A account as if you were registered to B. Then let the retrieval of the content of different instances up to the front-end, instead of mirroring it.

      • @OpenStarsEnglish
        4•10 hours ago

        No, the whole point for the federation is to share the content. For one, it allows redundancy so that if a rogue mod or admin decided to delete a bunch of stuff, then every other instance still retains copies of what came from it.

        But that said, having to keep everything up to the second, in batches of a single action, is extremely limiting. If I downvote someone with an accidental button press, then undownvote them, then upvote - that could have been just one net interaction to send, but instead it is three.

        • Lvxferre
          2•1 hour ago

          Redundancy is better handled through specialised mirrors, similar in spirit to reveddit. That would be even more transparent than the current system - as the mirrors could translate actions like content removal into content highlighting, so it would stick out like a sore thumb*. This would also throw the burden associated with redundancy (transmission, storage, removal of clearly illegal content) into a few machines, instead of the whole network.

          I’m aware that it’s a weaker form of federation than the current one but, as long as the front-end handles simultaneous multi-account and merges the feeds of the instances that you’re registered to, it’s already addressing the main needs:

          • users can see content from multiple places without registering individually to each
          • users don’t need to see what they don’t want to
          • content is still spread out, so no instance controls the whole
          • admins still have control over who accesses their own instance (through defederation + banning).

          *currently you can only find a piece of removed content if you know that it exists.