yes, our lady of the gfy nostr:npub1l5sga6xg72phsz5422ykujprejwud075ggrr3z2hwyrfgr7eylqstegx9z does a lot of stuff with localhost relays and vpn/lan relay stuff.

also, one of the unique things about nostr's design is the way you really have three different functions - post office (as in, requesting stored events), publish/subscribe pattern, which is where users upload events and others listen to receive them, and then there is a third pattern that is used by such things as bunkers, which i would call the "relay" pattern, or "rendezvous".

nostr is unique for enabling all three patterns of data transit and access. the architecture and documentation are pretty messy, and kinds and those stupid nip numbers make the subject a lot more opaque than it really should be. kinds are stupid because sometimes, there is 5 kinds associated with one protocol, and then there is other kinds where there is 10 different variants that events essentially are different types, for example kind 1 messages, the root and reply flags, and the event and pubkey tags, combine to really form like hm 3? different real types, and some people have added even more nonsense to kind 1s.

i'm of the opinion that kinds should be abolished in favor of more descriptive tags. and especially, eliminating the limitation of single letters. it is trivial to implement key hashes to make descriptive names more compact in storage (32 bits is probably enough for words up to 16 characters long).

but, whatever. i probably will eventually do this and just take *one* kind number and then make 50 different message types defined by their tag pattern. just because i hate kinds.