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.

  • Blaze (he/him)
    link
    fedilink
    11 year ago

    Resource wise, it makes sense to only retrieve content the users of the instance are interested in. Think about all the nsfw communities popping on lemmynsfw and pornlemmy, as well as all the content in languages your users don’t speak.

    Some instances are multilingual, so you don’t want to defederate from them (and defederation shouldn’t really be used in this context anyway), but retrieving 50% of content none of your users is ever going to read seems like a waste.

    • @[email protected]OP
      link
      fedilink
      1
      edit-2
      1 year ago

      Yeah. And I’m interested in retrieving all of the servers my instance is connected to that contain a string in that community name.

      Why is this so hard to get across to you?

      Why don’t you have a solution for how server members find communities on different servers in the first place? Are you really defending relying on third-party services and ‘other means’ to find communities on different servers?

      I think that’s really bad design and a testament to why the fediverse is inaccessible to the general public.