Ahh. I thought it was essentially a single relay that was accessible via radio and internet, but sort of limited there (which is very cool in itself, but not quite as extensible as being able to relay traffic to and from other relays.
Once I'm licensed (and more importantly, have equipment -- the licensing is cheap; the equipment less so!) I definitely intend to play with it a bit!
Login to reply
Replies (2)
I don't understand what you mean by relay traffic to and from relays?
That not really how nostr works. Relays are just stored data, nothing more. HAMSTR is not a relay, rather it connects to any relay you wish and published/gets notes from. There are some default relays, but totally configurable and changeable.
Yea, I've not been the best at explaining myself. I was sort of envisioning something that did what Hamstr does with being a gateway to existing, Internet native relays, but ALSO serves as a relay itself, so that in the event of an internet outage, Nostr functionality is maintained over radio (albeit only as a single relay). And you're right, while Nostr relays don't store and forward, I guess I was imagining something that could perhaps be termed a "caching gateway relay" -- something that serves as a relay itself, and also will route requests to other relays, and then cache those responses, in a bid to be a bit more anti-fragile (and maintain as much functionality as possible in an Internet outage).
It'd be less store and forward, and more get and store (and relay upon request).
Definitely don't have it all straight in my head, just sort of playing with a marriage of nostr like functionality with the sort of nntp/fidonet style store and forward networks of BBS's to provide something that feels a little less out of date.