FoxByte on Nostr: I'm toying with the idea of building a nostr based amateur radio logging client. I ...
I'm toying with the idea of building a nostr based amateur radio logging client. I love the idea of having QSOs public and decentralized, and I wonder if this could be used to synchronize all the centralized logging platforms (LOTW, clublog, hrdlog, etc etc). Would be cool to build in some sort of confirmation system, where if two QSOs match, they are both marked as confirmed. Might need to figure out a way to link public keys with callsigns, and need to also consider callsigns can be prefixed or suffixed depending on certain situations hams operate in (operating in a foreign country) or they could utilize a club callsign.
#hamradio
#nostr
#software
#amateurradio
#ham
Published at
2024-12-29 20:55:19Event JSON
{
"id": "cf4a931a1bc2b86bc1bcf9dd7bdd5f518c930ef9bd04718d024390ef10b4bb67",
"pubkey": "3e089f671add484b2e9172a4f813dc772b02fe84bf42e5480325aeb1cdd6b008",
"created_at": 1735505719,
"kind": 1,
"tags": [
[
"t",
"hamradio"
],
[
"t",
"nostr"
],
[
"t",
"software"
],
[
"t",
"amateurradio"
],
[
"t",
"ham"
]
],
"content": "I'm toying with the idea of building a nostr based amateur radio logging client. I love the idea of having QSOs public and decentralized, and I wonder if this could be used to synchronize all the centralized logging platforms (LOTW, clublog, hrdlog, etc etc). Would be cool to build in some sort of confirmation system, where if two QSOs match, they are both marked as confirmed. Might need to figure out a way to link public keys with callsigns, and need to also consider callsigns can be prefixed or suffixed depending on certain situations hams operate in (operating in a foreign country) or they could utilize a club callsign.\n\n#hamradio\n#nostr\n#software\n#amateurradio\n#ham",
"sig": "3e4b3159b01ebb1a8584d0f269c8eb8638638008c3f37d8d7b53faa187bb0540471207b05fc583cbc6fa371db5c7ea4e08aa6413c095b19b233079d2920a90ce"
}
