13 ms·

Cliqz had a lot of docs at the time about ways to preserve privacy with client side systems that clearly took a lot of developer effort to research. Their reput

Cliqz had a lot of docs at the time about ways to preserve privacy with client side systems that clearly took a lot of developer effort to research. Their reputation is undeserved unless new information came out

weinzierl 5y ago
Do you have a reference to documentation that shows that it was intended that these measures were to taken on the client side? Do you have proof that it was implemented on the client side. I have proof that the users clickstream ended up at Cliqz backend. What happened there is out of my knowledge and I don't care. If you respect my privacy you don't send the data that you claim you don't collect to your backend in the first place.
- gentleman11 5y ago
  Could you share the proof?
  - weinzierl 5y ago
    See this old thread: https://news.ycombinator.com/item?id=21677853 https://news.ycombinator.com/item?id=21677853 ...and no, I don't buy the "this ends up at servers we have no shared ownership with" someone wrote in the answers. As I said in other answers here, there are the client binaries out there (and I have them archived). Try them, dump the traffic. Maybe the backend servers don't exist anymore but I'm sure you can work around that.
    - jordemort 5y ago
      This is not quite the same as sending the whole clickstream, is it? Sending what you type into the URL off somewhere to autocomplete is what pretty much all browsers do out of the box, and it’s been the norm for many years. I’m not saying it’s a good norm, or that Cliqz is good, but this doesn’t seem to be an indicator of them being uniquely bad.
      - TedDoesntTalk 5y ago
        Clickstream data was not sent. He's probably referring to telemetry, all of which was sent to proxy servers run by FoxyProxy then forwarded to Cliqz servers (this removed ip addresses of the source).

13 ms·

Cliqz had a lot of docs at the time about ways to preserve privacy with client side systems that clearly took a lot of developer effort to research. Their reput

by gentleman11 5y ago

weinzierl 5y ago
Do you have a reference to documentation that shows that it was intended that these measures were to taken on the client side? Do you have proof that it was implemented on the client side. I have proof that the users clickstream ended up at Cliqz backend. What happened there is out of my knowledge and I don't care. If you respect my privacy you don't send the data that you claim you don't collect to your backend in the first place.
- gentleman11 5y ago
  Could you share the proof?
  - weinzierl 5y ago
    See this old thread: https://news.ycombinator.com/item?id=21677853 https://news.ycombinator.com/item?id=21677853 ...and no, I don't buy the "this ends up at servers we have no shared ownership with" someone wrote in the answers. As I said in other answers here, there are the client binaries out there (and I have them archived). Try them, dump the traffic. Maybe the backend servers don't exist anymore but I'm sure you can work around that.
    - jordemort 5y ago
      This is not quite the same as sending the whole clickstream, is it? Sending what you type into the URL off somewhere to autocomplete is what pretty much all browsers do out of the box, and it’s been the norm for many years. I’m not saying it’s a good norm, or that Cliqz is good, but this doesn’t seem to be an indicator of them being uniquely bad.
      - TedDoesntTalk 5y ago
        Clickstream data was not sent. He's probably referring to telemetry, all of which was sent to proxy servers run by FoxyProxy then forwarded to Cliqz servers (this removed ip addresses of the source).