livedesk 0.1.256 → 0.1.258

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (5) hide show
  1. package/README.md +63 -63
  2. package/bin/livedesk.js +652 -625
  3. package/hub/src/remote-hub.js +5510 -5510
  4. package/hub/src/server.js +534 -534
  5. package/package.json +2 -2
package/README.md CHANGED
@@ -1,63 +1,63 @@
1
- # LiveDesk
2
-
3
- Local screen wall Hub and remote client launcher.
4
-
5
- ## Hub
6
-
7
- ```powershell
8
- npx -y --prefer-online livedesk@latest
9
- npx -y --prefer-online livedesk@latest hub
10
- ```
11
-
12
- This starts the LiveDesk Hub, opens the local screen wall, and accepts clients.
13
- The Hub UI/API listens on `127.0.0.1` by default while the client endpoint
14
- continues to listen on the LAN.
15
-
16
- On startup, the launcher checks the Hub ports (`5179` and `5197`), identifies
17
- stale LiveDesk Hub processes from their Node command line, stops each PID only
18
- once, waits for the ports to be released and bindable, and then starts the new
19
- Hub. Unrelated processes are preserved and reported with their PID, name, and
20
- command line. The client endpoint remains fixed at TCP `5197` by default so
21
- firewall rules, router forwarding, and direct clients keep a stable contract.
22
- Pass `--no-clean` to disable the startup cleanup explicitly. If a child Hub
23
- still loses a startup race with `EADDRINUSE`, the launcher performs one cleanup
24
- and startup retry, then exits without looping.
25
-
26
- ## Client
27
-
28
- ```powershell
29
- npx -y --prefer-online livedesk@latest client
30
- npx -y --prefer-online livedesk@latest client 3
31
- ```
32
-
33
- The client signs in with Google, discovers the active Hub, and connects to the wall.
34
- On Windows, enable **Start with Windows** on the connection page to reconnect
35
- automatically after reboot.
36
-
37
- ## Frame modes
38
-
39
- - Mode 2: independent 320x180 RGB565+LZO tiles for large, stable walls.
40
- - Mode 3: direct hardware H.264 for focused remote control up to 4K.
41
- - Mode 4: client Mode 2 inputs composited by an isolated Hub worker into one
42
- bounded H.264 Atlas stream, then split by UV into the normal browser slots.
43
-
44
- ## Plans
45
-
46
- - Free: 5 personal devices with a standard wall banner ad.
47
- - Plus LTD launch: 30 personal devices, no ads, USD 79 one-time.
48
- - Pro LTD launch: commercial use and larger walls, no ads, USD 199 one-time.
49
-
50
- Monthly and yearly subscriptions are planned after the LTD launch.
51
-
52
- ## Free ad slot
53
-
54
- Free accounts show a standard bottom ad slot. Set these Vite build variables
55
- for a real AdSense placement:
56
-
57
- ```text
58
- VITE_LIVEDESK_ADSENSE_CLIENT=ca-pub-...
59
- VITE_LIVEDESK_ADSENSE_SLOT=...
60
- ```
61
-
62
- Without those values, LiveDesk renders a neutral sponsored-placement placeholder
63
- so the free-plan layout can still be tested.
1
+ # LiveDesk
2
+
3
+ Local screen wall Hub and remote client launcher.
4
+
5
+ ## Hub
6
+
7
+ ```powershell
8
+ npx -y --prefer-online livedesk@latest
9
+ npx -y --prefer-online livedesk@latest hub
10
+ ```
11
+
12
+ This starts the LiveDesk Hub, opens the local screen wall, and accepts clients.
13
+ The Hub UI/API listens on `127.0.0.1` by default while the client endpoint
14
+ continues to listen on the LAN.
15
+
16
+ On startup, the launcher checks the Hub ports (`5179` and `5197`), identifies
17
+ stale LiveDesk Hub processes from their Node command line, stops each PID only
18
+ once, waits for the ports to be released and bindable, and then starts the new
19
+ Hub. Unrelated processes are preserved and reported with their PID, name, and
20
+ command line. The client endpoint remains fixed at TCP `5197` by default so
21
+ firewall rules, router forwarding, and direct clients keep a stable contract.
22
+ Pass `--no-clean` to disable the startup cleanup explicitly. If a child Hub
23
+ still loses a startup race with `EADDRINUSE`, the launcher performs one cleanup
24
+ and startup retry, then exits without looping.
25
+
26
+ ## Client
27
+
28
+ ```powershell
29
+ npx -y --prefer-online livedesk@latest client
30
+ npx -y --prefer-online livedesk@latest client 3
31
+ ```
32
+
33
+ The client signs in with Google, discovers the active Hub, and connects to the wall.
34
+ On Windows, enable **Start with Windows** on the connection page to reconnect
35
+ automatically after reboot.
36
+
37
+ ## Frame modes
38
+
39
+ - Mode 2: independent 320x180 RGB565+LZO tiles for large, stable walls.
40
+ - Mode 3: direct hardware H.264 for focused remote control up to 4K.
41
+ - Mode 4: client Mode 2 inputs composited by an isolated Hub worker into one
42
+ bounded H.264 Atlas stream, then split by UV into the normal browser slots.
43
+
44
+ ## Plans
45
+
46
+ - Free: 5 personal devices with a standard wall banner ad.
47
+ - Plus LTD launch: 30 personal devices, no ads, USD 79 one-time.
48
+ - Pro LTD launch: commercial use and larger walls, no ads, USD 199 one-time.
49
+
50
+ Monthly and yearly subscriptions are planned after the LTD launch.
51
+
52
+ ## Free ad slot
53
+
54
+ Free accounts show a standard bottom ad slot. Set these Vite build variables
55
+ for a real AdSense placement:
56
+
57
+ ```text
58
+ VITE_LIVEDESK_ADSENSE_CLIENT=ca-pub-...
59
+ VITE_LIVEDESK_ADSENSE_SLOT=...
60
+ ```
61
+
62
+ Without those values, LiveDesk renders a neutral sponsored-placement placeholder
63
+ so the free-plan layout can still be tested.