Fix indenting
This commit is contained in:
Daniel Gray
parent
d31260716b
commit
9e188228fd
@ -56,26 +56,27 @@
|
||||
chrome="https://chrome.google.com/webstore/detail/keybase-for-reddit/ognfafcpbkogffpmmdglhbjboeojlefj"
|
||||
%}
|
||||
|
||||
<div class="container">
|
||||
<div class="container">
|
||||
<div class="row">
|
||||
<div class="col-md-6">
|
||||
<h3>Advantages</h3>
|
||||
<ul>
|
||||
<li>New features and changes can be implemented more quickly.</li>
|
||||
<li>Easier to get started with and to find contacts.</li>
|
||||
</ul>
|
||||
</div>
|
||||
<div class="col-md-6">
|
||||
<h3>Disadvantages</h3>
|
||||
<ul>
|
||||
<li>Centralized services could be more susceptible to <a href="#exploiting-centralized-networks">legislation requiring backdoor access</a>.</li>
|
||||
<li>Can include <a href="https://drewdevault.com/2018/08/08/Signal.html">restricted control or access</a>. This can include things like:</li>
|
||||
<h3>Advantages</h3>
|
||||
<ul>
|
||||
<li>Being <a href="https://github.com/LibreSignal/LibreSignal/issues/37#issuecomment-217211165">forbidden from connecting third-party clients</a> to the centralized network that might provide for greater customization or better user experience. Often defined in Terms and Conditions of usage.</li>
|
||||
<li>Poor or no documentation for third-party developers.</li>
|
||||
<li>New features and changes can be implemented more quickly.</li>
|
||||
<li>Easier to get started with and to find contacts.</li>
|
||||
</ul>
|
||||
<li>The <a href="https://blog.privacytools.io/delisting-wire">ownership</a>, privacy policy, and operations of the service can change easily when a single entity controls it, potentially compromising the service later on.</li>
|
||||
</ul>
|
||||
</div>
|
||||
<div class="col-md-6">
|
||||
<h3>Disadvantages</h3>
|
||||
<ul>
|
||||
<li>Centralized services could be more susceptible to <a href="#exploiting-centralized-networks">legislation requiring backdoor access</a>.</li>
|
||||
<li>Can include <a href="https://drewdevault.com/2018/08/08/Signal.html">restricted control or access</a>. This can include things like:</li>
|
||||
<ul>
|
||||
<li>Being <a href="https://github.com/LibreSignal/LibreSignal/issues/37#issuecomment-217211165">forbidden from connecting third-party clients</a> to the centralized network that might provide for greater customization or better user experience. Often defined in Terms and Conditions of usage.</li>
|
||||
<li>Poor or no documentation for third-party developers.</li>
|
||||
</ul>
|
||||
<li>The <a href="https://blog.privacytools.io/delisting-wire">ownership</a>, privacy policy, and operations of the service can change easily when a single entity controls it, potentially compromising the service later on.</li>
|
||||
</ul>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
@ -106,27 +107,28 @@
|
||||
web="https://riot.im/app/"
|
||||
%}
|
||||
|
||||
<div class="container">
|
||||
<div class="container">
|
||||
<div class="row">
|
||||
<div class="col-md-6">
|
||||
<h3>Advantages</h3>
|
||||
<ul>
|
||||
<li>Allows for greater control over your own data when running your own server.</li>
|
||||
<li>Allows you to choose who to trust your data with by choosing between multiple "public" servers.</li>
|
||||
<li>Often allows for third party clients which can provide a more native, customized, or accessible experience.</li>
|
||||
<li>Generally a less juicy target for governments wanting <a href="#exploiting-centralized-networks">backdoor access to everything</a> as the trust is decentralized. The server may be hosted independently from the organization developing the software.</li>
|
||||
<li>Server software can be verified that it matches public source code, assuming you have access to the server or you trust the person who does (e.g., a family member)</li>
|
||||
<li>Third-party developers can contribute code and add new features, instead of waiting for a private development team to do so.</li>
|
||||
</ul>
|
||||
</div>
|
||||
<div class="col-md-6">
|
||||
<h3>Disadvantages</h3>
|
||||
<ul>
|
||||
<li>Adding new features is more complex, because these features need to be standardized and tested to ensure they work with all servers on the network.</li>
|
||||
<li>Some metadata may be available (e.g., information like "who is talking to whom," but not actual message content if E2EE is used).</li>
|
||||
<li>Federated servers generally require trusting your server's administrator. They may be a hobbyist or otherwise not a "security professional," and may not serve standard documents like a privacy policy or terms of service detailing how your data is utilized.</li>
|
||||
<li>Server administrators sometimes choose to block other servers, which are a source of unmoderated abuse or break general rules of accepted behavior. This will hinder your ability to communicate with users on those servers.</li>
|
||||
</ul>
|
||||
<h3>Advantages</h3>
|
||||
<ul>
|
||||
<li>Allows for greater control over your own data when running your own server.</li>
|
||||
<li>Allows you to choose who to trust your data with by choosing between multiple "public" servers.</li>
|
||||
<li>Often allows for third party clients which can provide a more native, customized, or accessible experience.</li>
|
||||
<li>Generally a less juicy target for governments wanting <a href="#exploiting-centralized-networks">backdoor access to everything</a> as the trust is decentralized. The server may be hosted independently from the organization developing the software.</li>
|
||||
<li>Server software can be verified that it matches public source code, assuming you have access to the server or you trust the person who does (e.g., a family member)</li>
|
||||
<li>Third-party developers can contribute code and add new features, instead of waiting for a private development team to do so.</li>
|
||||
</ul>
|
||||
</div>
|
||||
<div class="col-md-6">
|
||||
<h3>Disadvantages</h3>
|
||||
<ul>
|
||||
<li>Adding new features is more complex, because these features need to be standardized and tested to ensure they work with all servers on the network.</li>
|
||||
<li>Some metadata may be available (e.g., information like "who is talking to whom," but not actual message content if E2EE is used).</li>
|
||||
<li>Federated servers generally require trusting your server's administrator. They may be a hobbyist or otherwise not a "security professional," and may not serve standard documents like a privacy policy or terms of service detailing how your data is utilized.</li>
|
||||
<li>Server administrators sometimes choose to block other servers, which are a source of unmoderated abuse or break general rules of accepted behavior. This will hinder your ability to communicate with users on those servers.</li>
|
||||
</ul>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
@ -173,24 +175,25 @@
|
||||
ios="https://itunes.apple.com/app/ring-a-gnu-package/id1306951055?mt=8"
|
||||
%}
|
||||
|
||||
<div class="container">
|
||||
<div class="container">
|
||||
<div class="row">
|
||||
<div class="col-md-6">
|
||||
<h3>Advantages</h3>
|
||||
<ul>
|
||||
<li>Minimal information is exposed to third parties.</li>
|
||||
<li>Modern P2P platforms implement end-to-end encryption by default. There are no servers that could potentially intercept and decrypt your transmissions, unlike centralized and federated models.</li>
|
||||
</ul>
|
||||
</div>
|
||||
<div class="col-md-6">
|
||||
<h3>Disadvantages</h3>
|
||||
<ul>
|
||||
<li>Reduced feature set:</li>
|
||||
<h3>Advantages</h3>
|
||||
<ul>
|
||||
<li>Messages can only be sent when both peers are online, however, your client may store messages locally to wait for the contact to return online.</li>
|
||||
<li>Generally increases battery usage on mobile devices, because the client must stay connected to the distributed network to learn about who is online.</li>
|
||||
<li>Minimal information is exposed to third parties.</li>
|
||||
<li>Modern P2P platforms implement end-to-end encryption by default. There are no servers that could potentially intercept and decrypt your transmissions, unlike centralized and federated models.</li>
|
||||
</ul>
|
||||
<li>Your <a href="https://en.wikipedia.org/wiki/IP_address">IP address</a> and that of the contacts you're communicating with may be visible if you do not use the software in conjunction with a <a href="/software/networks">self contained network</a>, such as <a href="https://www.torproject.org">Tor</a> or <a href="https://geti2p.net/">I2P</a>. Many countries have some form of mass surveillance and/or metadata retention.</li>
|
||||
</ul>
|
||||
</div>
|
||||
<div class="col-md-6">
|
||||
<h3>Disadvantages</h3>
|
||||
<ul>
|
||||
<li>Reduced feature set:</li>
|
||||
<ul>
|
||||
<li>Messages can only be sent when both peers are online, however, your client may store messages locally to wait for the contact to return online.</li>
|
||||
<li>Generally increases battery usage on mobile devices, because the client must stay connected to the distributed network to learn about who is online.</li>
|
||||
</ul>
|
||||
<li>Your <a href="https://en.wikipedia.org/wiki/IP_address">IP address</a> and that of the contacts you're communicating with may be visible if you do not use the software in conjunction with a <a href="/software/networks">self contained network</a>, such as <a href="https://www.torproject.org">Tor</a> or <a href="https://geti2p.net/">I2P</a>. Many countries have some form of mass surveillance and/or metadata retention.</li>
|
||||
</ul>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
Reference in New Issue
Block a user