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.

  • @[email protected]English
    12•1 year ago

    This is not obvious to anyone who doesn’t have some understanding of how networking and federation work, which is most people. Especially if we’re talking about users who have only ever experienced centralized platforms.

    It should be called “Known Network” or something more transparent that doesn’t require an explanation of indexing

    • Jeena
      1•1 year ago

      I agree. But the attitude of those users just ribbs me the wrong way.

      • @[email protected]English
        7•1 year ago

        It’s an understandable response. They were previously in a position where this was such an obvious concept that it didn’t merit any thought, and now they are required to have an understanding of networking and federation in order to understand how well actually this a fundamental part of how distributed systems work and isn’t technically a bug.

        From their perspective this seems like a fairly straightforward problem. Obviously (to us) it’s not, but the threshold for the fediverse shouldn’t be that you deeply understand federation if there’s ever going to be meaningful adoption.

        As an aside, your personal domain is timing out.

        • Jeena
          0•1 year ago

          Damn, thanks, I have a bad implementation of getting Twitter avatars and now that Twitter redirects everything which is not logged in my implementation goes into redirect hell every time someone opens a page with a Twitter comment. Perhaps I’ll find the time tonight to look for a fix.

          • Jeena
            0•1 year ago

            It seems I was able to fix it by adding curl.max_redirects = 3 to my caching code. No idea why it would hang without it because it gets the image from Twitter just fine now too.