Great!
Unfortunately your call sign must get sent both ways. There is no legal way around this. Just like any broadcast.
You could always create a vanity npub for HAMSTR only or something as well
Only the server sees the npub, over the air it is compressed and split into packets, so while technically possible to sniff and decode, unless you knew it was a HAMSTR signal and had the proper encoding type, there is not really any way to get at the info. Possible? Absolutely. Likely? No.
Just to clarify: I understand that the transmission itself will need to have callsign associated (legally) so the Hamstr server will know it, but will the resulting Nostr post include the callsign?
And is there a band that you’re currently focusing on? Or is the idea to use multiple? Seems to me that in its infancy it may be a good idea to concentrate on one.
No. The call sign is used for the connection between client and server only.
The server would have no reason to include it on a nostr note.
The idea is like winlink. Many servers on multiple bands. Maybe a 40 and 80.
After I get vara hf and reticulum, I want to add in radio control features for the server and a selectable band for the client.
Something where the server will change the frequency, wait say 5 seconds, if no signal, go to the next one, and so forth.
Again, much like a winlink RMS gateway does. The frequencies will be different by server. Perhaps a database or live nostr note with server frequencies and locator identifications
