• IngeniousRocks (They/She) @lemmy.dbzer0.com
    link
    fedilink
    arrow-up
    8
    arrow-down
    2
    ·
    2 hours ago

    I blocked .world because it’s a centrist shit hole that serves to do nothing but piss me off with whiners who don’t do shit about fuck complaining about tankies and fascists as though their no side taking ass even has a fucking seat at the table.

    Fuck .world

  • UltraGiGaGigantic@lemmy.ml
    link
    fedilink
    English
    arrow-up
    1
    ·
    2 hours ago

    It would be tight if there was a local option(What we have now) and a All option that let’s you see all the communities across all federated spaces that share that same name.

  • RedSnt@feddit.dk
    link
    fedilink
    arrow-up
    16
    arrow-down
    1
    ·
    5 hours ago

    I’m quite deliberately avoiding lemmy.world, so no, we shouldn’t just put everything on there.

  • Karu 🐲@lemmy.ml
    link
    fedilink
    arrow-up
    66
    ·
    17 hours ago

    There was some proposal that I have seen multiple times on Lemmy and at least once on the GitHub repo that communities should be able to subscribe to each other much like users can subscribe to communities. I vastly prefer this to other proposals such as auto-merging communities with the same name, which I can think of a few ways that can go wrong.

    It would also be reasonably intuitive for the average user, since following stuff is already a familiar action you take on social media. You wouldn’t really need to understand the quirks of federation to know why posting to one community makes it appear on other downstream communities. And as far as I know about ActivityPub (which is admittedly not much), it’s not a stretch use it to implement a feature like this.

    I wonder if this proposal ever reached anywhere.

      • Karu 🐲@lemmy.ml
        link
        fedilink
        arrow-up
        13
        ·
        16 hours ago

        The idea that I’m talking about is actually more like communities forming a network, with chains of following. If I host a new instance and create a memes community in it, I’d like to start having that community follow memes @ lemmy.ml and memes @ lemmy.world, so that the community already has content from the get-go, but users may be able to post memes that are unique to my instance and its followers. The followers would also see memes from upstream unless my community unfollows them, as long as they don’t also follow them independently.

        This model of the network would allow each community to independently determine which other communities it thematically implies, without the user having to follow all 4 communities with the same name but different content across the platform.

        The multireddit suggestion is more like having directories/tags for communities. It wouldn’t achieve quite the same thing, but it would be useful as well. Both ideas can coexist and complement each other.

        • Peter_Arbeitslos@feddit.orgOP
          link
          fedilink
          arrow-up
          9
          arrow-down
          1
          ·
          17 hours ago

          That’s a hyperlink. Some new www-stuff which was recently developed in one of our planet’s greates research Institutes which also has a great particle collider.

  • Sergio@slrpnk.net
    link
    fedilink
    English
    arrow-up
    39
    ·
    18 hours ago

    Crazy talk. Next you’re gonna say we only need one 196 instead of five.

      • OldManBOMBIN@lemmy.world
        link
        fedilink
        arrow-up
        6
        ·
        18 hours ago

        To be fair, it is one form of centralization; although, I admit, I was twisting the meaning of the term a bit to fit my sarcastic remark.

        That being said, as primarily a shitposting lurker who only occasionally actually creates content designed for sharing, I don’t mind the extra communities. I’m no stranger to seeing reposts, and I get my kicks from leaving the odd comment that may or may not spawn some sort of rant (usually from myself, not the other parties), but hopefully just tickles someone, and then scrolling to the next. If it’s the same thing, I just keep scrollin’.

        I could see how it would be irritating to post to multiple communities designed around the same idea, but perhaps the solution is more like turning each community into an aggregate of all similar communities. You could opt your community into a master community, and any post made in one would get shared to all of them.

  • unexposedhazard@discuss.tchncs.de
    link
    fedilink
    arrow-up
    17
    arrow-down
    2
    ·
    edit-2
    17 hours ago

    All my homies hate .world and rightfully so.

    Moving more communities away from .world is what we should be doing not the other way around.

    As others have pointed out, if you try to move to .world people will just riot and make a new community elsewhere. Dont try, its a ridiculously stupid idea.

    • Peter_Arbeitslos@feddit.orgOP
      link
      fedilink
      arrow-up
      2
      arrow-down
      2
      ·
      17 hours ago

      Again something the mods have to talk about. It’s something the mods have to discuss about (the community can take part in that discussion too, democracy and stuff). We could for example merge to lemmy.ml.

      • lugal@sopuli.xyz
        link
        fedilink
        arrow-up
        3
        ·
        2 hours ago

        All my homies hate .ml and rightfully so.

        Moving more communities away from .ml is what we should be doing not the other way around.

        As others have pointed out, if you try to move to .ml people will just riot and make a new community elsewhere. Dont try, its a ridiculously stupid idea.

  • deus@lemmy.world
    link
    fedilink
    arrow-up
    12
    ·
    18 hours ago

    There should be a way to see the content from different communities with the same name but from different instances in the same page, like some sort of automatic multireddit. The content would probably be limited to instances federated with your home instance but even then it’s something I would like to have.

    • Karu 🐲@lemmy.ml
      link
      fedilink
      arrow-up
      5
      ·
      16 hours ago

      You cannot assume that communities with the same name are meant to be on the same topic.

      Say I set up an instance focused on discussing parties at home. There are fun in-person games you can play with your friends when many of you are over, so I would create a community c/games for discussing them. Now, what if I want my instance to federate with lemmy.world? They already have a c/games that is dedicated to videogames. Maybe I also would need a community dedicated to videogames, but I’d have to call it c/videogames, because I already have a c/games.

      Some human intervention would be required to let the network know that the local c/videogames is the one that has to federate with lemmy.world’s c/games, and not the local c/games.

      Maybe an automatic suggestion would be fine as a starting point, but it would be more useful that communities themselves could explicitly establish which remote communities they are associated with, without depending on the names.

    • Peter_Arbeitslos@feddit.orgOP
      link
      fedilink
      arrow-up
      3
      ·
      edit-2
      17 hours ago

      That’s actually a pretty idea. I’m imaging something like a tool included into lemmy where you can collect different subs into one folder and even share these/export those folders as xml or json to a new account… And now we’re talking about RSS-feeds. Basically.

      But RSS-feeds included into lemmy. I don’t really know if that would help to get rid of reposts, but it’s certainly an interesting idea. Something one would have to integrate in an Lemmy update, so you would need to contribute to the Lemmy code.

      • JustAnotherKay@lemmy.world
        link
        fedilink
        arrow-up
        2
        ·
        17 hours ago

        I actually love this idea. I’m on a federated service, why do I need to go to 3 meme communities on 3 instances when I could go to “meme” and see all of them?

        Crossposts from within the cross-feed could be automatically hidden to avoid showing the same post multiple times, and then we just start spreading the word to crosspost instead of reposting. I think the only issue is that this would definitely be better to implement client-side because AP is just a protocol to move data, whereas this requires checking too many user-defined variables to make it idiomatic easily. I could be wrong though, I don’t know the AP code very well