

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?
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!)
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.