docs(roadmap): add WAN access, VRR passthrough, desktop QoL items
apple / swift (push) Successful in 57s
ci / docs-site (push) Successful in 1m2s
android / android (push) Successful in 3m26s
ci / rust (push) Successful in 1m14s
ci / web (push) Successful in 37s
ci / bench (push) Successful in 4m36s
deb / build-publish (push) Successful in 4m10s
decky / build-publish (push) Successful in 11s
docker / build-push (--build-arg FEDORA_VERSION=44, ci, ci/fedora-rpm.Dockerfile, punktfunk-fedora44-rpm) (push) Successful in 5s
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 4s
docker / build-push (ci, ci/rust-ci.Dockerfile, punktfunk-rust-ci) (push) Successful in 5s
docker / build-push (docs-site, docs-site/Dockerfile, punktfunk-docs) (push) Successful in 39s
rpm / build-publish (bazzite, punktfunk-fedora-rpm) (push) Successful in 8m37s
docker / deploy-docs (push) Successful in 19s
rpm / build-publish (fedora-44, punktfunk-fedora44-rpm) (push) Successful in 8m30s
apple / swift (push) Successful in 57s
ci / docs-site (push) Successful in 1m2s
android / android (push) Successful in 3m26s
ci / rust (push) Successful in 1m14s
ci / web (push) Successful in 37s
ci / bench (push) Successful in 4m36s
deb / build-publish (push) Successful in 4m10s
decky / build-publish (push) Successful in 11s
docker / build-push (--build-arg FEDORA_VERSION=44, ci, ci/fedora-rpm.Dockerfile, punktfunk-fedora44-rpm) (push) Successful in 5s
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 4s
docker / build-push (ci, ci/rust-ci.Dockerfile, punktfunk-rust-ci) (push) Successful in 5s
docker / build-push (docs-site, docs-site/Dockerfile, punktfunk-docs) (push) Successful in 39s
rpm / build-publish (bazzite, punktfunk-fedora-rpm) (push) Successful in 8m37s
docker / deploy-docs (push) Successful in 19s
rpm / build-publish (fedora-44, punktfunk-fedora44-rpm) (push) Successful in 8m30s
WAN/anywhere access (NAT traversal + relay + QUIC migration), VRR/ adaptive-sync passthrough, and a desktop quality-of-life bullet covering clipboard sync, multi-monitor, and virtual-webcam redirection. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
@@ -81,6 +81,19 @@ see [Status & Progress](/docs/status).
|
|||||||
- **gamescope multi-user isolation.** Per-session input and audio so concurrent clients are fully
|
- **gamescope multi-user isolation.** Per-session input and audio so concurrent clients are fully
|
||||||
independent desktops (the shared-desktop case already works).
|
independent desktops (the shared-desktop case already works).
|
||||||
- **Peer-approved pairing.** Approve a new device from an already-paired device's own app.
|
- **Peer-approved pairing.** Approve a new device from an already-paired device's own app.
|
||||||
|
- **WAN / anywhere access.** Reach a host beyond the LAN — NAT traversal (ICE/STUN/TURN) plus a
|
||||||
|
self-hostable relay for when no direct path can be punched, and **QUIC connection migration** so a
|
||||||
|
client roams between networks (Wi-Fi ↔ cellular) without dropping the session. The control plane is
|
||||||
|
already QUIC over UDP, so this is mostly signalling and relay rather than a protocol change.
|
||||||
|
- **VRR / adaptive-sync passthrough.** Variable refresh end to end — the host renders at a variable
|
||||||
|
rate and the client presents with tearing-control/VRR instead of a fixed cadence, for tear- and
|
||||||
|
judder-free gaming. Builds on the client's presentation-feedback path and the per-session virtual
|
||||||
|
outputs.
|
||||||
|
- **Desktop quality-of-life.** The essentials that make remote *work* pleasant, each a new side plane
|
||||||
|
over the existing QUIC datagram channel: bidirectional rich **clipboard sync** (text and images),
|
||||||
|
**multi-monitor streaming** (present the host's several outputs as separate client windows), and
|
||||||
|
**virtual-webcam redirection** (the client's camera shows up as a webcam on the host, so video calls
|
||||||
|
run on the remote machine).
|
||||||
|
|
||||||
## ⛔ Parked / blocked
|
## ⛔ Parked / blocked
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user