It’s excruciatingly obnoxious to have to rely on third party sources for what should be a first-party feature.

Like, I select all and then search a query. “Oh no, nobody on your server used a third party service to find it, so you won’t see it here.”

Like, how short-sighted is that, really? If I search for a string in the ‘all’ servers, I should have a list of ‘all’ the servers containing that string.

It’s a really simple concept. Not sure why this post even has to be made, but I’m wondering if there’s something I can do to make these ‘features’ more intuitive.

  • InquisitiveFactotum@midwest.social
    link
    fedilink
    English
    arrow-up
    4
    ·
    1 year ago

    Forgive what is probably a silly naive question…

    Can someone point me to an explanation of the federated architecture of lemmy? I haven’t found one yet that has helped me build a good mental model. I either get a step-by-step startup guide, or discussions on the merrits/demerits of a distributed system.

    I think I’ve pieced together that it’s basically independent “instances” of the machine each with their own communities within. Sort of like if there were multiple instances of reddit, each with its own r/aww or whatever. I don’t yet understand, however how these interact/relate/ovelap/collaborate…which I think is the basis for this thread.

    • larvyde@sh.itjust.works
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      when a user (let’s call them Kim) on one instance (let’s call it “Works”), subscribes to a community on another (let’s call that one “World”), Works creates a copy of the community on its own database. It also asks World to notify it when there is an update to the community – when there is a new post, new comment, up/downvote, something gets deleted, etc. Kim can now browse and interact with the community on Works. Works will also notify World when Kim does something in the community so everything syncs and everyone sees the same thing.

      So really, the problem OP is describing is simply a natural consequence of communities not existing on Works until someone subscribes to it.

      • InquisitiveFactotum@midwest.social
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 year ago

        Thanks, this makes sense. So, the last thing I’m wondering about is the redundancy/exclusivity of communities. For example, could there be a community called ‘gardening’ on the “Works” instance and also an independent community by the same name on “World” (before anyone is mutuallt subscribed)? Seems like it could… And if so, what happens when someone cross subscribes to ‘gardening’.

        Specifically, (from a user experience standpoint) do these redundant communities coelesce into one? Because some of the benefit of these communities (particularly the more niche) is pulling together the experts into one community.

        • larvyde@sh.itjust.works
          link
          fedilink
          arrow-up
          1
          ·
          1 year ago

          The gardening community on World will be called gardening@World on Works. they will continue to be distinct communities, and you can subscribe to either or both independently