in the screenshare branch, a resolved pin returns pip$: of(undefined), with the comment "the redundant PiP is hidden". It is only redundant when the pinned user is the one the PiP would have shown; upstream's PiP during a screenshare is the auto-selected spotlight speaker. Pinning participant B while C is talking hides C's PiP entirely, so you see the screen plus B and lose all visual feedback on who is speaking.
How to trigger
start/receive a screenshare, pin a participant who is not the active speaker.
Suggested fix
keep pip$: spotlightSpeaker$ and only blank it when the auto speaker resolves to the pinned participant.
Filed from the September 2026 audit (branch lotus).
**Severity:** low · **Type:** ux · **Confidence:** high
**Location:** `src/lotus/lotusSpotlight.ts:79-84`
### Problem
in the screenshare branch, a resolved pin returns `pip$: of(undefined)`, with the comment "the redundant PiP is hidden". It is only redundant when the pinned user *is* the one the PiP would have shown; upstream's PiP during a screenshare is the auto-selected spotlight speaker. Pinning participant B while C is talking hides C's PiP entirely, so you see the screen plus B and lose all visual feedback on who is speaking.
### How to trigger
start/receive a screenshare, pin a participant who is not the active speaker.
### Suggested fix
keep `pip$: spotlightSpeaker$` and only blank it when the auto speaker resolves to the pinned participant.
---
_Filed from the September 2026 audit (branch `lotus`)._
jared
added this to the EC fork audit 2026-09 · Medium & Low milestone 2026-09-12 02:13:12 -04:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Severity: low · Type: ux · Confidence: high
Location:
src/lotus/lotusSpotlight.ts:79-84Problem
in the screenshare branch, a resolved pin returns
pip$: of(undefined), with the comment "the redundant PiP is hidden". It is only redundant when the pinned user is the one the PiP would have shown; upstream's PiP during a screenshare is the auto-selected spotlight speaker. Pinning participant B while C is talking hides C's PiP entirely, so you see the screen plus B and lose all visual feedback on who is speaking.How to trigger
start/receive a screenshare, pin a participant who is not the active speaker.
Suggested fix
keep
pip$: spotlightSpeaker$and only blank it when the auto speaker resolves to the pinned participant.Filed from the September 2026 audit (branch
lotus).