https://wiki.doikayt.org/index.php?action=history&feed=atom&title=Category%3ACommunications 2026-09-11T09:37:57Z Revision history for this page on the wiki MediaWiki 1.46.0 https://wiki.doikayt.org/index.php?title=Category:Communications&diff=3&oldid=prev 2026-08-12T02:35:18Z

<p>qwiki: categories/communications.md</p> <p><b>New page</b></p><div>&lt;span id=&quot;communications&quot;&gt;&lt;/span&gt;<br /> = Communications =<br /> <br /> Internal and external messaging for the organization.<br /> <br /> &#039;&#039;&#039;On evaluating communication tools:&#039;&#039;&#039; judge every one on four axes, not just “is it encrypted”:<br /> <br /> # &#039;&#039;&#039;Content encryption&#039;&#039;&#039; – is it end-to-end &#039;&#039;by default&#039;&#039;, or can the provider read messages?<br /> # &#039;&#039;&#039;Metadata&#039;&#039;&#039; – what the operator can still see and log (who talks to whom, and when), even when content is encrypted.<br /> # &#039;&#039;&#039;Infrastructure control&#039;&#039;&#039; – can you self-host or federate, or can a single operator cut you off, change the rules, or be compelled by a government? Prefer self-hostable/federated, then privacy-focused nonprofits, then mainstream platforms.<br /> # &#039;&#039;&#039;Endpoint security&#039;&#039;&#039; – encryption in transit is moot if the device at either end is compromised; that is usually the real attack surface.<br /> <br /> [[Category:Domains]]</div>

Admin