7 comments

[ 3.4 ms ] story [ 26.2 ms ] thread
Yay clickbait.

Sure HTTPS might not be sufficient, but a VPN can.

Did you read the article? It's actually well put together. The ability to identify what's being browsed by the path taken through the network is pretty interesting.
(comment deleted)
This is a nice explanation of the limitations of HTTPS in regard to privacy. Most people do not understand the specific implications of S. J. Resolution 34.
You seem to have missed the news that the privacy exposure you fear from the Obama regulation change being removed is already happening and has been since 2015. The Obama administration kept that privacy hole open and didn't submit a privacy regulation until three months ago, and it wouldn't take effect until next December at the earliest anyway.

Indeed, most people do not understand the reality of the subject at all.

I've definitely been ignoring that point. Thanks for the reminder.

The real issue is that this will be much more difficult to replace after being removed from the FTC and the FCC.

The technique is very interesting. Would it be enough for websites like youtube to add a small, random amount of unnecessary data every time a resource gets accessed to prevent such analyses?