- cross-posted to:
- privacy@lemmy.ml
- cross-posted to:
- privacy@lemmy.ml
Today we are announcing a new privacy feature coming to Kagi Search. Privacy Pass is an authentication protocol first introduced by Davidson and recently standardized by the IETF as RFCs. At the same time, we are announcing the immediate availability of Kagi’s Tor onion service.
In general terms, Privacy Pass allows “Clients” (generally users) to authenticate to “Servers” (like Kagi) in such a way that while the Server can verify that the connecting Client has the right to access its services, it cannot determine which of its rightful Clients is actually connecting. This is particularly useful in the context of a privacy-respecting paid search engine, where the Server wants to ensure that the Client can access the services, and the Client seeks strong guarantees that, for example, the searches are not associated with them.
[etc…]
Kagi has been criticized for removing their list of partners - originally, they admitted to partnering with Yandex, but they recently hid that partnership after receiving backlash. I’m not sure if the changelog will reflect that information, but I am curious to check now.
Let us know what you find, if anything please.
I’m definitely interested in this service, but I’ve seen some suspicion surrounding it.
Originally they listed Yandex along with naming other major search engines, then later changed the language to say simply “major search engines”.
What’s the issue if API calls are anonymous?
https://github.com/kagisearch/kagi-docs/commit/6baff1c066db9b3d804653ea19bc9d1c076a710b