The fediverse has been good to me so far, I am more than happy to support these projects, and to support the future of social networking.

      • Lost_My_Mind@lemmy.world
        link
        fedilink
        English
        arrow-up
        2
        arrow-down
        1
        ·
        1 month ago

        I wouldn’t exactly call what I was complaining about my first week reposts, but I definately had system shock while I was still figuring out how things worked.

        I’d see 3 different communities, all about the same topic, and I’d subscribe to them all.

        Well, if you have 3 communities all focused on the same subject, when there’s breaking news about that subject, they’re all going to post that same news story.

        So in my feed I’d see the same url posted from 3 different instances. It’s not exactly a repost, but it feels the same.

        I still don’t know what the solution for that is. Feels less like a me problem, and more like a systems concept problem. Instead of having 3 communities with 3 users each, I feel like it’d be better to have 1 combined community with 20 users.

        Now you may be saying “heeeey, wait a second! 3+3+3 doesn’t equal 20!!!”. In which case, congrats, you passed American public school high school. But I feel like one community with more users to start with would attract more users going forward. Kind of like a snowball effect that a single split community of 3 never got the snowball rolling on.

        I like the idea of decentralized, I DON’T like the idea of fractured, and there is a difference. Right now, Lemmy feels like both.

        So you take the good, you take the bad, you roll it up, and what’dya get? The facts of life…the facts of life…

        • taiyang@lemmy.world
          link
          fedilink
          English
          arrow-up
          1
          ·
          1 month ago

          I know what you mean, especially news. I mostly do /all and it’s easily a problem there too. I think, possibly down the line, there might be a way to aggregate identical or similar posts, client side.