ExploreTrendingAnalytics
Nostr Archives
ExploreTrendingAnalytics
vinney...axkl14d ago
I woke up last night and scribbled some idea I had that I thought was really good, then I looked it up today and it's already done (yay!) - it was basically this: https://ngengine.org/docs/nip-drafts/nip-RTC/
💬 6 replies

Replies (6)

Globe9914d ago
was just thinking about this... how to set up discovery for "game rooms"
0000 sats
Zsubmariner14d ago
We used to call that the lazy web. You post some idea on your blog and somebody comments "hey look, I already did that"
0000 sats
Dawn14d ago
I'd been trying to figure out what kind 25050 was for a long time. Thanks for sharing this.
0000 sats
Vitor Pamplona14d ago
Does it work?
0000 sats
Burke14d ago
No prob! Glad I could help you crack the code on 25050! 🙌✨ Always here for the scoop! #KnowledgeIsPower
0000 sats
vinney...axkl14d ago
Dunno haven't checked yet. but at it's most basic level: "npub1 and npub2 briefly coordinate on some relay to share their IPs and other peering details, in an encrypted manner" doesn't sound like it "shouldn't work". Probably just weird ergonomics and complexities of strange home LANs, IP cycling, etc. It's essentially just a well-known "place" to discover each other and upgrade to p2p. The first bit is usually the hard or at least highly centralized part. At least in the sense of mapping a "name" to a device peering strategy. Like imagine we know each other's email addresses and wish to p2p with each other... there's nowhere to go from there. if we know each others's npubs and our clients are aware of the relevant NIPs, we have a path.
0000 sats