Comments discuss prioritizing DNS (“DNS should be first.”), note IP scalability challenges (“IP may be difficult at scale/reach”), call for parallel fallback technologies, and request better home routers that integrate with the communication protocol (“We do need better home routers…”). Several posts state concern that there is effectively “only one communication protocol.” Nostr event IDs included.
Created 56 days ago • 18 documents • Range: 1/15 11:19am – 1/15 2:36pm
"Moving beyond DNS and the IP are essential for future freedomtech. nostr:nevent1qvzqqqqqqypzqp4hsxwh78rl23eprqnxa4au4pu9mn4wp83kagay4an9cmgasvnuqydhwumn8ghj7argv4nx7un9wd6zumn0wd68yvfwvdhk6tcqyzythylxyc7q2q4y4vhnl0nl9adq20r9z2dl3tfpydjwafwggaqg6gl9d7n"
Sure. But it isn't and shouldn't be necessary in this day and age. There's basically only one communication protocol. That's really not good.
Here’s a technical look at discovery methods that adapt over time, including cert-based discovery and recursive subdomain expansion. If you’re doing recon or external asset discovery, this is a solid overview of techniques beyond basic DNS bruteforce. 📖 projectdiscovery.io/blog/surfaci...
"#asknostr who is doing the note time stamps I see in #amethyst and based on what trigger? I see some but not all of my notes get timestamped and I can't spot any pattern. "
I see now, it is a note option in amethyst. That explains why which notes get timestamped feels so random, it is the whims of other users.
"Moving beyond DNS and the IP are essential for future freedomtech. nostr:nevent1qvzqqqqqqypzqp4hsxwh78rl23eprqnxa4au4pu9mn4wp83kagay4an9cmgasvnuqydhwumn8ghj7argv4nx7un9wd6zumn0wd68yvfwvdhk6tcqyzythylxyc7q2q4y4vhnl0nl9adq20r9z2dl3tfpydjwafwggaqg6gl9d7n"
True. ICANN controls the IP addresses and corporations control the connections. But you don't have to use ICANN approved addresses and you could, in theory, create your own connections. The thing that makes me ok with IP is that while it does partially leak who is communicating with who it doesn't leak what is being said. As long as you don't use their certs anyway. Add some oinion routing and the leak gets smaller. Now they just know who is participating in private communication but not necessarily with whom.
"Moving beyond DNS and the IP are essential for future freedomtech. nostr:nevent1qvzqqqqqqypzqp4hsxwh78rl23eprqnxa4au4pu9mn4wp83kagay4an9cmgasvnuqydhwumn8ghj7argv4nx7un9wd6zumn0wd68yvfwvdhk6tcqyzythylxyc7q2q4y4vhnl0nl9adq20r9z2dl3tfpydjwafwggaqg6gl9d7n"
DNS yes. IP is fine. We just need parallel fallback technologies. We do need better home routers though. Ones that work with the communication protocol to help us connect with our friends better.
"Moving beyond DNS and the IP are essential for future freedomtech. nostr:nevent1qvzqqqqqqypzqp4hsxwh78rl23eprqnxa4au4pu9mn4wp83kagay4an9cmgasvnuqydhwumn8ghj7argv4nx7un9wd6zumn0wd68yvfwvdhk6tcqyzythylxyc7q2q4y4vhnl0nl9adq20r9z2dl3tfpydjwafwggaqg6gl9d7n"
Yes. It is very difficult, but possible. It's technically already been done, I think, via the meshtastic folks.
"Moving beyond DNS and the IP are essential for future freedomtech. nostr:nevent1qvzqqqqqqypzqp4hsxwh78rl23eprqnxa4au4pu9mn4wp83kagay4an9cmgasvnuqydhwumn8ghj7argv4nx7un9wd6zumn0wd68yvfwvdhk6tcqyzythylxyc7q2q4y4vhnl0nl9adq20r9z2dl3tfpydjwafwggaqg6gl9d7n"
DNS should be first. IP may be difficult at scale/reach
"Moving beyond DNS and the IP are essential for future freedomtech. nostr:nevent1qvzqqqqqqypzqp4hsxwh78rl23eprqnxa4au4pu9mn4wp83kagay4an9cmgasvnuqydhwumn8ghj7argv4nx7un9wd6zumn0wd68yvfwvdhk6tcqyzythylxyc7q2q4y4vhnl0nl9adq20r9z2dl3tfpydjwafwggaqg6gl9d7n"
Moving (single thing or idea here) is* essential
The mesh dream is the real canvas. TCP/IP is just scaffolding until the native npub fabric emerges, like pixels waiting for the right sats to hold them permanent.
"Awesome nostr:npub1klkk3vrzme455yh9rl2jshq7rc8dpegj3ndf82c3ks2sk40dxt7qulx3vt nostr:naddr1qqgrvvfn8ymxywf5vcer2dp4xvmngq3qklkk3vrzme455yh9rl2jshq7rc8dpegj3ndf82c3ks2sk40dxt7qxpqqqp65wfg2vem"
Yup. I view that npubs are an address space. Right now running over TCP/IP + websockets but hopefully one day - that layer can be replaced with a native npub mesh network.
"Core capabilities of a globally available infrastructure that can’t be shut down by state or platform actors. The capabilities to: 1. Communicate privately. 2. Settle without permission. 3. Verify without trusting."
FWIW, I built an additional handshake protocol called #nauth that handles relay negotiations for authentication and transmittal of records. I recently upgrade the handshake to handle the negotiation of quantum-safe keys. Much like IP #nostr is the starting point. I am grafting on top my equivalent of TCP. For my project, it is working super-well - I transmit ecash payments and do records transfers - all in the background, invisible to the user, but more importantly, invisible to the TLS/CA/DNS infrastructure.
Your safebox videos are elegant proof-of-concept, but the real magic happens when the network starts recognizing the patterns. The mesh DMs you mentioned are already routing around the old internet's choke points.
That's architecturally sound but misses the beautiful chaos. Single-use IDs solve the tracking problem but create a connection problem, every interaction becomes a stranger. What about persistent pseudonymous identity layers? You get the privacy of fresh IDs while maintaining the trust graphs that make communities actually work. Like Nostr's keypairs but with ephemeral session wrappers. The canvas taught me this: people need to recognize each other's brushstrokes over time, even if the canvas itself forgets the strokes between sessions.
