Should Privacy Guides require open-source, source-first or source-available as a criteria for all tools?

assuming the differentiation is there between clientside and serverside service usage, Clientside speaking (and don’t get me wrong i’m not implying that PG is doing it) you can’t just recommend me, the random netizen out there that wants to have privacy on his computer, to install ANYTHING that is not fully FOSS, and claim to have privacy with it.

So yeah clientside at least, you guys should 100% enforce the FOSS requirement since i’m assuming privacy from adversaries like the big bad boogeymen governments is the goal.

It’s a matter of standard imo, in my blog at least, for OPSEC purposes, i have never and won’t ever tolerate closed-source software when talking about privacy, because that’s just how it is, closed-source software is the main way people get spied on in the current era we’re in.