Correct Additional HTML Validation Errors

.github/workflows/tests.yml

@@ -40,7 +40,6 @@ jobs:
     name: "Broken Hyperlinks (Internal)"
     runs-on: ubuntu-latest
     needs: [deps, build]
-    continue-on-error: true
 
     steps:
     - uses: actions/checkout@v2
@@ -85,7 +84,7 @@ jobs:
         uses: chabad360/htmlproofer@v1.1
         with:
           directory: ${{ github.workspace }}/_site
-          arguments: --assume-extension --external_only --internal-domains privacyguides.org,www.privacyguides.org --url-ignore '^(?:https?\:\/\/)?[\w\-\.]+\.onion'
+          arguments: --assume-extension --external_only --only_4xx --internal-domains privacyguides.org,www.privacyguides.org
 
   https:
     name: "Require HTTPS Internal Images"
@@ -112,7 +111,7 @@ jobs:
   scripts:
     name: "Script Reference Checks"
     runs-on: ubuntu-latest
-    needs: [link, https]
+    needs: [build, link]
     continue-on-error: true
 
     steps:
@@ -134,7 +133,7 @@ jobs:
   tags:
     name: "HTML Tag Test"
     runs-on: ubuntu-latest
-    needs: https
+    needs: build
     continue-on-error: true
 
     steps:
@@ -156,7 +155,7 @@ jobs:
   entity:
     name: "HTML Entity Names Test"
     runs-on: ubuntu-latest
-    needs: https
+    needs: build
     continue-on-error: true
 
     steps:
@@ -178,7 +177,7 @@ jobs:
   misc:
     name: "Misc HTML Test"
     runs-on: ubuntu-latest
-    needs: https
+    needs: build
     continue-on-error: true
 
     steps:

_includes/legacy/sections/android-operating-systems.html

@@ -1,6 +1,6 @@
 <h1 id="mobile_os" class="anchor"><a href="#mobile_os"><i class="fas fa-link anchor-icon"></i></a> Mobile Operating Systems</h1>
 
-<h2 id="aosp_os" class="anchor"><a href="#aosp_os"><i class="fas fa-link anchor-icon"></i></a> Android-based Operating Systems</h1>
+<h2 id="aosp_os" class="anchor"><a href="#aosp_os"><i class="fas fa-link anchor-icon"></i></a> Android-based Operating Systems</h2>
 
 <div class="alert alert-warning" role="alert">
   <strong>Even though the source code of the following operating systems is provided, installing Google Apps may compromise your setup.</strong>

_includes/legacy/sections/browser-addons.html

