Hey all, so I’ve been trying to embrace the fediverse life. My background - I’ve been on the internet since pre-WWW, so I’ve seen it all.

I think there’s a structural issue in the design of Lemmy, that’s still correctable now but won’t be if it gets much bigger. In short, I think we’re federating the wrong data.

For those of you who used USENET back in the early days, when your ISP maintained a local copy of it, I think you’ll pick up where I’m going with this fairly quickly. But I know there aren’t a ton of us graybeards so I’ll try to explain in detail.

As it’s currently implemented, the Fediverse allows for multiple identically named communities to exist. I believe this is a mistake. The fediverse should have one uniquely named community instance, and part of the atomic data exchanged through the federation should include the instance that “owns” the community and a list of moderators. Each member server of the Fediverse should maintain an identical list of communities, based on server federation. Just like USENET of yore.

This could also be the gateway into instance transference. If the instances are more in-sync, it will be easier to transfer either a user account or a community.

This would eliminate the largest pain point/learning curve that Lemmy has vs Reddit.

Open to thought. And I’ll admit this isn’t fully fleshed out, it was just something I was thinking about as I was driving home from work tonight

Lemmy is good, but it could be great.

  • avantgeared@kbin.social
    link
    fedilink
    arrow-up
    0
    ·
    edit-2
    2 years ago

    Solution is hashtags + community name, not a “fedicommrc”.
    I was in FidoNet with a BBS in 1988 and on the Internet since 1990 first through a dialup vt100 connection to a Unix login access point for usenet and email before the Internet was available to the public. Communities are a special interest of mine. I started a particularly good one for Permaculture using a mailing list with email. I still run it. Noone should, for example, OWN the only permaculture community in the Fediverse. What are others who want their own going to do to gain users and generate traffic? call it permaculture2 or thatotherpermaculturecommunity or permaculture-general or permaculture-westernworld. Letting one group control any particular Fediverse named community is a really bad idea. Have you ever started and run a community (newsgroup, mailing list, subforum, fb group, google group, webforum, whatever)? Having one group control any named community is bad enough but everyone with an instance having to deal with a fixed list of communities for the entire Fediverse is absurd. You could easily have a multiplicity of communities with the same name but identified with hashtags for subjects they specialize it. This should solve your problem with community naming and with this no distributed list of communities for instances to carry would be needed. You could carry 6 different permaculture communities and each would be uniquely identified with hashtags alone. Make sure to code the software to feature those hashtags prominently along with the community name for ease of finding and subscribing to them.
    Are you talking about a Fediverse version of a Usenet newsrc? Those who install an instance and want their own communities named as they choose would just do that and ignore any network-wide policy. Other instances can block them for doing that but they can simply connect with other like minded instances and form their own network and forget Federation. This is especially true when some gang of control freaks own a named community, i.e. permaculture. That is not going to fly. Disunity but independence within the Fediverse will rule.

  • cowvin@kbin.social
    link
    fedilink
    arrow-up
    0
    ·
    2 years ago

    I think that would defeat a piece of the point of a decentralized system. In the current design, what will naturally happen is that if one instance has all the good content on a particular topic, most users will gravitate toward it anyway. We can read across federated instances anyway so I, a kbin user, have no problem reading something on lemmy like this.

    Then let’s say one day lemmyworld@lemmy.world gets taken over by people who want to post stuff I don’t want to see. If I miss how it used to be here, I could go make lemmyworld@kbin.social and it would be fine.

  • funkyb@lemmy.world
    link
    fedilink
    English
    arrow-up
    0
    ·
    2 years ago

    not sure that solution is a good one for this environment. I’m new but from what i’ve seen the concept of moderation is different and your solution is trying to engineer a reddit-like moderation design to an architecture that is fundamentally not reddit-like. Moderation here is at the instance level, not the community level.

  • kubica@kbin.social
    link
    fedilink
    arrow-up
    0
    ·
    2 years ago

    I can’t form an opinion right now.
    If all similar communities appeared combined into a single community I’d still be likely to want to still filter out sources.
    But at the same time sometimes a place to see them all together sounds appealing.
    It seems that I want both, but probably what we have now is the most flexible, forcing less limitations.

  • plz1@lemmy.world
    link
    fedilink
    English
    arrow-up
    0
    ·
    2 years ago

    Ether that or allow formeta-communities so that the 500 duplicate copies of “Technology” can self aggregate.

      • _sigma@kbin.social
        link
        fedilink
        arrow-up
        0
        ·
        2 years ago

        But with some fine grained tag support or similar, one could have a super powerful multi-reddit-esq thing that would make it easy to consume a specific type of content.

        • llama
          link
          fedilink
          arrow-up
          0
          ·
          2 years ago

          This I would really like to see, and be able to group my subscriptions into feeds however I want instead of just the default subscribed feed. And it seems like it would be relatively simple to implement.

      • MentalEdge@sopuli.xyz
        link
        fedilink
        English
        arrow-up
        0
        ·
        edit-2
        2 years ago

        I think the mods of each sub should agree to aggregate using an “invite”. It could also allow subs that have slightly different names on different instances to team up, if they are essentially the same thing.

      • DekkerNSFW@lemmy.fmhy.ml
        link
        fedilink
        English
        arrow-up
        0
        ·
        2 years ago

        I think that would self-correct when such a thing would be implemented. They’d just get more specific names, like solarpunktech or such. It would be an issue for existing communities like that though.

  • miridius@lemmy.world
    link
    fedilink
    English
    arrow-up
    0
    ·
    edit-2
    2 years ago

    Unless I’ve misunderstood something, community names are already globally unique and multiple identically named communities cannot exist, you’re just not looking at the full name.

    Memes@lemmy.ml and Memes@sopuli.xyz are different names, for example.

    Sometimes we ignore the part of the name after the @ if it’s unambiguous, but it’s still there.

    • Overzeetop@lemmy.world
      link
      fedilink
      English
      arrow-up
      0
      ·
      2 years ago

      tl;dr: I agree with OP that the ability to have multiple, identically named, disconnected communities on different instances will be a severe detriment to the adoption of the Fediverse by the general public.

      community names are already globally unique and multiple identically named communities cannot exist, you’re just not looking at the full name.

      That’s part of the problem. The simplest UI generally exposes the community name without the instance, !memes for example, but the backend is really !memes@lemmy.ml which is an entirely different community from !memes@sopuli.xyz. Now, that’s not really a problem - memes are memes. But what about a community for Edinburgh, UK? There are already two - !Edinburgh@sh.itjust.works and !Edinburgh@feddit.uk. That’s going to be an issue because if you choose one to participate in, you’ll miss all of the content in the other. If you’re a member of, say sopuli.xyz, you won’t even know that either exist because their community search doesn’t actually search all instances and might start a third. The whole idea of the Fediverse is to have a federation of instances which share information, and there is already talk of the biggest instances potentially creating a problem with the democratic ideals of the system (6 days into the reddit migration and three of the largest instances have defederated from one another). To have a thousand instances each with their own !Photography or !ManchesterUnited community dilutes the content and interaction.

      I agree with OP ( I actually don’t know how to link to a profile yet or I’d tag @TerryMatthews) that there should be some cross-linked mechanism to merge identically named communities across instances. There could still be detached instances - defederated content would not have their content propagated - but the content for each unique community would be co-mingled.

      I would expect that moderators would be limited in scope to their own communities. So a mod from feddit.uk could block a non-instance post or user on their instance but it would be present on other instances. They could also block a local post on their instance and it would not be propagated at all. Pinned posts get a little more hairy - would every mod have a separate set of local instance pins? I would think that would need to be the case. The issue of sidebars is also an issue.

      • dissonant@lemmy.world
        link
        fedilink
        English
        arrow-up
        0
        ·
        2 years ago

        The ability to create multis could solve that. I could make a local Edinburgh multi, sub to both of the communities, and view them together in one feed for example.

        • Overzeetop@lemmy.world
          link
          fedilink
          English
          arrow-up
          0
          ·
          2 years ago

          That would definitely fix the reading side of things. As would a reader/aggregator app which allows browsing (and discovery) of all the Fediverse instances as a unified feed. It still leaves the challenge of propagating information though communities without either leaving large swaths of the community in the dark or risking multiple posts (for people who do multi./aggregate). The last programming language I can claim to have studied is Fortran (77, no less), so my hope is only that someone competent shares my concern.

      • lotanis@discuss.tchncs.de
        link
        fedilink
        English
        arrow-up
        0
        ·
        2 years ago

        The “two Edinburghs” situation already existed on Reddit. You’d get slightly different “competing” subreddits. They’d have to differentiate their names a bit but it still happened.

        To flip it round - there was an issue in Reddit that whoever first set up a subreddit with a given name then owned it forever. Let’s say I got there first for /r/london but then I’m a twat and either create a community of horrible people or fail to build a community at all. Everyone in London who wants a city subreddit is worse off, and at best someone has to come along and make a different subreddit with a different name to fulfill the same person. Not having this single namespace with “first mover” advantage is good and democratic. And all we have to do is pay attention to the bit after the @ sign.

        • Overzeetop@lemmy.world
          link
          fedilink
          English
          arrow-up
          0
          ·
          2 years ago

          That’s fair. Sometimes there are competing/unfriendly communities on the same topic (EliteDangerous and Elite_Dangerous sub mods hate each other with a fiery passion for…reasons). Since writing my post I’ve stumbled upon another poster suggesting a fix may be on the user side (a fediverse aggregating reader) rather than attempting to somehow weave communities together on the server end. That does mostly what’s needed (imho) without requiring any additional overhead on the instance ends.

  • Freeman@lemmy.pub
    link
    fedilink
    English
    arrow-up
    0
    ·
    2 years ago

    As it’s currently implemented, the Fediverse allows for multiple identically named communities to exist. I believe this is a mistake. The fediverse should have one uniquely named community instance, and part of the atomic data exchanged through the federation should include the instance that “owns” the community and a list of moderators. Each member server of the Fediverse should maintain an identical list of communities, based on server federation. Just like USENET of yore.

    Hard disagree. This allows abuse by moderator abuse similar to how reddit does it. Ideally the UI would allow you to create collections of communities based on your own groupings. And search could be expanded to find more similar communities (ie: based on keywords).

    The way loading/finding and joining a totally new community into a new external instance is kinda buggy.

      • Freeman@lemmy.pub
        link
        fedilink
        arrow-up
        0
        ·
        edit-2
        2 years ago

        Sorry. Was getting late and comment submissions have been weird.

        Personally I am hoping for 2 or 3 changes thst I went into here.

        https://lemmy.pub/comment/2889

        -1. Create multi-communities thst you can group together multiple different communities across instance into a single place based on whatever criteria. Basically like multi-reddits and allow them to be public/shared or private. This would allow the load to be spread across instances and different moderation strategies to take place without a single community becoming some weird power grab.

        -2. Makes links to other instances and communities always open in your instance so you dont have to constantly create a https://my-instance.com/c/community@othernstance.com style link. Basically what this site is doing, but integrated into your own communities section.

        -3. Like above, Improve search and communities to index basic stats before you have to externally find and, search multiple times to get your instance to discover the communities then open the federated link an subscribe. And when on a multi-community aid it discovery of new additions with a basic keyword search. This one is probably the most difficult and may scare some folks from privacy standpoint. But could be mitigated a bit if you can make option one public for others to subscribe to or use mutlis they didn’t compile themselves.

    • MentalEdge@sopuli.xyz
      link
      fedilink
      English
      arrow-up
      0
      ·
      edit-2
      2 years ago

      Yeah, basically we need somthing like public and private multireddits. Public, so you can sub to one thing to get content from many similar communities, and private, for people to organize their own stuff.

    • PixxlMan@lemmy.world
      link
      fedilink
      English
      arrow-up
      0
      ·
      2 years ago

      I agree. I think people come here believing their vision of the fediverse has to be the vision and anything else is a bug, but that’s not necessarily right.

      • MiddleWeigh@lemmy.world
        link
        fedilink
        English
        arrow-up
        0
        ·
        2 years ago

        Imo that’s kind of the beauty. It’s whatever the people want it to be. You can curate your own experience on your end and the users sort themselves out. So as time goes, your experience naturally becomes what you want it to be. It’s confusing at first, but I think it’s actually a good practice in the long term, and even a good way to practice mindfulness in regards to your content consumption.

      • dekatron@lemmy.fmhy.ml
        link
        fedilink
        English
        arrow-up
        0
        ·
        2 years ago

        When I first came here from reddit, my vision was heavily skewed by what I’m used to. However, the more I learn about the fediverse, the more I appreciate the differences and the value of small communities.

    • Isaac@lemmy.world
      link
      fedilink
      English
      arrow-up
      0
      ·
      2 years ago

      Couldn’t agree more. Naturally, the best communities will become more used and have better content over time, but de-federation is the key feature of all of this. It’s necessary.

  • Elle@lemmy.world
    link
    fedilink
    English
    arrow-up
    0
    ·
    2 years ago

    This could also be the gateway into instance transference. If the instances are more in-sync, it will be easier to transfer either a user account or a community.

    I think this is perhaps the most compelling part of your thinking here, but at the same time, I’m more drawn by the idea of improved portability of instance information than the synchronization.

    I may be mistaken, but I think a fundamental aspect of the federation model is the independent operations of each community while enabling their intercommunication, and the sort of synchronization you suggest would be a violation of each instance’s autonomy to a degree. Not to say it’s a bad idea, just that I think it would better fit a different networking model than what I think the federated model seems to be pursuing.

  • foo@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    0
    ·
    edit-2
    2 years ago

    USENET was a mess too, though… The entire Alt.* hierarchy was an attempt to route around censorship and I’m pretty sure I recall lots of duplication of groups. /derail

  • Stardust@kbin.social
    link
    fedilink
    arrow-up
    0
    ·
    2 years ago

    Communities should have categories/hashtags that users can optionally sub to, like the ‘metacommunities’ like plz1 said but optional and multiple. Mastodon does hashtagging and can be done on a post by post basis. The forum software Flarum has a ‘tag’/category system and an additional hashtag system, so what I’m thinking of is more like the Flarum system since it would be awkward to hashtag every single post in a community/magazine/whatever.

    So if I wanted to just get solarpunk tech I’d sub to that, but if I wanted that and even moar I’d sub to a generalized Tech tag. Make sense?

    • shua_too@kbin.social
      link
      fedilink
      arrow-up
      0
      ·
      2 years ago

      @Stardust this is a great approach I see suggested often. A 2-dimensional identity for a community; one through tags, another through names/policies/wikis/sidebar info. Like, you might have users see all the time and identify with from a specific sub, and also have labeled/mechanical community interaction with much less familiar people in the tags if that makes any sense. Kind of like how Reddit would recommend related posts from adjacent subs I suppose, but this would be on a user-generated level.

      @TerryMathews

    • Kuma@lemmy.world
      link
      fedilink
      arrow-up
      0
      ·
      2 years ago

      I am glad I read through the comments first because this is what I was going to suggest. Because you may not want to see all the comms post because some are more friendly then others and some may only post in an language you don’t understand. With tags you can discover all the comms or even create one feed with comms like #tech #English #Japan you never even sub to them unless you need to manage those particular comms/posts with those tags.

      We could make it possible to group tags so there are multiple feeds and you can pick to see all feeds or one or many that you have created. It will be like groupings all of the comms/post you like together to one community but making it very personal because you may only care about tech in Japan but you want to have all the news from your country and maybe do not care what country memes comes from. But if you really want to mange them by comms then that should be an option to. So the tags will be a tool to discovering comms instead then.

    • polygon@kbin.social
      link
      fedilink
      arrow-up
      0
      ·
      edit-2
      2 years ago

      This is the best solution I’ve heard so far. Any server could have their own Technology group. Using Federation, anyone from anywhere could subscribe to each of them. Or, instead of subbing to each of them you just sub to the !tech tag, and you automatically get content from all of them. When you start a community you apply any tag you want to be included in.

      To me, the instance should be mostly invisible/seamless. Subbing to tags instead of instance communities puts the focus on the content rather than where the content came from. Tags would make one large meta community that simulates how that other site feels, but with the option to still subscribe to a specific community if you ended up liking it more.

      Say for instance one of the !tech groups ends up with really good content and discussions and the other smaller ones end up with a lot of duplicates and low quality comments. You’d easily be able to see which one you’d want to sub to directly. In this way tags would make community discovery much easier. Instead of having to seek out 10 different groups on 10 different instances, you sub to a general interest tag and either that works well enough or you discover the one you like the most and sub to that one directly.

      • cendawanita@kbin.social
        link
        fedilink
        arrow-up
        0
        ·
        2 years ago

        @polygon I’ll be interested to see this happen in the threadiverse side of things (all these link aggregation protocols like L/k right now). In the larger fediverse, this (tracking hashtags) is basically the number one way to do discoverability (i won’t get into why but suffice to say straight search isn’t fully supported technically and normatively). All the microblogging protocols (masto is one) allows you to follow hashtags (and the contents will show up on your timeline without having to follow accounts), though how it’s done is different based on protocol. I’m curious to see why L/k doesn’t automatically allow user accounts to do this, perhaps that was the whole point of the comms/mags.

        @TerryMathews @Stardust

  • Margot Robbie@lemmy.world
    link
    fedilink
    English
    arrow-up
    0
    ·
    2 years ago

    I disagree respectfully, as I think this is a feature and not a bug of a federated structure. It’s well known that reddit suffers from the “20K Law”, which is that “The quality of any subreddit drops off a cliff after it gets more than 20K subscribers”. Which is likely because that is the limit of effective manual moderation.

    So, having multiple communities on the same topic would be a fundamental fix to that issue, as instead of one giant community, instead you get different, smaller communities with different culture on the same topic, whose users can still talk to each other.

    I think the current system is fine as is, we’re not trying to remake a better reddit, we are trying to be better than the limits of reddit.

  • SpacemanSpiff@kbin.social
    link
    fedilink
    arrow-up
    0
    ·
    2 years ago

    I understand your idea, but I think it would defeat the purpose of the fediverse. It would create single points of failure that are un-correctable.

    I also think many people forget that Reddit never functioned any differently. Everyone seems to have forgotten (and I’m not saying you have!) that there are and were always multiple subreddits for any given topic. With slightly differing names. The only reason people are forgetting this is because eventually one or a handful became pre-eminent and the others died or became transformed into something more niche.

    I think it’s a problem that will ultimately correct itself, but I think a tags based system, like hashtags in Mastodon, would be a better solution for tying communities/magazines together through metadata.

  • DocMcStuffin@lemmy.world
    link
    fedilink
    English
    arrow-up
    0
    ·
    2 years ago

    I see this suggestion as problematic and recreating a problem reddit had. One group could lay claim to territory and everyone was stuck with however good or bad the culture was in the sub and however good or bad the mods were. There were some places with mods on a powertrip creating an exclusionary or outright toxic environment.

    • girthero@lemmy.world
      link
      fedilink
      English
      arrow-up
      0
      ·
      2 years ago

      One group could lay claim to territory and everyone was stuck with however good or bad the culture was in the sub

      This problem is easily surmountable with a new community name. Its not like it doesn’t happen anyway because for example c/trees isn’t about trees across multiple instances. Also i think ‘syncing’ a community could be optional decision between federated instances. If one instance grows to have values that disagree with your instance community you no longer sync that community and possibly defederate.