Comment by Technetium 2 days ago
They proclaim "privacy-respecting" but all your keystrokes go to OpenAI. Horrific and genuinely upsetting.
Edit: The author replied to another comment that there is an intent to add local AI. If that is the plan, then fix the wording until it can actually be considered privacy-respecting: https://news.ycombinator.com/item?id=41579144
> Doesn't seem like a good idea for extensions to be accessing local resources though.
To the best of my knowledge all localhost connections are exempt from CORS and that's in fact how the 1Password extension communicates with the desktop app. I'd bet Bitwarden and KeePassXC behave similarly
settings for opting out of training etc. for OpenAI
https://help.openai.com/en/articles/7730893-data-controls-fa...
Download koboldcpp and llama3.1 gguf weights, use it with the llama3 completions adapter.
Edit the 'background.js' file in the extension and replace the openAI endpoint with
'http://your.local.ip.addr:5001/v1/chat/completions'
Set anything you want as an API key. Now you have a truly local version.
* https://github.com/LostRuins/koboldcpp/releases
* https://huggingface.co/bartowski/Meta-Llama-3.1-8B-Instruct-...
* https://github.com/LostRuins/koboldcpp/blob/concedo/kcpp_ada...
Lol, this was my second thought immediately after my first, which was one of excitement. Hope the author does add a option for local. Wonder how that would work as a Chrome extension. Doesn't seem like a good idea for extensions to be accessing local resources though.