Frustratingly, doing a search on that Changelog page for sources is mostly full of stuff not relevant to my search.

I did find a different post on Lemmy that talks about it, though. This post is incredibly thorough, and does an excellent job of undoing Kagi’s attempt to memory-hole the information about which sources they use.

This makes it all the more frustrating that Vlad refuses to re-add them, instead asking to know why we would care. Here’s a link to that conversation, which is on a platform controlled by Vlad, which appears to be resistant to archiving services that attempt to fetch those particular comments. Also for posterity:

slamor
Oct 27, 2024
https://help.kagi.com/kagi/search-details/search-sources.html

There is really no proper information about search sources. We need to know what resources are used and at what rate.

Please make a more detailed and clear edit.

Vlad
Oct 29, 2024
[@]slamor Is there any particular reason you are asking for this? More context will help us better understand the need.

slamor
Nov 2, 2024
[@]Vlad why not?

Searching through kagi.com for “Yandex” yields a lot of dead links. The one living link is the Changelog, which says they added Yandex to their image search, back in December 2024… But that’s hardly a revelation. The changelog doesn’t go back very far either, AFAIK

As for the other links: Google says these links used to contain it the word, but I don’t know why. Maybe this one was for raised sites, maybe it was for lowered sites, which would at least give a little insight into whether users loved or hated the domain…

url: https://europe-west2.kagi.com/stats?sd=asc&st=percentage
text: yandex.com. zlibrary.to. androidcentral.com. answer-all.com. baijiahao.baidu.com. cbc.ca. developer.apple.com. eightify.app. github.getafreenode.com. gitmemory …

Another result seems to suggest Yandex Images served up a photo of Steve Jobs in a demo search, but that is no longer the case. Maybe it’s just a coincidence.

url: https://kagi.com/images?q=steve+jobs
text: 564 x 318 yandex.ru. 20 Steve Jobs Quotes: Wisdom from the Apple Co-Founder 20 Steve Jobs Quotes: Wisdom from the Apple Co-Founder. 696 x 418 cioviews.com. 75 …

SOURCE

  • @asap
    link
    English
    44 days ago

    What’s the issue with this? API calls to other search engines are anonymised, and naturally I want Kagi to search as many sources as possible.

    So what’s the issue?

    You don’t need Wayback machine to find their old page, it’s all open on Github: https://github.com/kagisearch/kagi-docs/commit/6baff1c066db9b3d804653ea19bc9d1c076a710b

    I don’t see any “conspiracy” removing an itemised list - it’s just something which is a pain to keep up-to-date over time. Better to say “all major search engines worldwide”, which is what they’re now saying.

    Again, I don’t really see any issue here…

    • @[email protected]
      link
      fedilink
      English
      12 days ago

      So what’s the issue? You don’t need Wayback machine to find their old page…

      The issue is that the page is old and hidden! Normal people don’t hunt through repositories, let alone archives. It is extremely unreasonable to assume someone should do this.

      Kagi Corp should provide this information transparently, not respond with mild hostility when that information is politely requested. In addition, they should keep it up to date! Acting cagey with users and hiding data isn’t how an honest corporation should behave!

      • @asap
        link
        English
        1
        edit-2
        2 days ago

        The topic is “using Yandex”. What’s the issue with that? I wasn’t asking what is the issue with changing the wording on some random page 🤦

        • @[email protected]
          link
          fedilink
          English
          1
          edit-2
          2 days ago

          The topic is “using Yandex”.

          No it was not. Read the post. The topic was obfuscation.

          That obfuscation did come from an interlinked issue (Vladimir Prelovac getting caught paying Yandex for search data), but this year that concerned me was Kagi hiding this information from the community.

          Do we not agree that being cagey about things and hiding once-public information is a red flag when it comes to privacy?

          • @asap
            link
            English
            121 hours ago

            As I said in my original comment, I think it makes perfect sense to replace an itemised list - which needs to be constantly updated - with a generic “all major search engines” which covers everything.

            If Yandex being removed isn’t an issue, then I’m not sure what could be termed as Proton being cagey.

            For me, from a privacy perspective as a user it’s largely irrelevant what third-parties they use on the backend as long as my searches stay private.

            Adding the statistics for third parties to their stats page would be neat from the user perspective, but I can’t imagine what value there would be in publishing that information from Kagi’s perspective.

            • @[email protected]
              link
              fedilink
              English
              120 hours ago

              Let’s agree to disagree, then. I also disagree on the framing: you call it inconvenient, I call it a clear step backwards in terms of transparency. We can even compromise: CEO Vladimir Prelovac can simply update the list when he finds time. (He can even take time off from his occasional searches for online critics!)

              For me, from a privacy perspective as a user it’s largely irrelevant what third-parties they use on the backend as long as my searches stay private.

              This is largely circular logic. “It’s irrelevant what Kagi is doing, as long as I can trust what Kagi is doing.” You should never trust an opaque company. A company that becomes more opaque upon scrutiny is not a trustworthy company.

              • @asap
                link
                English
                120 hours ago

                This is largely circular logic. “It’s irrelevant what Kagi is doing, as long as I can trust what Kagi is doing.”

                The problem is that you can never know what software a company is running in production. So for any service you don’t host yourself, at some point you have to just cross your fingers and hope.

                We can certainly agree to disagree. I don’t encourage you to use Kagi - quite the opposite, I would say it is a terrible fit.