Arjen on Nostr: ...

quoting nevent1q…q9lu

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