From c3fa121f1a3ec74c5980bc8981e4836ca3a708f2 Mon Sep 17 00:00:00 2001 From: yum Date: Mon, 13 Oct 2025 19:17:26 -0700 Subject: shart attack --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'README.md') diff --git a/README.md b/README.md index 5faee83..9c21585 100644 --- a/README.md +++ b/README.md @@ -4,11 +4,11 @@ Shitty service to proxy data from OBS into a low-latency MPEG-DASH stream VRChat 1. Configure OBS with a custom server pointing at `rtmp:///live` and the pre-shared key stored in `STREAM_PSK`. 2. Start the Python service (see `etc/systemd/system/obsproxy.service` for a sample unit). -3. Share `https:///dash/manifest.mpd` with your VRChat video player. Multiple viewers can consume the feed concurrently. +3. When the service starts it prints a session-specific manifest URL like `https:///dash//manifest.mpd`; share that exact URL with your VRChat video player. Multiple viewers can consume the feed concurrently. Environmental knobs: - `STREAM_PSK`: required PSK for the single ingest client. - `DASH_SEGMENT_TIME` / `DASH_FRAGMENT_TIME`: tweak DASH segment/fragment durations to balance latency vs resilience. -The server seeds a fresh 128-bit session ID on every restart and writes DASH fragments under `/live/`. The public manifest route stays fixed at `/dash/manifest.mpd`. +The server seeds a fresh 128-bit session ID on every restart and writes DASH fragments under `/live/`. The manifest and segments are only exposed under `/dash//`, making it infeasible to guess a live session path. -- cgit v1.2.3