Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Always-visible mic and camera state, with a hardware off

已关闭
#170 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
15/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
c, electron, python, typescript

调研方向

Design work spanning the voice service, desktop shell, tray and glasses firmware. Start by reading how mic and camera state is emitted in sentient/voice/service.py and sentient/nodes/service.py, then the existing DesktopPrivacy.tsx controls. Done means the indicator appears within a second of any capture starting, and camera-off on the glasses cannot be overridden by the engine. Agree the design with maintainers before writing code.

由索引模型根据 Issue 内容生成。

描述

area: desktop area: devices area: voice enhancement help wanted priority: P1 size: S

Users trust devices that show when they listen. Gemini Live shows a persistent indicator while sharing. Removing Echo's local-processing option drove users away from Alexa. Reviewers treat the camera-less Even G2 as a privacy feature.

Idea:

  • a tray and title-bar indicator whenever any mic or camera is live, on desktop, phone or glasses
  • on the glasses, an LED tied to the camera's power line and a firmware-level camera-off mode
  • Settings states plainly that all audio stays local

Status in Sentient today: Partial. Desktop privacy controls exist (DesktopPrivacy.tsx), but there is no unified live indicator across devices.

Where: Mic and camera state events from sentient/voice/service.py and sentient/nodes/service.py, indicators in desktop/src/components/shell/TitleBar.tsx and desktop/electron/main/tray.ts, and firmware in firmware/esp32s3-glasses/main/camera.c and app_config.h.

Done when:

  • the indicator shows within a second of any mic or camera turning on, on any device
  • camera-off mode on the glasses cannot be overridden by the engine

Sources:

Roadmap ID: VOICE-3 · Priority: P1 · Size: S

主要语言
Python
星标
702
派生
113
平均合并
5 小时 8 分钟
30 天内合并 PR
171

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

existence-master/Sentient 的其他 Issue

查看 existence-master/Sentient 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。