docs: correct Real-time Communication in the beta README

Evidence: spikersoft-backend@master SpikerSoft.Business/Domain/Messaging/Services/MessagingAccessRules.cs:56 staff may message anyone.
Co-authored-by: Cursor <cursoragent@cursor.com>
This commit is contained in:
spikerjandCursor committed 2026-10-06 04:41:10 -04:00
1 parent 1b5953b11f
commit 3afdbd1f65
1 file changed
+3 -3
+3 -3
View File
@@ -2346,7 +2346,7 @@ Peer-to-peer browser video calls (WebRTC) with **authenticated, first-party sign
Live video streaming using **OvenPlayer** (WebRTC client) connected to an **OvenMediaEngine** instance. The media server runs as a separate Docker service behind Traefik. Live video streaming using **OvenPlayer** (WebRTC client) connected to an **OvenMediaEngine** instance. The media server runs as a separate Docker service behind Traefik.
- WebRTC source: `wss://stream.spikersoft.com/app/stream/` - WebRTC source: `wss://stream.spikersoft.com/app/stream?transport=all`
- Low-latency streaming for events and demonstrations - Low-latency streaming for events and demonstrations
- OvenPlayer embedded in the Angular `StreamComponent` - OvenPlayer embedded in the Angular `StreamComponent`
@@ -2374,8 +2374,8 @@ Chat is entirely hub-based with no REST API; all message exchange happens over W
Distinct from chat rooms: **1:1 private messaging** with a REST surface plus live delivery. Distinct from chat rooms: **1:1 private messaging** with a REST surface plus live delivery.
- A global chat **FAB + drawer** (`messaging-fab` / `messaging-drawer`) with per-conversation unread counts. - The corner quick-actions dock opens the **messaging drawer** (`messaging-drawer`) with per-conversation unread counts.
- The contact roster is **relationship-derived** (parent/child family links), and `MessagingAccessRules` enforces a role/family-scoped permission matrix — who may message whom is a policy decision, not an open directory. - `MessagingAccessRules` decides who may message whom: staff may message anyone, a parent may message their approved child, a child may message their parent, and anyone may reply in a conversation that already exists.
- Delivery rides the existing `NotificationsHub` (`ReceiveDirectMessage`), so no extra WebSocket connection. - Delivery rides the existing `NotificationsHub` (`ReceiveDirectMessage`), so no extra WebSocket connection.
| Method | Endpoint | Purpose | | Method | Endpoint | Purpose |