> This is not it, this is an open source app that you can run anywhere
The service for EU age verification app requires Google Play Integrity API check. So as much as you "can" run the app itself anywhere, you are forced to do it on whitelisted build of an OS on a whitelisted device.
IPv4 has exact same problem, the NAT is working here because devices does not actually have proper Internet connection, all connections are terminated on NAT and reassembled after.
Actual solution could be extending TCP and UDP or make a new transport layer procotol that handles changing addresses, similar to what QUIC do. But we cannot do it exactly because things like NATs existing, thus QUIC build was build on ossificated UDP.
Imagine if instead of IP+port a connection use unique per-connection hash to persist IP addreses changing. No more trying fighting to keep the IP the same.
Ipv4 does NOT have this problem. The typical setup is always NAT for ipv4 lan, so external address can be changed with minimal disruption.
All ipv4 apps that require hole punching assume they will need to "discover" the external address anyways, for every new p2p connection.
In contrast to the vast majority of ipv6 apps which assume their ipv6 address is identical to external ipv6 address, as this is(was) the main marketing point of ipv6 - directly addressable end points.
> Easy way to explain the absurdity of the idea is to picture how could a law be made restricting 2D printers from printing schematics of guns.
>
> How the printer could detect it, where the censoring circuit or program would live, how effective it would be and what it means long-term.
Maybe instead of stopping you the printer could add some small almost invisible dots in a pattern to identify which printer printed the schematic.
You have three devices at home, A, B and C.
Only device A have Internet connection and can connect to public Yggdrasil node. B can connect only to A and C. C can connect only to B.
Have Yggdrasil installed on all of them (and tell Yggdrasil about the peers), all devices would have access to full Yggdrasil network.
And? How is that novel? I read the site as saying the have a new, and better solution to how to do internet scale routing (in an overlay network, but that did not seem like a critical aspect)
How could we determine which device on mobile network is a faceless cellphone and which is a proper device needing real sweet Internet connection? And won't that make things more complicated than just v6 deployment?
Can argue that NAT, which interrupt layers ment for end device do basically the same as popular user hostinle unchangable mobile OSes, but I don't think latter is good either.
Highly disagree. Middleboxes are a huge problem on global scale and have frozen any innovation below application layer. TCP and UDP even that they are on software not hardware layer cannot be updated or changed, see MPTCP efforts or QUIC giving up and building on top of UDP.
If this is so much privacy problem, IPv6 is there for many years reaching 50%+ deployments in some countries, I bet there should be concrete examples of such breaches and papers written.
> Reaching your own stuff is already a solved problem, too. Tailscale/Headscale
No address to receive communication - no problem install an app that would proxy it through someone who has the address.
Tailscale/Headscale is great, using it daily, but they are not solution to the huge already build global network created to connect devices not connecting devices because lack of digits. Global is key here.
The service for EU age verification app requires Google Play Integrity API check. So as much as you "can" run the app itself anywhere, you are forced to do it on whitelisted build of an OS on a whitelisted device.
reply