High on my todo list is HTTP over #veilid app messages with a local daemon that can act as a proxy.

- Register veilid service
- Run local daemon as a proxy (optionally tell it to make a safety route)
- Curl to a unix socket the daemon is listening on
- `Host` header set to the public key for the service
- Encode request as app message to the service
- Response gets sent as an HTTP response down the socket

Bad for large files, good for locally run services / automation.