docs(roadmap): add Magic multi-user support to planned
apple / swift (push) Successful in 56s
ci / web (push) Successful in 36s
ci / docs-site (push) Successful in 57s
deb / build-publish (push) Successful in 2m35s
ci / rust (push) Successful in 1m22s
android / android (push) Successful in 3m14s
decky / build-publish (push) Successful in 12s
docker / build-push (--build-arg FEDORA_VERSION=44, ci, ci/fedora-rpm.Dockerfile, punktfunk-fedora44-rpm) (push) Successful in 6s
docker / build-push (., web/Dockerfile, punktfunk-web) (push) Successful in 4s
docker / build-push (ci, ci/fedora-rpm.Dockerfile, punktfunk-fedora-rpm) (push) Successful in 3s
docker / build-push (ci, ci/rust-ci.Dockerfile, punktfunk-rust-ci) (push) Successful in 4s
docker / build-push (docs-site, docs-site/Dockerfile, punktfunk-docs) (push) Successful in 47s
ci / bench (push) Successful in 4m40s
rpm / build-publish (bazzite, punktfunk-fedora-rpm) (push) Successful in 9m30s
rpm / build-publish (fedora-44, punktfunk-fedora44-rpm) (push) Successful in 9m17s
docker / deploy-docs (push) Successful in 18s

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
2026-06-22 14:55:25 +00:00
parent b0c82333d2
commit a12c6e0ba4
+5
View File
@@ -60,6 +60,11 @@ see [Status & Progress](/docs/status).
## 🔭 Planned ## 🔭 Planned
- **Magic multi-user support.** Map a connecting client to a real user account on the host and log
them in automatically. The client picks an identity — e.g. an **Apple TV profile** — which maps to
an available host profile (likely behind a second per-user auth layer); on connect to an idle host,
the user lands in *their own* desktop/session, signed in, without touching the host. Turns one box
into a personal, profile-aware streaming target for a household.
- **Sub-frame pipelining.** Overlap encode and transmit within a single frame (a direct NVENC slice - **Sub-frame pipelining.** Overlap encode and transmit within a single frame (a direct NVENC slice
path) — the next big latency lever at high resolutions. path) — the next big latency lever at high resolutions.
- **True glass-to-glass latency** measured end to end (capture → on-screen present). - **True glass-to-glass latency** measured end to end (capture → on-screen present).