On desktops browser displaying the fingerprint/hash requires clicks, on mobile is not implemented and on native apps practically not existing.

The keys should be shown, so they could be verified manually in person or via other channel. Just like the SSH do. Someone say people would just click "accept" without a thought, but the button is already here, just no information what actually is accepted.

Icon can really be a generic SVG taken from some CC stock website, if there is no time for anything else, would look much better. Getting rid of emoji vomit is one prompt away. I might do a PR if I find free five minutes.

https://github.com/etkecc/komai

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.

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.

All of IPv6 features are just direct effects of having more space and not. Basically IPv6 "features" is just getting rid of IPv4 workarounds.

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.

Translates to:

"We have to make sure citized accessing the public service have not control over the device per the eIDAS implementing acts"

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.

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.

So anyway it gives 128bits in total, 64 for network and 64 for node.

But I wish there was a better way to write just the local node part and global part being taken automatically.

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.

Even easier.

Called this out and the security team said noone complains, that there is no use case and they do not want to deal with security risks.

And the ossification continues.