28·
1 month agoThe same tool that can be used to permanently activate a Windows install can be used to permanently activate an Office install as well; including 365.
Oh, and the tool to do so is open-source.
Or you could just dump Microsoft entirely (unless you need Excel in particular). Either way, it’s free.
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…