A simple block diagram on how two instances of #nostr #safebox instances dynamically interact with one another. I have successfully de-coupled the interaction so that each user interacts with their https server only and all interactions are marshalled through relays. For example the QR that is scanned contains only the #nauth information required to create the channel - the npub, the relays to listen on etc. What is really cool is that I can have a #nostr #safebox running as localhost, behind a firewall, and it can communicate seamlessly with any other nostr safebox on the planet, automatically. Throw in WebSockets, I have full-duplex dynamic interaction channels intermediated via relays. For fun, I might add in real-time chat (but not to replace @White Noise ) Plus the added bonus - I decided to bite the bullet on integrating post-quantum algorithms, so no PQC-FUD. The next major lift is integrating Blossom blob support. I have mapped out the approach and plan to add the same PQC-resistant scheme for encrypting the blobs. Onward! image
The #nstrprise image
Note to self: Add this term to the ever-expanding bad #nostr neologisms: —- nstrprise (n): An organizational entity that uses the Nostr protocol as the basis for its digital capabilities.
Web of Correctness
In Meredith we trust. With GitHub we deploy. With Nostr we s***post.
I’m just going to call them machine-learning workers from now one.
Doing a docker build on a EU-based vps image
Your credit card is your id card.