• 3 Posts
  • 136 Comments
Joined 3 天前
cake
Cake day: 2026年2月10日

help-circle



  • GraphaneOS founder has fetish for Chromium and he hates F-Droid 1

    tldr: he accuse f-droid not being secure and citing this bs post https://privsec.dev/posts/android/f-droid-security-issues/ and he promotes accrescent.app

    • they contain closed-source app
    • they have very flawed understanding of open-source and security 2, 3

    here is some examples:

    Open source doesn’t necessarily mean more secure. I’m aware of many open source apps with numerous well-known security vulnerabilities, as well as many closed-source apps that are highly secure. Furthermore, Accrescent will have a filter to, for example, show only open source apps, so your treatment is incomprehensible.

    Accrescent doesn’t claim to serve only open-source apps and never has out of the belief that an app’s source model doesn’t inherently make it more or less private or secure. Qlango doesn’t violate any explicit or implicit Accrescent policy by the properties you listed, so it would be inappropriate to remove it.

    …In addition, “trackers” are subjective. Accrescent has no plans to enumerate specific libraries or classes and blacklist them solely based on the fact that they connect to Google, Amazon, etc.; collect analytics; or contain proprietary code. This approach isn’t scalable anyway because it is trivial to bypass such detection methods.

    So I take everything GraphaneOS says with a grain of salt




  • They listed their sources before and they removed https://web.archive.org/web/20231228222303if_/https://help.kagi.com/kagi/search-details/search-sources.html

    But than this month they write a blog https://blog.kagi.com/waiting-dawn-search and revealed everything again

    Vendor 	Status
    Mojeek 	Direct license
    Brave 	Direct license
    Yandex 	Direct license
    Wikipedia 	Direct license
    TripAdvisor 	Direct license
    Yelp 	Direct license
    Apple 	Direct license
    Wolfram Alpha 	Direct license
    Our own Small Web Index 	Proprietary
    
    With Google and Bing, we failed - not for lack of trying.
    
    Bing: Their terms didn’t work for us from the start. Microsoft’s terms prohibited reordering results or merging them with other sources - restrictions incompatible with Kagi’s approach. In February 2023, they announced price increases of up to 10x on some API tiers. Then in May 2025, they retired the Bing Search APIs entirely, effective August 2025, directing customers toward AI-focused alternatives like Azure AI Agents.
    
    Google: Google does not offer a public search API. The only available path is an ad-syndication bundle with no changes to result presentation - the model Startpage uses.
    

    and “it doesn’t just act as a proxy for other search engines” it exactly does this, Teclis is <1% of the results (you can see yourself https://teclis.com/)