Arjen

If you're into Nostr and also have a solid understanding of Networking, I want to work with you! Sign up for SEC-07! nostr:naddr1qvzqqqr4gupzpq7enxs5scju854msxd0xpjvpa4p94763rmgktrfyg0n5arpw8geqy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qgewaehxw309aex2mrp0yhxummnw3ezucm0d5hxzaf0qqv8xetr95crwtt5dpjj6mn9w3mk7unt94ehgctrdvea32pg

Finally selling my beloved decentralized home. Lived in it for 4 years. I can't keep it because i'm migrating soon 😢. Hoping to find someone that will appreciate the design and will take good care of it. https://plebeian.market/products/30018:3273726ad59eb50b7f8e008661f7d7e7be9d539e7477297fe0ad00da346e0200:decentralized-home-l4011rfxmw

Shower thought: "Why can kids adulterate something"

General purpose compute for sats After several iterations of (GitHub) Actions runners I recently had some very good conversations that helped boil the whole thing down to one core component: Paid subprocesses. The idea: - IN: cmd + args + stdin + env + 🥜 money - OUT: stdout + stderr + 🥜 change ⚠️ I'm showing a hacky proof of concept, by no means production ready. This is just to get the idea out. - Operators advertise their preinstalled software. (ffmpeg, ngit, act, etc...) - User filters operators by software/architecture. - Operator can whitelist users Workflows (CI/CD): - Doing workflows will be a layer on top of this. - Deals with the complexity of the ACT runners and (n)git. - All the workflow orchestrator would need is an operator that runs both ngit and act (or install it manually as part of the exec). Other stuff: - Use this to run one-off video transcoding jobs on specialized hardware - Video rendering - Audio transcription - [your creative idea here] I got this (hacky) version running, the first worker there is whitelist-only (for my own safety) Frontend for testing: https://loom.treegaze.com/ use: https://testnut.cashu.space wants: - Allow Operator to pipe to any backend (docker, vm, metal) - Log livestreaming (prob through some third-party server) Repos: protocol: https://gitworkshop.dev/npub1hw6amg8p24ne08c9gdq8hhpqx0t0pwanpae9z25crn7m9uy7yarse465gr/relay.ngit.dev/loom-protocol worker: https://gitworkshop.dev/npub1hw6amg8p24ne08c9gdq8hhpqx0t0pwanpae9z25crn7m9uy7yarse465gr/relay.ngit.dev/loom-worker site: https://gitworkshop.dev/npub1hw6amg8p24ne08c9gdq8hhpqx0t0pwanpae9z25crn7m9uy7yarse465gr/relay.ngit.dev/loom-site

😱 I realized the diagrams never showed up properly in the article. Fixed it. It should be more clear now what i'm describing in the article. https://blossom.primal.net/76d2a4ceb57294601b2196395be2480bd58035fde0108be92bb5adc3be13992a.svg nostr:naddr1qvzqqqr4gupzpwa4mkswz4t8j70s2s6q00wzqv7k7zamxrmj2y4fs88aktcfuf68qyghwumn8ghj7mn0wd68ytnhd9hx2tcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsq9rx9f3kkttfwqnhxtfjxqhnzvf0xgcrydglhc98q