Freedom hardware would be a good follow-up, but it won't be enough. The last frontier to free is the human mind
Discussion
Need a secure medium to interact. That is my hope with Nostr Wallet Connect evolving into a full-blown protocol.
Relay and asymmetric encryption should do the work 🤙 in the other hand you mean RPC over nostr? Is what nwc and contextvm do
I need to learn more about contextvm I knew there were similar ideas with dvms
Yes, you can implement any functionality using a CVM, just as you could with a DVM. However, the issue with DVMs is that their specification is somewhat unclear. Additionally, there are different approaches to their implementation. DVMs segregate jobs by type, using one kind for a specific job type (e.g., transitions), another kind for a different job type (e.g., algo feeds), and yet another kind for responses, which is typically the job type kind plus 1000. In contrast, a CVM uses a single kind, making it agnostic to the job type. This allows it to implement any functionality without worrying about which kind to choose. Furthermore, a CVM uses this single kind as a bidirectional socket, eliminating the need for a separate kind for responses. This design enhances privacy significantly.
The big insight that I had was that NWC is very similar to the message queue architectures from about 20 years ago, before the web (https/rest) took over everything.
Now we can go back to a publish and subscribe model using relay pools instead of the request and response apis. The properties of the nostr protocol is that it’s possible to go global immediately instead of being limited to an enterprise context.
Totally, that's how cvm its implemented and specified, it uses nostr as a transport, auth, and discovery layer. It publishes and listens subscriptions. Using relays as kind of hole punch mechanism you can run anything and make it instantly available reachable. I'm curious for that old message queue approach you are mentioning, it's documented anywhere?
RabbitMQ is an open source version. Message Queue Architecture was the hottest thing 20-30 years ago in government. That’s what Estonia implemented (still using), but it all got captured by proprietary vendors that made it stinking expensive and restrictive. I am still trying to remember that name of the vendor that captured it all (still trying). Eventually the dotcom craze made it uncool.
Over the longer run, there were open source versions like RabbitMQ - successful- but now I see NWC blowing the doors wide open on the architecture.
There is also this article form nostr:nprofile1qqsd5x8fscqypualfyu8dlqkkx539tj6dah634g4ns779wpr8gxes5gpremhxue69uhkummnw3ez6ur4vgh8wetvd3hhyer9wghxuet59uq3vamnwvaz7tmzv4mx7tnwdaehgu339e3k7mf0qyghwumn8ghj7mn0wd68ytnhd9hx2tcd9leln exploring this differences and trying to bring more clarity to the DVM side nostr:naddr1qqxnzde4xscryvpc8qerzwf5qy28wumn8ghj7am0wshxummnw3ezumn9wshsygx6rr5cvqzq7wl5jwrklsttr2gj4edx7mag652ec00zhq3n5rvc2ypsgqqqw4rsp0qn5q
Also, you don't need an llm to use contextvm... But if you want you can use it as well