Loving that lead paragraph.
If an app on one device connects to an app on another via Veilid, it shouldn’t be possible for either client to know the other’s IP address or location from that connectivity, which is good for privacy, for instance. The app makers can’t get that info, either.
Is that considered a new thing? I don’t think I’ve ever encountered a P2P service/protocol that also masks IP addresses.
They state they take inspiration from Tor and IPFS, so there are added transport layers below the top layer “P2P” that obfuscates ones IP address. It’s nothing new really, and I’m honestly not sure what the advantages are over something like I2P, which largely doesn’t suffer from Tor’s issues of node ownership as there are no guard or exit nodes to own (unless expressly configured), while also being faster overall.
Idk what it means because for networks to work you need an ip address to send the data to your device.
You right. There are still IP addresses; you can’t really just yank out layer3 and call it a day.
Here is a piece from their website about the “Secure envelopes”:
“Each node hop only knows about the next one This is similar to onion routing, but assumes that the source is fully in control of the Safety Route and the destination is fully in control of the Private Route.”
There’s also a packet diagram. It’s just encapsulation inception. There are also IP addresses listed as being encapsulated in the packets for additional node hops.
I guess from the perspective of the source and destination, they don’t know each other’s IPs. So there is that v0v.
