Doesn't Keychat use ecash 'blind signatures' stamps also? How's White Noise going to address spam on relays if only the group ID is known? Auth would reveal metadata and a different emphemeral key use used to sign each event? Blind signatures seem ideal here.

Yup, starting with "Untraceable Electronic Mail, Return Addresses, and Digital Pseudonyms" from 1981. Hughes, Finney and Cypherpunks were some of the first to implement.

This is one of the few books that has the history of Tor correct with origins beginning with Chaum mixnets, Cypherpunk remailers, Mixmaster, Free Haven... and NRL Onion Routing. NRL is sometimes cited as the origin. They built on previous ideas and expanded it to TCP/IP. Folks from Free Haven later joined and implemented it into Tor, combined with other prior research and development.

Great work! Looking forward, lots of opportunity.

Should be a good one!

So much more possible too with MLS!

Awesome! Reference to onion packages?

False positives could be problematic, there is always some probability. With matching 'what to send' (as with bitcoin) a false positive would just an event (tx) sent that shouldn't have been (easy to check and discard). With matching 'what not to send' a false positive would mean a missing event. Also, negentropy I think handles this case, bandwidth efficiency, already very well with set-reconciliation (NIP-77). Might not apply to the scenario you describe, however.

"It's not magic, it's just physiology." Looks pretty good.

Even though, I don't think outbox has been implemented yet in notedeck? Just a local relay to sync to, if I remember correctly.

This is pretty huge! Nostr + MLS w/ and on bitcoin++ Insider Edition. Full episode: https://youtube.com/watch?v=AuKJFZJrcuA

Great to see Bitcoin Stack Exchange listed in this weeks Optech. What have been other support paths?

Looks like Tidal Cycles https://tidalcycles.org/

We also used plugins for blockfilters, if I remember correctly.

I implemented this once in bitcoind, once with nodejs and another time in bcoin. The architecture in bcoin with plugins I think was the best and could run in a seperate asynchronous task (not part of consensus code), it could also be extended to index (or count) anything, types of scripts used, fees and other info.

Blossom but for git repos?

Glad to see the release naming tradition continues 😂

Kinda interesting. I bet using other HIDs (like AKAI drum pads...) would be really useful with that to control variables and effects...

Best wishes to you and your family during this time.

Yup! Spam, privacy and persistence! Spam: Web-of-trust can be a default with shared block/mute lists, this could possibly also help with email spam blocking! Micropayments (and proof of work challenges and LLM based filtering) for outside web-of-trust requests or comments: comments and messages can break through filters with some added cost (ecash and lightning). Privacy: Always have a private option, a way to privately follow and to privately publish to specific people, from direct messages or for many. Peristence: Store your own notes and other media with your own hardware and the notes of those you follow, and have bookmarked,, or otherwise interacted or zapped (possibly for access). Backup these notes via a hosting provider (ecash, lightning, gift cards/invitations or etc) or additional offsite hardware. Everyone is able to participate in The Wayback Machine. Some might offer search and indexing of what they store via a protocol.

Yeah, very possible, they have become quite complex. And so many of these new frameworks have ten-thousand and one dependencies and often not designed with security as a top priority.

With Gnome and KDE both going towards mobile AND Andriod going towards desktop with windowing and a taskbar, I think this might be the best way to go to develop cross-platform responsive networking apps. Especially considering this performance. 🤘🌞