![](/static/c15a0eb1/assets/icons/icon-96x96.png)
![](https://linux.community/api/v3/image_proxy?url=https%3A%2F%2Flemmy.world%2Fpictrs%2Fimage%2F9677e716-69d1-40b0-80e1-99b81d23256d.png)
Looked up LL Bean on OpenSecrets just because my other reply rants about them a little. So I’m eating a bit of crow and sharing that apparently according to https://www.opensecrets.org/orgs/ll-bean-inc/summary?id=D000042703 LL Bean’s contributions lean vastly towards the Democrats, and none were from the company itself, but individuals within.
Still dislike the company for other valid reasons, but their political stance is different than I was originally assuming.
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…