The Lotus fork has no documentation: the io.lotus.* widget protocol and URL flags are only described in code comments #43

Closed
opened 2026-10-04 19:50:23 -04:00 by jared · 0 comments
Owner

The fork adds a lot that the host relies on, and none of it is documented outside src/lotus/*.ts comments (README.md and docs/ are upstream's):

  • ~22 widget actions in src/lotus/lotusActions.ts, both toWidget and fromWidget. Examples: call_state, set_deafen, inject_audio, set_quality, focus_participant, set_screenshare (with Capability Delegation), prompt_screenshare, set_hotkeys/hotkey, controls_state, mic_level, denoise_state, audio_output_state, call_summary, screenshare_notice, request_state.
  • URL flags: lotusCallState, lotusTransparent, lotusTheme, lotusHostControls, lotusFrameScreenshare, lotusAudioInject, lotusDenoiseSource, lotusModel, lotusGate, lotusGateThreshold.
  • Fork-only behaviour: per-person volume memory (#36), screenshare notices (#39), mono mic capture, an SFU refusal reason instead of "Something went wrong", and its own-origin support (cinny #43).

Why it matters: the host and the fork have already drifted. cinny never handles denoise_state or audio_output_state (cinny #260), and still listens for a postMessage the fork stopped sending. A single protocol table both sides are tested against would have caught that.

Suggestion: LOTUS.md in this repo with the action table (direction, payload, who handles it, since which version), the URL flags, and the release/publish flow (@lotusguild/element-call-embedded, lotus dist-tag).


Found in the October 2026 client audit (Playwright against a local Synapse + LiveKit stack, plus code reading). Code refs are at cinny 30e2dbcd, cinny-desktop 8f67ec7, element-call 3b0050e8.

The fork adds a lot that the host relies on, and none of it is documented outside `src/lotus/*.ts` comments (README.md and docs/ are upstream's): - **~22 widget actions** in `src/lotus/lotusActions.ts`, both toWidget and fromWidget. Examples: `call_state`, `set_deafen`, `inject_audio`, `set_quality`, `focus_participant`, `set_screenshare` (with Capability Delegation), `prompt_screenshare`, `set_hotkeys`/`hotkey`, `controls_state`, `mic_level`, `denoise_state`, `audio_output_state`, `call_summary`, `screenshare_notice`, `request_state`. - **URL flags:** `lotusCallState`, `lotusTransparent`, `lotusTheme`, `lotusHostControls`, `lotusFrameScreenshare`, `lotusAudioInject`, `lotusDenoiseSource`, `lotusModel`, `lotusGate`, `lotusGateThreshold`. - **Fork-only behaviour:** per-person volume memory (#36), screenshare notices (#39), mono mic capture, an SFU refusal reason instead of "Something went wrong", and its own-origin support (cinny #43). **Why it matters:** the host and the fork have already drifted. cinny never handles `denoise_state` or `audio_output_state` (cinny #260), and still listens for a postMessage the fork stopped sending. A single protocol table both sides are tested against would have caught that. **Suggestion:** `LOTUS.md` in this repo with the action table (direction, payload, who handles it, since which version), the URL flags, and the release/publish flow (`@lotusguild/element-call-embedded`, `lotus` dist-tag). --- _Found in the October 2026 client audit (Playwright against a local Synapse + LiveKit stack, plus code reading). Code refs are at cinny `30e2dbcd`, cinny-desktop `8f67ec7`, element-call `3b0050e8`._
jared added the priority: lowdocsarea: widget-actions labels 2026-10-04 19:50:23 -04:00
jared closed this issue 2026-10-18 07:49:15 -04:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: LotusGuild/element-call#43