The hub
darkpyonix.dev
The hub connects your machines to each other and to the people you share with. It passes connections along; it does not run kernels. Everything on this page is planned.
What it does planned #21
- Sign-in with GitHub, and a list of your devices.
- Rendezvous and relay between machines: a direct connection through NAT when possible, a relay otherwise.
- Share links that open a shared kernel in ash.
- HTTPS names for a dedicated manager.
- Hosting ash, the shared notebook.
Hosts planned #41
How the work splits across hosts is a draft in pull request #41 and waits for the maintainer's approval. The draft:
| Host | Serves |
|---|---|
darkpyonix.dev/ | The main page and the ash web app, built by darkpyonix-ash. |
darkpyonix.dev/<repo>/ | Project guides such as this one. They do not move. |
api.darkpyonix.dev | The hub API: sign-in, devices, address directory, shares, names. |
relay.darkpyonix.dev | The relay for machine-to-machine connections. |
What the hub sees
The hub connects two ends. Content is meant to be encrypted between them (SPEC NFR-H1), so the hub does not read your code or outputs. In the draft, a share link keeps its token in the URL fragment, which browsers never send to a server.
What works today
The hub is not running yet. To reach a kernel on another machine today, run a dedicated manager there
(darkpyonix manager --dedicated --host ... --port ...) and reach it over a network you
already trust, such as a VPN.