In any case what is an unhinged rant going to accomplish.
If you are looking for a Chrome conspiracy though...
Google forced the industry to rubber stamp their HTTP/2.0 protocol and along with that the TCP connection to google-analytics is kept open longer than 30 minutes whereas it was under 6 minutes previously in HTTP/1.1. This TCP connection is itself, because of how the internet works, a unique identifier for your browsing session. Before this they changed Chrome so that all domains reuse the same TCP connection for google-analytics.
Google also made it so that the only way to drag links and not open new tabs in Chromiums is to drop it in a tiny space over the current tab in the tabs list... sometimes a 50x10 pixel area or smaller. It's basically impossible to have one window open that you read, and another that you drag links to just glance at to see what they are without opening lots and lots of tabs.
Well, if any one of the tabs has google-analytics and refreshes or fetches anything then it keeps your tracking connection to google-analytics open for another 30 minutes. More tabs, more chance to keep the tracker from timing out. And they've engineered the UI to make it hard to not create new tabs.
I don't see how these things taken together could be anything other than a deliberate attempt to create a tracker, stealthily embedded into the protocol itself.
The TCP connection has to be a unique identifier -- that's how the packets get to your computer instead of a different one. The identifier is (local IP, local port, remote IP, remote port). See wikipedia TCP. The only way it doesn't uniquely identify a browsing session is if you connect through a proxy.
To read about how Google forced the industry to rubber stamp HTTP/2 search for "Poul-Henning Kamp" the main guy opposed to accepting it as-is (also a computer science wizard, even 2004-era Google would be a step down for him), ietf-http-wg, SPDY (Google's internal name for HTTP/2). I don't know there's a particular summary of how it went down.
The connection to google-analytics being left open for half an hour you can test yourself with Wireshark. I last tested it a few years ago in Chrome so possibly Chromium or Brave protects you by not keeping it open. There was a bug report on chromium or bugzilla where Google said they did this on purpose for "performance", but I can't find it. I may have been censored.
This was likely a html based crypto miner on a webpage you visited.... They've become a popular way of mining
In any case what is an unhinged rant going to accomplish.
If you are looking for a Chrome conspiracy though...
Google forced the industry to rubber stamp their HTTP/2.0 protocol and along with that the TCP connection to google-analytics is kept open longer than 30 minutes whereas it was under 6 minutes previously in HTTP/1.1. This TCP connection is itself, because of how the internet works, a unique identifier for your browsing session. Before this they changed Chrome so that all domains reuse the same TCP connection for google-analytics.
Google also made it so that the only way to drag links and not open new tabs in Chromiums is to drop it in a tiny space over the current tab in the tabs list... sometimes a 50x10 pixel area or smaller. It's basically impossible to have one window open that you read, and another that you drag links to just glance at to see what they are without opening lots and lots of tabs.
Well, if any one of the tabs has google-analytics and refreshes or fetches anything then it keeps your tracking connection to google-analytics open for another 30 minutes. More tabs, more chance to keep the tracker from timing out. And they've engineered the UI to make it hard to not create new tabs.
I don't see how these things taken together could be anything other than a deliberate attempt to create a tracker, stealthily embedded into the protocol itself.
Know where I can read more about this?
The TCP connection has to be a unique identifier -- that's how the packets get to your computer instead of a different one. The identifier is (local IP, local port, remote IP, remote port). See wikipedia TCP. The only way it doesn't uniquely identify a browsing session is if you connect through a proxy.
To read about how Google forced the industry to rubber stamp HTTP/2 search for "Poul-Henning Kamp" the main guy opposed to accepting it as-is (also a computer science wizard, even 2004-era Google would be a step down for him), ietf-http-wg, SPDY (Google's internal name for HTTP/2). I don't know there's a particular summary of how it went down.
The connection to google-analytics being left open for half an hour you can test yourself with Wireshark. I last tested it a few years ago in Chrome so possibly Chromium or Brave protects you by not keeping it open. There was a bug report on chromium or bugzilla where Google said they did this on purpose for "performance", but I can't find it. I may have been censored.