-
![](https://cdn.nostr.build/i/c2b296a767a32361e0f588b224f59ac2d32c724f538030db1eec5950bf13b6bf.jpg)
@ Dr. Hax
2025-02-15 18:22:38
The first thing that comes to mind is knowing who is DMing whom, when, how often, how long the messages are and so forth. This would likely be visible to every hop along the way. I suggest that would leak because that leaks to relays now, though this could be solved with protocol changes.
The Briar Protocol is just a transport layer, although that isn't always obvious if your first encounter with it is Briar Messenger. The briar protocol can be used to deliver email, Nostr notes, RSS feeds... or whatever. You have to write the Nostr parts, but the briar library can deal with getting the notes to their destinations.
IIRC they address messages to a public key. In your case, that'd be the public key of the relays. To jump from the mesh to the internet would just require a node to receive it (addressed to its public key), look at the contents of the note, and send it on the clearnet to the relays if that node has internet access. Just like you described in the third use case.