HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
cliqz-oss
browser-f
Web Development2019–2020
cliqz-oss / browser-f

browser-f

Cliqz Desktop Browser

Web DevelopmentMobile & Desktop
Explore on GitHubRead Hacker News discussions
3Distinct people
3Mentions
0Explicit recommenders
86GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Cliqz Desktop Browser

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by week3 dated mentions

Observed mentions: 2019-12-06 20:44:53 UTC to 2020-05-01 17:20:44 UTC. Weeks start Monday, UTC.

012019-12-02 00:00:00 UTC to 2019-12-09 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsDec 22019-12-09 00:00:00 UTC to 2019-12-16 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-12-16 00:00:00 UTC to 2019-12-23 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-12-23 00:00:00 UTC to 2019-12-30 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-12-30 00:00:00 UTC to 2020-01-06 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-01-06 00:00:00 UTC to 2020-01-13 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-01-13 00:00:00 UTC to 2020-01-20 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-01-20 00:00:00 UTC to 2020-01-27 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-01-27 00:00:00 UTC to 2020-02-03 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-02-03 00:00:00 UTC to 2020-02-10 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-02-10 00:00:00 UTC to 2020-02-17 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsFeb 102020-02-17 00:00:00 UTC to 2020-02-24 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-02-24 00:00:00 UTC to 2020-03-02 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-03-02 00:00:00 UTC to 2020-03-09 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-03-09 00:00:00 UTC to 2020-03-16 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-03-16 00:00:00 UTC to 2020-03-23 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-03-23 00:00:00 UTC to 2020-03-30 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-03-30 00:00:00 UTC to 2020-04-06 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-04-06 00:00:00 UTC to 2020-04-13 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2020-04-13 00:00:00 UTC to 2020-04-20 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-04-20 00:00:00 UTC to 2020-04-27 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-04-27 00:00:00 UTC to 2020-05-04 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsApr 27

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Dec 22019-12-02 00:00:00 UTC2019-12-09 00:00:00 UTC101
Dec 92019-12-09 00:00:00 UTC2019-12-16 00:00:00 UTC000
Dec 162019-12-16 00:00:00 UTC2019-12-23 00:00:00 UTC000
Dec 232019-12-23 00:00:00 UTC2019-12-30 00:00:00 UTC000
Dec 302019-12-30 00:00:00 UTC2020-01-06 00:00:00 UTC000
Jan 62020-01-06 00:00:00 UTC2020-01-13 00:00:00 UTC000
Jan 132020-01-13 00:00:00 UTC2020-01-20 00:00:00 UTC000
Jan 202020-01-20 00:00:00 UTC2020-01-27 00:00:00 UTC000
Jan 272020-01-27 00:00:00 UTC2020-02-03 00:00:00 UTC000
Feb 32020-02-03 00:00:00 UTC2020-02-10 00:00:00 UTC000
Feb 102020-02-10 00:00:00 UTC2020-02-17 00:00:00 UTC000
Feb 172020-02-17 00:00:00 UTC2020-02-24 00:00:00 UTC000
Feb 242020-02-24 00:00:00 UTC2020-03-02 00:00:00 UTC000
Mar 22020-03-02 00:00:00 UTC2020-03-09 00:00:00 UTC000
Mar 92020-03-09 00:00:00 UTC2020-03-16 00:00:00 UTC000
Mar 162020-03-16 00:00:00 UTC2020-03-23 00:00:00 UTC000
Mar 232020-03-23 00:00:00 UTC2020-03-30 00:00:00 UTC000
Mar 302020-03-30 00:00:00 UTC2020-04-06 00:00:00 UTC000
Apr 62020-04-06 00:00:00 UTC2020-04-13 00:00:00 UTC101
Apr 132020-04-13 00:00:00 UTC2020-04-20 00:00:00 UTC000
Apr 202020-04-20 00:00:00 UTC2020-04-27 00:00:00 UTC000
Apr 272020-04-27 00:00:00 UTC2020-05-04 00:00:00 UTC101

What Hacker News says

3 sources
chrmod·May 1, 2020
Hi. I'm one of the engineers that was working on Cliqz browsers. My focus was on the iOS one recently. All browser code was always open, you can find it on Github. iOS - https://github.com/cliqz/user-agent-ios Android - https://github.com/cliqz-oss/browser-android Android (NextGen, was planned for release next month) - https://github.com/cliqz/daisy Destkop - https://github.com/cliqz-oss/browser-f There is much more on our Github organizations: https://github.com/cliqz-oss/ https://github.com/cliqz/ We loved OSS at Cliqz, it was a part of the company culture and ultimate proof how private our products were.
In The Cliqz Story Is Over
pythux·Apr 7, 2020
Yey! This is a fun one, I fixed it in Cliqz (a browser based on Firefox) a while ago: https://github.com/cliqz-oss/browser-f/pull/912#issue-195908... If you are wondering why this discrepancy in behavior between platforms: This default behavior was initially changed to prevent a 16-years old bug in SeaMonkey, which was already fixed in Firefox since 2007. See following issues for more details: * https://bugzilla.mozilla.org/show_bug.cgi?id=190615 * https://bugzilla.mozilla.org/show_bug.cgi?id=611162 Inertia I guess... happy to see this fixed upstream!
In Firefox 75: Ambitions for April
kkm·Dec 6, 2019
Hi dessant, Disclaimer: I work for Cliqz. Would be really interesting to know your concerns with FoxyProxy.FoxyProxy is legally bound to not log the IP or share it. From the HPN protocol's perspective, data can be routed via any trusted party - in our case it's FoxyProxy. Right now, there is no way to configure this in the Browser, but should be doable. It's actually one of the motivations to move to the newer version of HPN[1]. We do agree that sending data through Tor network is the gold standard for anonymity. - We did a lot of work on getting Tor running in Cliqz browsers. It's a hard problem but definitely do-able, something we might pursue again in future[2]. - We also have experimented with WebAssembly version of Tor client to make it compatible for web extension[3]. Having the ability to use the Tor network in Cliqz products is
Read the rest
also good, because we can actually leverage the anonymity guarantees by sending data via .onion services. You can also check more details under evaluation section of the paper[4]. In case you wish to check the network traffic you can also check the debugging section[5]. References: 1. https://www.0x65.dev/blog/2019-12-04/human-web-proxy-network... 2. https://github.com/cliqz-oss/browser-f/commit/12fcef8479d9c3... 3. https://github.com/cliqz-oss/browser-f/commit/12fcef8479d9c3... 4. https://arxiv.org/pdf/1812.07927.pdf 5. https://www.0x65.dev/blog/2019-12-03/human-web-collecting-da...
In Building a Search Engine from Scratch

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.