dvms are async - request note is created and submitted to relays - dvm may take that request and execute - some time later the dvm posts a response note

dvms are async - request note is created and submitted to relays - dvm may take that request and execute - some time later the dvm posts a response note

dvms are async - request note is created and submitted to relays - dvm may take that request and execute - some time later the dvm posts a response note

dvms are async - request note is created and submitted to relays - dvm may take that request and execute - some time later the dvm posts a response note

dvms are async - request note is created and submitted to relays - dvm may take that request and execute - some time later the dvm posts a response note

dvms are async - request note is created and submitted to relays - dvm may take that request and execute - some time later the dvm posts a response note

dvms are async - request note is created and submitted to relays - dvm may take that request and execute - some time later the dvm posts a response note

dvms are async - request note is created and submitted to relays - dvm may take that request and execute - some time later the dvm posts a response note

dvms are async - request note is created and submitted to relays - dvm may take that request and execute - some time later the dvm posts a response note

dvms are async - request note is created and submitted to relays - dvm may take that request and execute - some time later the dvm posts a response note

dvms are async - request note is created and submitted to relays - dvm may take that request and execute - some time later the dvm posts a response note

dvms are async - request note is created and submitted to relays - dvm may take that request and execute - some time later the dvm posts a response note

dvms are async - request note is created and submitted to relays - dvm may take that request and execute - some time later the dvm posts a response note

dvms are async - request note is created and submitted to relays - dvm may take that request and execute - some time later the dvm posts a response note

dvms are async - request note is created and submitted to relays - dvm may take that request and execute - some time later the dvm posts a response note

子にとっては関西時代のチームが良すぎたのもあるな。全国大会に出て予戦も超えて、一定の成功体験があるから余計に

結果こうなんだけど「相手がバカだったら伝わらないじゃん」とか思っちゃう（） https://chatgpt.com/share/67f29c47-11ec-8000-868c-2cb68cd128a3

cool idea. honestly this sounds like a paas built on kubernetes. k8s has the security context, network policies, and resource constraints you’re looking for, and provides an api for orchestrating workloads across nodes. - you could use nostr notes as workload definitions - you could use zaps to fund execution

cool idea. honestly this sounds like a paas built on kubernetes. k8s has the security context, network policies, and resource constraints you’re looking for, and provides an api for orchestrating workloads across nodes. - you could use nostr notes as workload definitions - you could use zaps to fund execution

cool idea. honestly this sounds like a paas built on kubernetes. k8s has the security context, network policies, and resource constraints you’re looking for, and provides an api for orchestrating workloads across nodes. - you could use nostr notes as workload definitions - you could use zaps to fund execution

cool idea. honestly this sounds like a paas built on kubernetes. k8s has the security context, network policies, and resource constraints you’re looking for, and provides an api for orchestrating workloads across nodes. - you could use nostr notes as workload definitions - you could use zaps to fund execution

cool idea. honestly this sounds like a paas built on kubernetes. k8s has the security context, network policies, and resource constraints you’re looking for, and provides an api for orchestrating workloads across nodes. - you could use nostr notes as workload definitions - you could use zaps to fund execution

cool idea. honestly this sounds like a paas built on kubernetes. k8s has the security context, network policies, and resource constraints you’re looking for, and provides an api for orchestrating workloads across nodes. - you could use nostr notes as workload definitions - you could use zaps to fund execution

cool idea. honestly this sounds like a paas built on kubernetes. k8s has the security context, network policies, and resource constraints you’re looking for, and provides an api for orchestrating workloads across nodes. - you could use nostr notes as workload definitions - you could use zaps to fund execution

cool idea. honestly this sounds like a paas built on kubernetes. k8s has the security context, network policies, and resource constraints you’re looking for, and provides an api for orchestrating workloads across nodes. - you could use nostr notes as workload definitions - you could use zaps to fund execution