• @jetA
      link
      English
      111 months ago

      It really is though. You have to know about which communities to subscribe to to get them federated on your instance. Which is a pain in the butt. It’s not a good workflow. You’d have to use some external Lemmy community website, convert the link into the bang link, then put it into your mobile client. And then subscribe. It’s a terrible workflow.

      It’s extremely high friction, which means smaller instances are only going to know about the large communities that people bother to do it for.

      Am I hopeful this workflow gets better? Absolutely! I have faith that this workflow will get better on many clients. But right now it’s high friction very high friction

      • @fr0g@infosec.pub
        link
        fedilink
        1
        edit-2
        11 months ago

        Oh, okay, so you’re talking about a case scenario where you’re on a small/new instance that also isn’t your own. Got it, dunno why I was making a different assumption. Yeah, I can see what you’re talking about then.

        • @jetA
          link
          English
          211 months ago

          Even if it is my own instance. It’s still high friction. Populating small instances, which is what we want in federation right? We want lots of distributed instances. We need central discovery, or distributed discovery, right now there’s basically no discovery at the instance level

          • @fr0g@infosec.pub
            link
            fedilink
            211 months ago

            Yeah, on a more practical note, the liftoff lemmy app has lemmy.world baked in (and makes it fairly easy to add other instances to) which is a fairly big instance so its all feed could be a good point to start adding stuff in a fairly straightforward way. Not saying that’s as good as adding better discovery to mainline lemmy, but maybe a somewhat low barrier option to share with people who might find it useful in the meantime