Re:Show HN: I wrote a browser AI assistant without requiring...
by richin13 on Wednesday March 12, 2025 @04:06PM
(#43347154)
Fair enough. I asked because an extension like this has access to too much information which I don't like from a privacy stand point.
Thanks for sharing though!
Re:Show HN: I wrote a browser AI assistant without requiring...
by djyde on Wednesday March 12, 2025 @10:19PM
(#43349790)
I understand your concern. I think "access to much information" means this extension require <all_url> host_permission, which I don't want to either but it must.
Because custom AI provider's API base url is submit by user. If I want to call the API on background script, this base url must be listed on host_permissions. Otherwise it will cause a CORS problem.
optional_host_permissions may fix this problem, but since the base url is set by user, it's not possible to use this workaround.
Any suggestion?
Re:Show HN: I wrote a browser AI assistant without requiring...
by tough on Thursday March 13, 2025 @02:12AM
(#43350763)
you could give paying customers access to the code to run themselves (not open source)
if that works for you/your privacy-aware customer they can inspect the code/build it/ run their own version
Re:Show HN: I wrote a browser AI assistant without requiring...
by djyde on Thursday March 13, 2025 @03:05AM
(#43350925)
Actually, the nice thing about chrome extensions is that users can view all requests made by content_script and background script through devtool. This is much more intuitive than checking the code.
Re:Show HN: I wrote a browser AI assistant without requiring...
by Ylpertnodi on Wednesday March 12, 2025 @06:10PM
(#43348179)
>will less than $20/year.
I'd rather pay more, once, than another* subscription.
*Of which, I have reduced to two: phone plan [€5.99pcm], and mullvad [€5.00pcm].
No more.
But I can share the tech stack I use:
- WXT: the browser extension framework
- Vercel AI SDK. Both SDK core and SDK UI. I wrote a bridge that I can proxy the api request to background script which compat with the SDK streaming protocol, so that I can use the SDK UI.
- Next.js: for the landing page and the up coming cloud service (e.g. prompt sync)
- Strapi: headless cms.