[idea]: add browser extensions for better speaker names

[meck93]

Idea: Add browser extensions for better speaker names

I would have first created a Github discussion but it doesn't seem to be enabled in this project. That's why I thought I create an issue. Hope this is fine @dremnik

Problem

Quill can tell the difference between the local user and other speakers. But it cannot always tell which remote person is speaking.
On the other hand, meeting tools already know the active speaker. They also know the participant names.
A browser extension could send this data to Quill to improve the speaker names in the transcript.

Ideas

• Use separate extension builds for each browser family.
  • Chromium and Firefox support native messaging (browser starts a bridge, bridge connects to running Quill app).
  • Safari could use the Safari Web Extension messaging system.
• Create one browser-independent adapter for each meeting tool.
• Define one shared event format. For example, meeting.started/participant.joined/speaker.started, etc.
• Quill can then match speaker events with transcript segments using the time overlap between both records.

[malihae]

I'd like to work on this @meck93 @dremnik

Proposed MVP:

• Chrome extension for Google Meet (most common)
• Native messaging host in Swift (integrated into Quill binary)
• Events: speaker.started with name + timestamp
• Quill merges with transcript segments

Questions:

1. Should I use an existing framework or build from scratch?
2. What's the preferred event format for Quill?
3. Any specific meeting platform to prioritize?

I can have a prototype ready in ~1 week. Let me know if this sounds good!