Earlier quoted context omitted.
It's a shame you're getting downvoted because you are correct. The dramatic acceleration of TLS adoption means that your ISP is getting less and less info about their customers' behaviors. But if your browser has ever logged into something like Facebook or Google, then any site with embedded content will be sending info about your behavior back to them. A LOT of sites carry pixels from those companies, but anything c…
He's not correct which is why he's being downvoted. As TLS rolls out further I suspect you'll see more ISPs move from firewall/router devices being deployed with their service to an edge proxy under the guise of additional security, "our new routers terminate all connections before they reach your computer directly allowing us to block malware and other dangerous packets" -- while that statement is 100% true what it…
Telco lobbyists accidentally send their talking points
21–28 of 28 posts
Re: Telco lobbyists accidentally send their talking points
#22Earlier quoted context omitted.
It's worth nothing that the vast majority of Americans have their internet setup as defaulted. So, every DNS request goes to the ISP's DNS servers (your ISP knows every single domain you visit regardless of association with Google/Facebook) and every domain name that doesn't exist winds up at the ISPs own search/not found landing page. Plus if you use your ISP's email server (like my mom) who knows if they're reading…
For some stats behind this, the most recent estimate of websites with Google Analytics is around 40 million (1). A rough estimate of the number of websites would be around 1.5 billion (2). 1. https://trends.builtwith.com/analytics/Google-Analytics 2. https://news.netcraft.com/archives/2018/06/13/june-2018-web-...
The fact that "Uncle Joe's Fishing Blog" with a total of 5 hits that weren't crawlers or Uncle Joe doesn't include GA, doesn't really mean much in the context of this discussion. The vast majority of traffic on the web goes to a very small portion of those 1.5B sites.
Re: Telco lobbyists accidentally send their talking points
#23Earlier quoted context omitted.
Masnick has a pretty severe critic of both Google and Facebook for years and it would be pretty difficult to bend his words here to try to support your claim.
Do you think an internet lobbyist would be so brazen to attempt to redirect onto Google & Facebook a discussion thread talking about the way the telcos want to redirect discourse to place blame on Google and Facebook?
Re: Telco lobbyists accidentally send their talking points
#24Earlier quoted context omitted.
He's not correct which is why he's being downvoted. As TLS rolls out further I suspect you'll see more ISPs move from firewall/router devices being deployed with their service to an edge proxy under the guise of additional security, "our new routers terminate all connections before they reach your computer directly allowing us to block malware and other dangerous packets" -- while that statement is 100% true what it…
Which browsers are going to trust an ISP signing cert?
With a notice informing you if you refuse you won't get the malware blocking and scanning services to protect you. Depending on the laws the ISP may require you to accept the certificate in order to pass TLS traffic.
Re: Telco lobbyists accidentally send their talking points
#25Earlier quoted context omitted.
It's a shame you're getting downvoted because you are correct. The dramatic acceleration of TLS adoption means that your ISP is getting less and less info about their customers' behaviors. But if your browser has ever logged into something like Facebook or Google, then any site with embedded content will be sending info about your behavior back to them. A LOT of sites carry pixels from those companies, but anything c…
He's not correct which is why he's being downvoted. As TLS rolls out further I suspect you'll see more ISPs move from firewall/router devices being deployed with their service to an edge proxy under the guise of additional security, "our new routers terminate all connections before they reach your computer directly allowing us to block malware and other dangerous packets" -- while that statement is 100% true what it…
Re: Telco lobbyists accidentally send their talking points
#26Earlier quoted context omitted.
For some stats behind this, the most recent estimate of websites with Google Analytics is around 40 million (1). A rough estimate of the number of websites would be around 1.5 billion (2). 1. https://trends.builtwith.com/analytics/Google-Analytics 2. https://news.netcraft.com/archives/2018/06/13/june-2018-web-...
Not sure if you're trying to be intentionally misleading to "win" an argument here, but look at the stats for the top 1M, 100k, and 10k sites if you want to be honest about the portion of actual web traffic Google is able to capture detailed data on. The fact that "Uncle Joe's Fishing Blog" with a total of 5 hits that weren't crawlers or Uncle Joe doesn't include GA, doesn't really mean much in the context of this di…
Re: Telco lobbyists accidentally send their talking points
#27Earlier quoted context omitted.
Then again, with Chrome, there is at least the technical possibility of Google tracking every single website you visit just as well (including http, https and now even sites that just sit on your LAN and don't hit the ISP at all) I don't say they do, but my trust in Google not to do this isn't that much higher than ISP s not doing this. (Though, to be fair, code doing this would probably be found rather quickly in th…
Well they do, in point of fact. I was debugging our corporate proxy and tailing the logs for a particular site- when using chrome I matched the site string despite it being directed to bypass proxy- but not going to the site, but to google, despite putting a full url in. Anyone wanting to truly understand what chrome is doing should run an ssl decrypting proxy on their web traffic for awhile- it is eye opening.
Re: Telco lobbyists accidentally send their talking points
#28Earlier quoted context omitted.
Well they do, in point of fact. I was debugging our corporate proxy and tailing the logs for a particular site- when using chrome I matched the site string despite it being directed to bypass proxy- but not going to the site, but to google, despite putting a full url in. Anyone wanting to truly understand what chrome is doing should run an ssl decrypting proxy on their web traffic for awhile- it is eye opening.
Perhaps more interesting is that Chrome is happy to send data to google.com without checking the certificate. I'd file a bug.
Firefox on the other hand, you have to import the whole CA chain into the app itself for it to work transparently, since it won't reference the OS cert store.