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.

  • Mmagnusson@programming.dev
    link
    fedilink
    arrow-up
    0
    ·
    edit-2
    1 year ago

    While it has problems of its own, instances could pool and share that knowledge. The first time an instance talks to a different insta ce it could just ask “hey, what other instances are you aware of?”. The main issue there is just instances obsessively sending exponentially growing lists of instances back and forth.

    But no, that is the main bane of federated social media, discoverability without a center of truth

    • PupBiru@kbin.social
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      yup! 100% agree! federation is kind of a new thing and we have some issues to work out that’s for sure!

      heck, i could even see some kind of federated search service: activitypub instances could submit their content for indexing and individual instance could choose an existing, or run their own federated fediverse search… importantly, there would need to be choice for each individual instance with no centralised repository