open water bitcoin
Nick
npub1jy2p...9p6d
Trying to recap the history of nostr proposals for onion routing to preserve network metadata privacy:
Are there any current onion routing proposals using NIP-17? CC @PABLOF7z and @Vitor Pamplona I believe I saw some rumbling from you guys in some deep comment threads.
2025.01 Vol.1 | YONSON
@Keychat any thoughts on this simple onion routing proposal for nostr as an extra privacy layer? Feel like it could be useful for low bandwidth, but extra sensitive messages. Or is something like this already baked in? 
GitHub
Publish by peers · Issue #411 · nostr-protocol/nips
TL;DR: problem: relays know the IP of clients and can track their private messaging activity solution: clients can use onion-routing like events to...
Has there been any consideration for #nostr relays to support some sort of compact filters like BIP157/158 style in order to preserve user privacy? Allow reading from a relay without disclosing exactly which events they are interested in.
Added a flake to my little liquidity management app if you are into that: 
GitHub
GitHub - nyonson/raiju: Your friendly bitcoin lightning network helper.
Your friendly bitcoin lightning network helper. Contribute to nyonson/raiju development by creating an account on GitHub.
Did a little deep dive on OP_RETURN, ordinals, and STAMPS:
2024.01 Vol.1 | YONSON
Why do a lot of nostr web clients in the wild register to the “web+nostr:” scheme instead of the nip-21 “nostr:”?