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
    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