nostr over reticulum initial draft

[basantagoswami]

NIP: https://github.com/nostr-protocol/nips/blob/9f97a8558b417c62577bf7c415f0de1fee298115/xx.md

Proof of concept: https://github.com/Unsigned-Labs/nostr-over-reticulum

Issues I haven't yet figured out:

• Is reticulum://<destination_hash> the proper way to handle this
• Should there be a different event kinds for adding your Reticulum based relays? TOR relays seem to be mixed with the standard relays, so we can probably leave it up to the clients to figure out

[fiatjaf]

Nostr over rectum.

[basantagoswami]

Nostrils up your rectum

[basantagoswami]

Closing this for now, because it is not ready yet, and I might have taken the wrong approach

• The Reticulum guys are more interested in creating their own protocol using the same cryptographic primitives already used in Reticulum. They created LXMF for example which is made for private data, and they would rather create something like nostr for public data as well. This is not a reason for us to not want to run nostr on Reticulum but still something to keep in mind

• They want to come up with a standard way of doing resource transfer. Once they do it, we can use it to send the JSON queries to the relays, and receive the events back. That would be better than coming up with our own way of doing things