zlacker

[parent] [thread] 4 comments
1. rvnx+(OP)[view] [source] 2019-10-04 07:36:05
+1 @cnst, what privacy concerns are you all afraid of with ECS ? archive.is will get informed that someone around IP range A.B.x.x tries to reach its website, just a few seconds later to see a connection from A.B.C.D.

The main reason that Cloudflare wouldn't share this info is to prevent competitors like Akamai to operate a CDN as good as them. It looks more like sabotaging competition than increasing privacy.

replies(2): >>FDSGSG+y >>cnst+N1
2. FDSGSG+y[view] [source] 2019-10-04 07:43:37
>>rvnx+(OP)
In practice this is one of the most common techniques used to deanonymize proxy users.
replies(1): >>cnst+42
3. cnst+N1[view] [source] 2019-10-04 07:59:41
>>rvnx+(OP)
> The main reason that Cloudflare wouldn't share this info is to prevent competitors like Akamai to operate a CDN as good as them. It looks more like sabotaging competition than increasing privacy.

Exactly. Their own answers in the threads over here at HN are basically admitting as much — they claim to be working on solutions alternative to ECS, because Google and some others have more PoPs than Cloudflare does. They're obviously using this as a competitive advantage to slow down competing CDNs. And noone's talking about!

◧◩
4. cnst+42[view] [source] [discussion] 2019-10-04 08:03:18
>>FDSGSG+y
How? If your client is leaking DNS outside of the confines of the proxy you're using, you've got bigger problems than ECS.
replies(1): >>FDSGSG+mL2
◧◩◪
5. FDSGSG+mL2[view] [source] [discussion] 2019-10-05 15:59:21
>>cnst+42
I don't disagree about DNS leaks being a separate problem, that doesn't change anything about what I said though.
[go to top]