

14·
17 days agoIt’s clearly bad juju if you dont then save again just to be sure.
It’s clearly bad juju if you dont then save again just to be sure.
So uhh… hypothetically if one were to live next to a cornfield and acquire some seeds from said field cough somehow cough, would those purely hypothetical seeds grown in one’s garden then constitute corn piracy?
Asking for a friend of course.
I’m fairly confident it’s Obsidian, and not sure if the theme’s even been changed, as the default Obsidian in dark mode looks the same. Not sure if Logseq uses the same icons like on the left, but Obsidian does for sure.
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…