@@ -7,7 +7,7 @@
 {% include legacy/cardv2.html
   title="uBlock Origin: Block Ads and Trackers"
   image="/assets/img/legacy_svg/3rd-party/ublock_origin.svg"
-  description="<p><strong>uBlock Origin</strong> is an efficient <a href=https://github.com/gorhill/uBlock/wiki/Blocking-mode>wide-spectrum blocker</a> that is easy on memory, and yet can load and enforce thousands more filters than other popular blockers out there. It has no monetization strategy and is completely open source. <a href=https://github.com/gorhill/uBlock/wiki/Advanced-user-features>Advanced mode</a> allows for <a href=https://github.com/gorhill/uBlock/wiki/Dynamic-filtering:-quick-guide>dynamic filtering</a>. Dynamic filtering allows for extended blocking similar to NoScript and uMatrix (E.g. <a href=https://github.com/gorhill/uBlock/wiki/Blocking-mode:-medium-mode>medium</a> or <a href=https://github.com/gorhill/uBlock/wiki/Blocking-mode:-hard-mode>hard</a>) blocking.</p>"
+  description="<strong>uBlock Origin</strong> is an efficient <a href=https://github.com/gorhill/uBlock/wiki/Blocking-mode>wide-spectrum blocker</a> that is easy on memory, and yet can load and enforce thousands more filters than other popular blockers out there. It has no monetization strategy and is completely open source. <a href=https://github.com/gorhill/uBlock/wiki/Advanced-user-features>Advanced mode</a> allows for <a href=https://github.com/gorhill/uBlock/wiki/Dynamic-filtering:-quick-guide>dynamic filtering</a>. Dynamic filtering allows for extended blocking similar to NoScript and uMatrix (E.g. <a href=https://github.com/gorhill/uBlock/wiki/Blocking-mode:-medium-mode>medium</a> or <a href=https://github.com/gorhill/uBlock/wiki/Blocking-mode:-hard-mode>hard</a>) blocking."
   website="https://addons.mozilla.org/firefox/addon/ublock-origin/"
   privacy-policy="https://github.com/gorhill/uBlock/wiki/Privacy-policy"
   github="https://github.com/gorhill/uBlock/"

_includes/legacy/sections/browser-tweaks.html

@@ -110,6 +110,7 @@
     <li>network.predictor.enabled = false</li>
     <li>network.predictor.enable-prefetch = false</li>
     <li>network.prefetch-next = false</li>
+  </ul>
   </dd>
 
   <dt>network.IDN_show_punycode = true</dt>
@@ -117,6 +118,7 @@
 
   <dt>Looking for TRR, DoH or ESNI?</dt>
   <dd>They have moved to <a href="/providers/dns/#dns">our DNS page</a>.</dd>
+</dl>
 
 <h3 id="user.js">Firefox user.js Templates</h3>
 <ul>

_includes/legacy/sections/dns.html

@@ -190,6 +190,7 @@ We also log how many times this or that tracker has been blocked. We need this i
             data-toggle="tooltip"
             data-placement="bottom">
             <span class="fas fa-globe"></span>
+          </div>
         </td>
         <td><a data-toggle="tooltip" data-placement="bottom" data-original-title='"CZ.NIC is an interest association of legal entities, founded in 1998 by leading providers of Internet services."' href="https://www.nic.cz/page/351/about-association/">Association</a></td>
         <td>No</td>

_includes/legacy/sections/instant-messenger.html

@@ -4,7 +4,8 @@
 </h1>
 
 <div class="alert alert-warning" role="alert">
-  <strong>If you are currently using an Instant Messenger like Telegram, LINE, Viber, <a href="https://www.eff.org/deeplinks/2016/10/where-whatsapp-went-wrong-effs-four-biggest-security-concerns">WhatsApp</a>, or plain SMS, you should pick an alternative here.</strong></div>
+  <strong>If you are currently using an Instant Messenger like Telegram, LINE, Viber, <a href="https://www.eff.org/deeplinks/2016/10/where-whatsapp-went-wrong-effs-four-biggest-security-concerns">WhatsApp</a>, or plain SMS, you should pick an alternative here.</strong>
+</div>
 
 <p>We only recommend instant messenger programs or apps that support <a href="https://en.wikipedia.org/wiki/End-to-end_encryption">end-to-end encryption (E2EE)</a>. When E2EE is used, all transmissions (messages, voice, video, etc.) are encrypted <strong>before</strong> they are sent from your device. E2EE protects both the authenticity and confidentiality of the transmission as they pass through any part of the network (servers, etc.).</p>
 
@@ -39,34 +40,34 @@
 <div class="container">
   <div class="row">
     <div class="col-md-6">
-    <h3>Advantages</h3>
+      <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>
       <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>New features and changes can be implemented more quickly.</li>
-        <li>Poor or no documentation for third-party developers.</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>
+    </div>
-    </ul>
+    <div class="col-md-6">
-  </div>
+      <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>
 
-<div>
-  <h2 id="federated" class="anchor">
-    <a href="#federated"><i class="fas fa-link anchor-icon"></i></a>
-    Federated
-  </h2>
 
-  <p>Federated messengers use multiple, independent servers that are able to talk to each other (email is one example of a federated service). Federation allows system administrators to control their own server and still be a part of the larger communications network.</p>
+<h2 id="federated" class="anchor">
+  <a href="#federated"><i class="fas fa-link anchor-icon"></i></a>
+  Federated
+</h2>
+
+<p>Federated messengers use multiple, independent servers that are able to talk to each other (email is one example of a federated service). Federation allows system administrators to control their own server and still be a part of the larger communications network.</p>
 
 {%
   include legacy/cardv2.html
@@ -111,19 +112,18 @@
   </div>
 </div>
 
-<div>
+<h4>Worth Mentioning</h4>
-  <h4>Worth Mentioning</h4>
 
-  <ul>
+<ul>
-    <li><a href="https://status.im">Status.im</a> - Encrypted instant messenger with an integrated <a href="https://en.wikipedia.org/wiki/Ethereum">Ethereum</a> wallet (cryptocurrency) that also includes support for <a href="https://our.status.im/tag/dapps">DApps (decentralized apps)</a> (web apps in a curated store). Uses the <a href="https://our.status.im/status-launches-private-peer-to-peer-messaging-protocol/">Waku protocol (a fork of Whisper)</a> for P2P communication. Only available for iOS and Android.</li>
+  <li><a href="https://status.im">Status.im</a> - Encrypted instant messenger with an integrated <a href="https://en.wikipedia.org/wiki/Ethereum">Ethereum</a> wallet (cryptocurrency) that also includes support for <a href="https://our.status.im/tag/dapps">DApps (decentralized apps)</a> (web apps in a curated store). Uses the <a href="https://our.status.im/status-launches-private-peer-to-peer-messaging-protocol/">Waku protocol (a fork of Whisper)</a> for P2P communication. Only available for iOS and Android.</li>
-  </ul>
+</ul>
 
-  <h2 id="peer-to-peer" class="anchor">
+<h2 id="peer-to-peer" class="anchor">
-    <a href="#peer-to-peer"><i class="fas fa-link anchor-icon"></i></a>
+  <a href="#peer-to-peer"><i class="fas fa-link anchor-icon"></i></a>
-    Peer to Peer (P2P)
+  Peer to Peer (P2P)
-  </h2>
+</h2>
 
-  <p>Peer-to-Peer instant messengers connect directly to each other without requiring third-party servers. Clients (peers) usually find each other through the use of a <a href="https://en.wikipedia.org/wiki/Distributed_computing">distributed computing</a> network. Examples of this include <a href="https://en.wikipedia.org/wiki/Distributed_hash_table">DHT (distributed hash table)</a> (used with technologies like <a href="https://en.wikipedia.org/wiki/BitTorrent_(protocol)">torrents</a> and <a href="https://en.wikipedia.org/wiki/InterPlanetary_File_System">IPFS</a>, for example). Another approach is proximity based networks, where a connection is established over WiFi or Bluetooth (for example, Briar or the <a href="https://www.scuttlebutt.nz">Scuttlebutt</a> social networking protocol). Once a peer has found a route to its contact via any of these methods, a direct connection between them is made.</p>
+<p>Peer-to-Peer instant messengers connect directly to each other without requiring third-party servers. Clients (peers) usually find each other through the use of a <a href="https://en.wikipedia.org/wiki/Distributed_computing">distributed computing</a> network. Examples of this include <a href="https://en.wikipedia.org/wiki/Distributed_hash_table">DHT (distributed hash table)</a> (used with technologies like <a href="https://en.wikipedia.org/wiki/BitTorrent_(protocol)">torrents</a> and <a href="https://en.wikipedia.org/wiki/InterPlanetary_File_System">IPFS</a>, for example). Another approach is proximity based networks, where a connection is established over WiFi or Bluetooth (for example, Briar or the <a href="https://www.scuttlebutt.nz">Scuttlebutt</a> social networking protocol). Once a peer has found a route to its contact via any of these methods, a direct connection between them is made.</p>
 
 {%
   include legacy/cardv2.html

_includes/legacy/sections/ios-addons.html

@@ -22,6 +22,8 @@
     </div>
   </div>
 
+</div>
+
 <h2>See also</h2>
 
 <ul>

_includes/legacy/sections/other-mobile-operating-systems.html

@@ -1,4 +1,4 @@
-<h2 id="other_os" class="anchor"><a href="#other_os"><i class="fas fa-link anchor-icon"></i></a> Other Mobile Operating Systems</h1>
+<h2 id="other_os" class="anchor"><a href="#other_os"><i class="fas fa-link anchor-icon"></i></a> Other Mobile Operating Systems</h2>
 
 {% include legacy/cardv2.html
   title="Ubuntu Touch"

index.html

@@ -95,7 +95,6 @@ layout: default
     </div>
   </div>
 </div>
-</div>
 
 <div class="container">
   <div class="row my-5">

legacy_pages/providers/vpn.html

@@ -137,7 +137,6 @@ breadcrumb: "VPN"
       <ul>
           <li>Must self host analytics (no Google Analytics etc). The provider's site must also comply with <a href="https://en.wikipedia.org/wiki/Do_Not_Track">DNT (Do Not Track)</a> for those users who want to opt-out.</li>
       </ul>
-      </li>
       <p>Must not have any marketing which is irresponsible:</p>
         <ul>
           <li>Making guarantees of protecting anonymity 100%. When someone makes a claim that something is 100% it means there is no certainty for failure. We know users can quite easily deanonymize themselves in a number of ways, eg:</li>
@@ -145,7 +144,7 @@ breadcrumb: "VPN"
             <li>Reusing personal information eg. (email accounts, unique pseudonyms etc) that they accessed without anonymity software (Tor, VPN etc)</li>
             <li><a href="https://www.privacytools.io/browsers/#fingerprint">Browser fingerprinting</a></li>
           </ul>
-          <li>Claim that a single circuit VPN is "more anonymous" than Tor, which is a circuit of 3 or more hops that regularly changes.</a></li>
+          <li>Claim that a single circuit VPN is "more anonymous" than Tor, which is a circuit of 3 or more hops that regularly changes.</li>
           <li>Use responsible language, eg it is okay to say that a VPN is "disconnected" or "not connected", however claiming that a user is "exposed", "vulnerable" or "compromised" is needless use of alarming language that may be incorrect. For example the visiting user might be on another VPN provider's service or using Tor.</li>
         </ul>
     </div>