this post was submitted on 23 Apr 2024
1062 points (97.1% liked)

Memes

45674 readers
901 users here now

Rules:

  1. Be civil and nice.
  2. Try not to excessively repost, as a rule of thumb, wait at least 2 months to do it if you have to.

founded 5 years ago
MODERATORS
gary_host_laptop@lemmy.ml
sexy_peach@feddit.de
cyclohexane@lemmy.ml
cypherpunks@lemmy.ml
1062
Cough Cough... Chrome... Chough... (slrpnk.net)
submitted 6 months ago by Sunny@slrpnk.net to c/memes@lemmy.ml
151 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[โ€“] magic_lobster_party@kbin.run 18 points 6 months ago (1 children)

They need the IP address to know where to forward the packet to. Hard to avoid that without VPN or TOR.

[โ€“] JDubbleu@programming.dev 2 points 6 months ago

There was a demo for a technology put out recently that circumvents this. I don't remember the exact mechanisms, but it obscured DNS such that your ISP couldn't see the DNS record you requested, and then used a proxy to route traffic before it hit the final endpoint eliminating exposing the IP to your ISP. It worked very similar to a VPN, but without the encrypted connection, and had some speed focused optimizations including the proxy being proximate to your ISP. It was pretty interesting.