Kazik24

I've been using iroh for a while now for personal projects. I wrote an utility for sharing locally running services with others: https://github.com/Kazik24/server_share Glad I can finally update to 1.0. It's a great library.

Excuse me if this is explained somewhere, but how does noq/iroh relays QUIC packets between peers? How does relay know which QUIC packets it receives should be sent where, since QUIC is famously hard to track? Do you stream to relay new/retire_connection_id packets through different connection so that it can link them to specific peers? Or is the relayed QUIC wrapped in different protocol?

Do you see porn on every website right now, since we don't have widespread verification yet? The internet was designed for adults from the start, only in recent years we got a significant portion of kids on it.

The thing is that if you are a kid, your device would be bought and signed by your parent, you have no way of refusing to show ID cause device does it automatically. Of course there is a problem that children could use parent's phone but that's also a way to circumvent current age verification propositions.

The idea is just to sign device once for a kid and let them use it without constant worry.

Shouldn't the verification be other way around? That is, you need to prove that you are a child. Then the site can present you more strictly filtered content. Parent can sign child's device on first boot, token stored in TPM so that it's hard to remove.

It's basically the same type of enforcement on sites, as they need to verify and filter content for children, or just block them. Most of the internet users are adults, why not make internet for adults by default.

There is DNS over QUIC, and in case your current Connection ID or IP is blocked during the connection, QUIC can use multiple IPs and CIDs for single connection, and CIDs are negotiated in encrypted part of packet. It's a mechanism for migrating connection over changing networks. Servers can also take advantage of that.

Server could have multiple QUIC output nodes to migrate connection in case one of them is blocked. The output node network can be shared by many servers and DoQ endpoints so blocking it entirely would scare government.

This solution still needs to connect to some known IP in order to establish connection first. And the same goes for DoQ. To mitigate this we can use Encrypted Client Hello as other commenter mentioned and connect to a pool instead of single IP.

Applications based on QUIC and/or P2P might be an option. QUIC is designed to not be as easy to filter as TCP + TLS. But then right now it can be blocked by just blocking UDP. But if majority of the internet would use QUIC then blocking UDP would mean blocking most of the internet so the governments wouldn't be so eager do nationwide firewalls (hopefully).

I think it's a matter of perspective. Creativity as an ability to create something new will always be relevant. At the core concept, creative ideas are just ideas, and something needs to translate them into the real world. Right now we are learning skills to do this. In the future, AI could do it for us.

In that case, there is an information bottleneck. If you, as a single entity, have an idea and skills needed to translate it, then internal communication in your brain is very fast. But when we as a creator have an idea and describe it to AI (or even other humans), there is some very lossy compression going on.

Creative jobs in 10 years will probably shift to focus more on being able to communicate those ideas well to "execution units" and back, so the skill to learn would be mapping some internal "mindset" of an AI to predict outcomes.