Smart choice using Groq's free tier with LLaMA 3 - the speed is hard to beat for real-time summarization. Using Mozilla Readability for extraction is solid too, it handles messy article HTML surprisingly well. Curious - how do you handle pages where Readability fails to extract cleanly, like single-page apps or paywalled content? Also, DOMPurify for sanitization is a nice touch for security. 36 customization combos is a lot of flexibility without overcomplicating the UX.
Nice approach, using Supabase as the storage backend means users own their data completely. The no-middleman architecture is exactly what privacy-conscious users want. How's the recording quality compared to Loom? And do you handle variable bitrate or let the browser's MediaRecorder decide? Curious about the PIP overlay performance too - canvas compositing can get heavy during long recordings.
Scoping to a dedicated tab group is a smart approach for sandboxing. The activeTab permission model already limits access nicely, but combining it with tab groups adds a visible boundary that users can actually see and trust. Would be great if Chrome's extensions API gave more granular tab group controls natively.
Really cool that all data stays local in the browser — that's exactly how privacy-sensitive tools should work. As someone building a Chrome extension myself, I appreciate the no-account-needed approach. For UX feedback: have you considered adding a simple onboarding screen on first install? Even a single page explaining what it does and how to start would help with retention. Nice work shipping this!
