

So big scary warning, but nothing than “audit your shit” to address it? I’m not an expert, and in fact just got ollama w/deepseek running on my machine last night… but like, isn’t it common courtesy to at least suggest a couple of ways to mitigate things when posting a “big scary warning” like that?
Especially given deepseek’s more open nature, and the various tidbits I’ve seen indicating that deepseek is open enough to be able to tweak/run entirely locally. So addressing the API issue seems within the realm of possibility…














I’m just glad Firefox is free, because with the way they’ve been doing things the last couple iterations I dont see a very good future for it.
Thank dog there’re alternatives out there.