nostr:nprofile1qqs9pk20ctv9srrg9vr354p03v0rrgsqkpggh2u45va77zz4mu5p6ccpzemhxue69uhk2er9dchxummnw3ezumrpdejz7qgkwaehxw309a5xjum59ehx7um5wghxcctwvshszrnhwden5te0dehhxtnvdakz7qrxnfk is bitchat using hardcoded relays? What to be precise? Are they the same in android and IOS version?
Login to reply
Replies (3)
nostr:nprofile1qqs9pk20ctv9srrg9vr354p03v0rrgsqkpggh2u45va77zz4mu5p6ccpzemhxue69uhk2er9dchxummnw3ezumrpdejz7qgkwaehxw309a5xjum59ehx7um5wghxcctwvshszrnhwden5te0dehhxtnvdakz7qrxnfk ok, found it reading the codebase. What could be the best way to do discoverability for geohash chats without hardcoding servers? Geohash based state-syncing across relays, discoverability trought dht-like nodes? Just vibin...
Since CDNs are not really a thing in nostr, you could just do geolocation on the IP of the relay.
but clients should know ip of relays. How can the network be resilient to some nodes being took off without manually retype new address or domain name? Maybe a p2p (mesh bluetooth and dht-like peer discoverability) to exchange infos about what and wher are relays and where to ping.