I've thought a bit more, and radio based store and forward nostr could involve a combination of relay and botted client to repist what comes in.
The tricky part is how to handle those reposts, because if it's from one npub, more than a handful of relay users would make it unwieldy to follow what you want.
I'm curious as to whether you think something like an nsec bunker or amber could be used to permit the bot to sign and send what the relay receives in a manner that'd work in the limited bandwidth environment.
The vision here being tha ability to relay notes globally without touching the Internet, but maintaining the cryptographic integrity lf Nostr.
I guess where things really get hairy is when you go to relay things a second time and there's no way to tell Amber or your bunker to allow signing.
Replies (3)
Or there's always the option to get way less complicated and basically rsync between the relays. the notes are already signed...
Once a note is signed on the client, it is just json. You can send and forward as many times as needed to get to a relay as long as the signed json is identical bytes and intact.
I guess the question there is HOW that forwarding is done. But that may be where my understanding of Nostr is a bit suboptimal -- that may be as simple as just boosting it without needing to faff about with signing. Otherwise, it seems like it'd be a propagation that's done from relay to relay without going through a normal client connection, which is where things get a bit odd. The goal of course being to allow people following the person posting the note to see it, and also not to have one npub belonging to the relay that is just a mostly unsorted pile of relayed content which is harder to selectively follow.
