update based on https://github.com/mdn/yari/issues/2028

6 files changed, 0 insertions, 669 deletions

diff --git a/files/nl/mozilla/persona/browser_compatibility/index.html b/files/nl/mozilla/persona/browser_compatibility/index.html
deleted file mode 100644
index 3a41d46459..0000000000
--- a/files/nl/mozilla/persona/browser_compatibility/index.html
+++ /dev/null
@@ -1,103 +0,0 @@
----
-title: Browser compatibiliteit
-slug: Mozilla/Persona/Browser_compatibility
-tags:
-  - Persona
-translation_of: Archive/Mozilla/Persona/Browser_compatibility
----
-<h2 id="Supported_Browsers">Supported Browsers</h2>
-
-<p>Persona is developed, tested, and supported with the following browsers. Thanks to Persona's cross-platform JavaScript library, users do not need add-ons in order to use Persona.</p>
-
-<table>
- <tbody>
-  <tr>
-   <th colspan="3" scope="row" style="text-align: center; background-color: #d3d7cf;"><strong>Desktop Browsers</strong></th>
-  </tr>
-  <tr>
-   <th scope="row"><strong>Internet Explorer</strong></th>
-   <td colspan="2" rowspan="1" style="background-color: #8ae234;">8.0<sup>*</sup>, 9.0<sup>†</sup>, 10.0<sup>*</sup><sup>*</sup> (but see <a href="https://developer.mozilla.org/docs/persona/Browser_compatibility#Internet_Explorer_.22Compatibility_Mode.22" title="https://developer.mozilla.org/docs/persona/Browser_compatibility#Internet_Explorer_.22Compatibility_Mode.22">Compatibility Mode</a> below)</td>
-  </tr>
-  <tr>
-   <th scope="row"><strong>Firefox</strong></th>
-   <td colspan="2" style="background-color: #8ae234;">Current Stable, Beta, Aurora, Nightly, and Extended Support Releases<br>
-    Previous Stable Release</td>
-  </tr>
-  <tr>
-   <th scope="row"><strong>Chrome</strong></th>
-   <td colspan="2" style="background-color: #8ae234;">Latest Stable Release</td>
-  </tr>
-  <tr>
-   <th scope="row"><strong>Safari</strong></th>
-   <td colspan="2" style="background-color: #8ae234;">Latest Stable Release</td>
-  </tr>
-  <tr>
-   <th scope="row"><strong>Opera</strong></th>
-   <td colspan="2" style="background-color: #8ae234;">Latest Stable Release<sup>‡</sup></td>
-  </tr>
-  <tr>
-   <th colspan="3" scope="row" style="text-align: center; background-color: #d3d7cf;"><strong>iOS Browsers</strong></th>
-  </tr>
-  <tr>
-   <th scope="row"><strong>Mobile Safari</strong></th>
-   <td colspan="2" rowspan="1" style="background-color: #8ae234;">iOS 5.x — 6.x</td>
-  </tr>
-  <tr>
-   <th colspan="3" scope="row" style="text-align: center; background-color: #d3d7cf;"><strong>Android Browsers</strong></th>
-  </tr>
-  <tr>
-   <th scope="row"><strong>Default Browser</strong></th>
-   <td colspan="2" rowspan="1" style="background-color: #8ae234;">2.2 — 4.x</td>
-  </tr>
-  <tr>
-   <th scope="row"><strong>Firefox</strong></th>
-   <td colspan="2" style="background-color: #8ae234;">Current Stable, Beta, Aurora, and Nightly Releases<br>
-    Previous Stable Release</td>
-  </tr>
-  <tr>
-   <th scope="row"><strong>Chrome</strong></th>
-   <td colspan="2" style="background-color: #8ae234;">Latest Stable Release</td>
-  </tr>
- </tbody>
-</table>
-
-<p><sup>*</sup>: For Windows XP. <sup>†</sup>: For Windows Vista and Windows 7. <sup>*</sup><sup>*</sup>Windows 8.<sup>  </sup><sup>‡</sup>: As time allows.</p>
-
-<h2 id="Unsupported_Browsers">Unsupported Browsers</h2>
-
-<ul>
- <li>Internet Explorer versions 6.0 and 7.0 are not supported. Users will be prompted to upgrade their browser. Also see the section below on <a href="https://developer.mozilla.org/docs/persona/Browser_compatibility#Internet_Explorer_.22Compatibility_Mode.22" title="https://developer.mozilla.org/docs/persona/Browser_compatibility#Internet_Explorer_.22Compatibility_Mode.22">IE "Compatibility Mode"</a>.</li>
- <li>Google Chrome Frame is not supported and will not function. Support may be added later (<a href="https://github.com/mozilla/browserid/issues/796" title="https://github.com/mozilla/browserid/issues/796">Issue #796</a>).</li>
- <li>Third party browsers on iOS are not supported and will not function. Support may be added later (<a href="https://github.com/mozilla/browserid/issues/2034" title="https://github.com/mozilla/browserid/issues/2034">Issue #2034</a>).</li>
-</ul>
-
-<h2 id="Internet_Explorer_Compatibility_Mode">Internet Explorer "Compatibility Mode"</h2>
-
-<p>From version 8.0 onwards Internet Explorer supports a feature called Compatibility Mode, in which the browser may be instructed to emulate a pre-8.0 version when rendering a page. This feature may be controlled in three different ways</p>
-
-<ol>
- <li>as a local setting in the browser</li>
- <li>based on the presence and value of the <a href="https://developer.mozilla.org/docs/Quirks_Mode_and_Standards_Mode" title="https://developer.mozilla.org/docs/Quirks_Mode_and_Standards_Mode">DOCTYPE</a> declaration in the page</li>
- <li>as an instruction sent from the site, using the <a href="http://msdn.microsoft.com/library/cc288325%28v=vs.85%29.aspx" title="http://msdn.microsoft.com/library/cc288325%28v=vs.85%29.aspx">"X-UA-Compatible"</a> header either as an HTTP header or as a <a href="https://developer.mozilla.org/docs/HTML/Element/meta" title="https://developer.mozilla.org/docs/HTML/Element/meta"><code>&lt;meta&gt;</code></a> tag in the page. This method overrides the other two.</li>
-</ol>
-
-<p>Because versions of Internet Explorer earlier than 8.0 are not supported by Persona, any version of Internet Explorer which is configured to emulate a pre-8.0 version will also not function with Persona. This is typically for one of the following reasons:</p>
-
-<ul>
- <li>your site is using "X-UA-Compatible" to explicitly instruct the browser to emulate a pre-8.0 version</li>
- <li>your site's pages omit the DOCTYPE, do not have the DOCTYPE as the first line of the page, or set the browser to quirks mode, and your site is not setting "X-UA-Compatible" to IE version 8.0 or higher</li>
- <li>the browser is locally configured to use a pre-8.0 Compatibility Mode, and your site is not overriding this by setting "X-UA-Compatible" to IE version 8.0 or higher</li>
-</ul>
-
-<p>For more information, see <a href="https://blogs.msdn.com/b/askie/archive/2009/03/23/understanding-compatibility-modes-in-internet-explorer-8.aspx?Redirected=true" title="https://blogs.msdn.com/b/askie/archive/2009/03/23/understanding-compatibility-modes-in-internet-explorer-8.aspx?Redirected=true">"Understanding Compatibility Modes in Internet Explorer 8"</a> and <a href="http://hsivonen.iki.fi/doctype/index.html#ie8" title="http://hsivonen.iki.fi/doctype/index.html#ie8">"IE8 and IE9 Complications"</a>.</p>
-
-<h2 id="Other_Browsers">Other Browsers</h2>
-
-<p>Despite not being explicitly supported, any browser that includes both {{ domxref("window.postMessage()") }} and {{ domxref("Storage", "localStorage") }} should work. These APIs have been available in all major browsers since March 2010.</p>
-
-<h2 id="Known_Issues">Known Issues</h2>
-
-<ul>
- <li>Browsers must accept third party cookies for full functionality (<a href="https://github.com/mozilla/browserid/issues/1352" title="https://github.com/mozilla/browserid/issues/1352">Issue #1352</a>).</li>
- <li>Android 2.x users without a default browser selected may be unable to log in (<a href="https://github.com/mozilla/browserid/issues/1854" title="https://github.com/mozilla/browserid/issues/1854">Issue #1854</a>).</li>
-</ul>
diff --git a/files/nl/mozilla/persona/huisstijl/index.html b/files/nl/mozilla/persona/huisstijl/index.html
deleted file mode 100644
index 5ac30e82ba..0000000000
--- a/files/nl/mozilla/persona/huisstijl/index.html
+++ /dev/null
@@ -1,49 +0,0 @@
----
-title: Huisstijl hulpbronnen
-slug: Mozilla/Persona/Huisstijl
-tags:
-  - Persona
-  - branding
-  - huisstijl
-  - hulpbronnen
-  - merken
-  - resources
-translation_of: Archive/Mozilla/Persona/User_interface_guidelines
----
-<h2 id="Aanmelden_met_Persona_Knoppen">Aanmelden met Persona Knoppen</h2>
-<h3 id="Afbeeldingen">Afbeeldingen</h3>
-<p>De "Sign in" (aanmelden) knop komt in drie verschillende versies, en drie kleuren:</p>
-<table>
-  <thead>
-    <tr>
-      <th scope="row"> </th>
-      <th scope="col">Sign in with your Email</th>
-      <th scope="col">Sign in with Persona</th>
-      <th scope="col">Sign in</th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr>
-      <th scope="row">Zwart</th>
-      <td><img alt="" src="/files/3955/email_sign_in_black.png" style="width: 202px; height: 25px;"></td>
-      <td><img alt="" src="/files/3961/persona_sign_in_black.png" style="width: 185px; height: 25px;"></td>
-      <td><img alt="" src="/files/3967/plain_sign_in_black.png" style="width: 95px; height: 25px;"></td>
-    </tr>
-    <tr>
-      <th scope="row">Blauw</th>
-      <td><img alt="" src="/files/3957/email_sign_in_blue.png" style="width: 202px; height: 25px;"></td>
-      <td><img alt="" src="/files/3963/persona_sign_in_blue.png" style="width: 185px; height: 25px;"></td>
-      <td><img alt="" src="/files/3969/plain_sign_in_blue.png" style="width: 95px; height: 25px;"></td>
-    </tr>
-    <tr>
-      <th scope="row">Rood</th>
-      <td><img alt="" src="/files/3959/email_sign_in_red.png" style="width: 202px; height: 25px;"></td>
-      <td><img alt="" src="/files/3965/persona_sign_in_red.png" style="width: 185px; height: 25px;"></td>
-      <td><img alt="" src="/files/3971/plain_sign_in_red.png" style="width: 95px; height: 25px;"></td>
-    </tr>
-  </tbody>
-</table>
-<h3 id="CSS-Gebaseerd">CSS-Gebaseerd</h3>
-<p><a href="http://sawyerhollenshead.com/" title="http://sawyerhollenshead.com/">Sawyer Hollenshead</a> heeft een set uitstekende CSS-gebaseerde knoppen gemaakt. <a href="/files/3973/persona-css-buttons.zip" title="/files/3973/persona-css-buttons.zip">Download (.zip)</a></p>
-<h2 id="Meer_informatie">Meer informatie</h2>
-<p>Meer informatie over het visuele ontwerp van Persona is te vinden in <a href="http://people.mozilla.org/~smartell/persona/" title="http://people.mozilla.org/~smartell/persona/">Sean Martells style primer</a>.</p>
diff --git a/files/nl/mozilla/persona/index.html b/files/nl/mozilla/persona/index.html
deleted file mode 100644
index 079b7e8072..0000000000
--- a/files/nl/mozilla/persona/index.html
+++ /dev/null
@@ -1,196 +0,0 @@
----
-title: Persona
-slug: Mozilla/Persona
-tags:
-  - Persona
-translation_of: Archive/Mozilla/Persona
----
-<p></p><div class="warning">  <p>Op 30 november 2016 zal Mozilla de services van persona.org stopzetten. Persona.org en gerelateerde domeinen zullen offline worden gehaald.</p>  <p>Bekijk voor meer informatie deze handleiding voor het migreren van uw website vanaf Persona:</p>  <p><a href="https://wiki.mozilla.org/Identity/Persona_Shutdown_Guidelines_for_Reliers">https://wiki.mozilla.org/Identity/Persona_Shutdown_Guidelines_for_Reliers</a></p></div><p></p>
-
-<div class="summary">Eenvoudige, privacygevoelige eenmalige aanmelding: laat uw gebruikers zich bij uw website aanmelden met hun e-mailadres, en verlos uzelf van wachtwoordbeheer.</div>
-
-<div class="column-container">
-<p><span class="seoSummary"><a href="https://login.persona.org/">Mozilla Persona</a> is een browseronafhankelijk aanmeldingssysteem voor het internet dat eenvoudig is te gebruiken en uit te rollen. Het werkt in <a href="/nl/docs/Mozilla/Persona/Browser_compatibility">alle grote browsers</a>, en u kunt <a href="/nl/docs/Mozilla/Persona/Quick_Setup">er direct mee beginnen</a>.</span></p>
-
-<p>Waarom zou u Persona op uw website gebruiken?</p>
-
-<ol>
- <li><strong>Persona maakt een einde aan wachtwoorden voor elke website</strong>, en zorgt ervoor dat gebruikers geen wachtwoorden meer hoeven te bedenken, te beheren en veilig te bewaren.</li>
- <li><strong>Persona is makkelijk te gebruiken.</strong> Met twee muisklikken kan een gebruiker zich aanmelden bij een nieuwe website, zoals <a href="http://voo.st">Voost</a>, waarbij extra handelingen om een account aan te maken worden overgeslagen.</li>
- <li><strong>Persona is makkelijk te implementeren</strong><strong>. </strong>Ontwikkelaars kunnen in slechts één middag Persona aan hun website toevoegen.</li>
- <li><strong>Er is geen afhankelijkheid</strong>. Ontwikkelaars krijgen van iedere gebruiker een geverifieerd e-mailadres, en gebruikers kunnen elk e-mailadres gebruiken.</li>
-</ol>
-
-<p>Daarbij wordt Persona alleen nog maar beter: het is gebouwd op een <strong>open, gedecentraliseerd protocol</strong>, dat is ontworpen voor <strong>directe integratie in browsers</strong> en <strong>ingebouwde ondersteuning door e-mailproviders</strong>. Websites die Persona vandaag implementeren, zullen automatisch verbeteringen ervaren zonder code te hoeven wijzigen.</p>
-</div>
-
-<hr>
-<div class="column-container">
-<h2 id="Persona_op_uw_website_gebruiken">Persona op uw website gebruiken</h2>
-
-<div class="column-third">
-<h3 id="Beginnen">Beginnen</h3>
-
-<dl>
- <dt><a href="/nl/docs/Mozilla/Persona/Why_Persona">Waarom Persona?</a></dt>
- <dd>Wat er bijzonder is aan Persona in vergelijking met andere gebruikers- en authenticatiesystemen.</dd>
- <dt><a href="/nl/docs/Mozilla/Persona/Quick_Setup">Snelle installatie</a></dt>
- <dd>Een stap-voor-stap handleiding die toont hoe u Persona aan uw website toevoegt.</dd>
-</dl>
-
-<h3 id="API-verwijzing">API-verwijzing</h3>
-
-<dl>
- <dt><a href="/nl/docs/Mozilla/Persona/The_navigator.id_API">De navigator.id-API</a></dt>
- <dd>De browser-API.</dd>
- <dt><a href="/nl/docs/Mozilla/Persona/Remote_Verification_API">Naslag over de verificatie-API</a></dt>
- <dd>De API voor externe verificatie.</dd>
-</dl>
-</div>
-
-<div class="column-third">
-<h3 id="Handleidingen">Handleidingen</h3>
-
-<dl>
- <dt><a href="/nl/docs/Mozilla/Persona/Security_Considerations">Veiligheidsoverwegingen</a></dt>
- <dd>Methoden en technieken die ervoor zorgen dat uw Persona-implementatie veilig is.</dd>
- <dt><a href="/nl/docs/Mozilla/Persona/Browser_compatibility">Browsercompatibiliteit</a></dt>
- <dd>Lees hier welke browsers Persona ondersteunen.</dd>
- <dt><a href="/nl/docs/Mozilla/Persona/Internationalization">Internationalisatie</a></dt>
- <dd>Lees hier hoe Persona met verschillende talen omgaat.</dd>
- <dt><a href="/nl/docs/Mozilla/Persona/The_implementor_s_guide">Tips voor implementatie</a></dt>
- <dd>Tips van websites die ondersteuning voor Persona hebben toegevoegd.</dd>
-</dl>
-</div>
-
-<div class="column-third">
-<h3 id="Hulpmiddelen">Hulpmiddelen</h3>
-
-<dl>
- <dt><a href="/nl/docs/Mozilla/Persona/Libraries_and_plugins">Bibliotheken en plug-ins</a></dt>
- <dd>Vind een kant-en-klare bibliotheek voor uw favoriete programmeertaal, webframework, blog of inhoudsbeheersysteem.</dd>
- <dt><a class="link-https" href="https://github.com/mozilla/browserid-cookbook">The Persona cookbook</a></dt>
- <dd>Voorbeeldbroncode voor Persona-websites. Bevat onderdelen in C# (MVC3), PHP, Node.JS en meer.</dd>
- <dt><a href="/nl/docs/Mozilla/Persona/User_interface_guidelines">Richtlijnen voor de gebruikersinterface</a></dt>
- <dd>Persona-aanmelding aanbieden aan gebruikers.</dd>
-</dl>
-</div>
-</div>
-
-<hr>
-<h2 id="Een_Identity_Provider_worden">Een Identity Provider worden</h2>
-
-<p>Als u een e-mailprovider of een andere identiteitsproviderservice bent, bekijk dan de koppelingen voor meer informatie over het worden van een Persona Identity Provider.</p>
-
-<div class="column-container">
-<div class="column-third">
-<dl>
- <dt><a href="/nl/docs/Mozilla/Persona/Identity_Provider_Overview">IdP-overzicht</a></dt>
- <dd>Een beknopte uitleg over Persona Identity Providers.</dd>
-</dl>
-</div>
-
-<div class="column-third">
-<dl>
- <dt><a href="/nl/docs/Mozilla/Persona/Implementing_a_Persona_IdP">Een IdP implementeren</a></dt>
- <dd>Een gedetailleerde handleiding met technische details over het worden van een IdP.</dd>
-</dl>
-</div>
-
-<div class="column-third">
-<dl>
- <dt><a href="/nl/docs/Mozilla/Persona/.well-known-browserid">.well-known/browserid</a></dt>
- <dd>Een overzicht van het bestand <code>.well-known/browserid</code>, dat IdP’s gebruiken om aan te geven dat ze het protocol ondersteunen.</dd>
-</dl>
-</div>
-</div>
-
-<hr>
-<h2 id="Het_Persona-project">Het Persona-project</h2>
-
-<div class="column-container">
-<div class="column-third">
-<dl>
- <dt><a href="/nl/docs/Mozilla/Persona/Glossary">Woordenlijst</a></dt>
- <dd>BrowserID- en Persona-begrippen uitgelegd.</dd>
- <dt><a href="/nl/docs/Mozilla/Persona/FAQ">FAQ</a></dt>
- <dd>Antwoorden op veelgestelde vragen.</dd>
- <dt><a href="/nl/docs/Mozilla/Persona/Protocol_Overview">Protocoloverzicht</a></dt>
- <dd>Een technisch overzicht op gemiddeld niveau van het onderliggende BrowserID-protocol.</dd>
-</dl>
-</div>
-
-<div class="column-third">
-<dl>
- <dt><a href="/nl/docs/Mozilla/Persona/Crypto">Versleuteling</a></dt>
- <dd>Een blik op de cryptografische concepten achter Persona en BrowserID.</dd>
- <dt><a class="link-https" href="https://github.com/mozilla/id-specs/blob/prod/browserid/index.md">De specificaties</a></dt>
- <dd>Gedetailleerde technische details zijn hier te vinden.</dd>
-</dl>
-</div>
-
-<div class="column-third">
-<dl>
- <dt><a href="/nl/docs/Mozilla/Persona/Bootstrapping_Persona">De Persona-website</a></dt>
- <dd>Om Persona online te houden, hosten we drie services op <a class="link-https" href="https://login.persona.org" rel="freelink">https://login.persona.org</a>: een fallback-Identity Provider, een implementatie van de <a href="/nl/docs/Web/API/Navigator/id" title="The documentation about this has not yet been written; please consider contributing!"><code>navigator.id</code></a> API’s, en een verificatieservice.</dd>
- <dt><a href="https://github.com/mozilla/browserid">De Persona-broncode</a></dt>
- <dd>De code van Persona bevindt zich op GitHub. Wijzigingen via Pull requests zijn welkom!</dd>
-</dl>
-</div>
-</div>
-
-<p></p><div class="overheadIndicator communitybox" dir="ltr">
-
-    <div class="column-container">
-        <h2 id="Join_the_Identity_community">Join the Identity community</h2>
-        <div class="column-half">
-            <div class="communitysubhead">Choose your preferred method for joining the discussion:</div>
-            <ul class="communitymailinglist">
-  <li><a href="https://lists.mozilla.org/listinfo/dev-identity">Mailing list</a></li>
-
-
-  <li><a href="http://groups.google.com/group/mozilla.dev.identity">Newsgroup</a></li>
-  <li><a href="http://groups.google.com/group/mozilla.dev.identity/feeds">RSS feed</a></li>
-</ul>
-        </div>
-        <div class="column-half">
-            <ul class="communitycontact"><li><strong>IRC: </strong><a href="irc://irc.mozilla.org/identity">#identity</a> <span class="smaller">(<a href="https://wiki.mozilla.org/IRC">learn more</a>)</span></li><li><strong>Blog: </strong><a href="http://identity.mozilla.com/" title="Bezoek het Identity-blog">identity.mozilla.com</a></li><li><strong>GitHub: </strong><a href="https://github.com/mozilla/browserid/issues/new" title="Een bug melden">een bug melden</a></li></ul>
-        </div>
-    </div>
-</div><p></p>
-
-<h2 id="Subnav">Subnav</h2>
-
-<ol>
- <li><a href="#">Persona op een website gebruiken</a>
-
-  <ol>
-   <li><a href="/nl/docs/Mozilla/Persona/Why_Persona" title="Waarom Persona?">Waarom zou u Persona gebruiken?</a></li>
-   <li><a href="/nl/docs/Mozilla/Persona/Quick_setup" title="Snelle start">Beginnen</a></li>
-   <li><a href="/nl/docs/Mozilla/Persona/The_implementor_s_guide" title="Handleiding voor implementatie">Tips voor implementatie van Persona</a></li>
-   <li><a href="/nl/docs/Mozilla/Persona/Security_Considerations" title="Veiligheidsoverwegingen">Veiligheidsoverwegingen</a></li>
-   <li><a href="/nl/docs/Mozilla/Persona/Browser_compatibility" title="Browsercompatibiliteit">Browsercompatibiliteit</a></li>
-   <li><a href="/nl/docs/Mozilla/Persona/Internationalization" title="Internationalisatie">Internationalisatie</a></li>
-   <li><a href="/nl/docs/Mozilla/Persona/The_navigator.id_API" title="De navigator.id-API">De navigator.id-API</a></li>
-   <li><a href="/nl/docs/Mozilla/Persona/Remote_Verification_API" title="API voor externe verificatie">De API voor externe verificatie</a></li>
-   <li><a href="/nl/docs/Mozilla/Persona/Libraries_and_plugins" title="Bibliotheken en plug-ins">Bibliotheken en plug-ins</a></li>
-   <li><a href="/nl/docs/Mozilla/Persona/User_interface_guidelines" title="Richtlijnen voor de gebruikersinterface">Richtlijnen voor de gebruikersinterface</a></li>
-  </ol>
- </li>
- <li><a href="#">Een Identity Provider worden</a>
-  <ol>
-   <li><a href="/nl/docs/Mozilla/Persona/Identity_Provider_Overview" title="IdP-overzicht">IdP-overzicht</a></li>
-   <li><a href="/nl/docs/Mozilla/Persona/Implementing_a_Persona_IdP" title="Een IdP implementeren">Een idP implementeren</a></li>
-   <li><a href="/nl/docs/Mozilla/Persona/.well-known-browserid" title="Opmaak van .well-known-browserid">Opmaak van .well-known-browserid</a></li>
-  </ol>
- </li>
- <li><a href="#">Het Persona-project</a>
-  <ol>
-   <li><a href="/nl/docs/Mozilla/Persona/Glossary" title="Woordenlijst">Woordenlijst</a></li>
-   <li><a href="/nl/docs/Mozilla/Persona/FAQ" title="FAQ">FAQ</a></li>
-   <li><a href="/nl/docs/Mozilla/Persona/Bootstrapping_Persona" title="Door Persona gehoste services">Door Persona gehoste services</a></li>
-   <li><a href="/nl/docs/Mozilla/Persona/Protocol_Overview" title="Protocoloverzicht">Protocoloverzicht</a></li>
-   <li><a href="/nl/docs/Mozilla/Persona/Crypto" title="Versleuteling">Versleuteling</a></li>
-  </ol>
- </li>
-</ol>
diff --git a/files/nl/mozilla/persona/protocol_overview/index.html b/files/nl/mozilla/persona/protocol_overview/index.html
deleted file mode 100644
index cf8c729edf..0000000000
--- a/files/nl/mozilla/persona/protocol_overview/index.html
+++ /dev/null
@@ -1,61 +0,0 @@
----
-title: Protocol Overview
-slug: Mozilla/Persona/Protocol_Overview
-translation_of: Archive/Mozilla/Persona/Protocol_Overview
----
-<p>Persona is built on the BrowserID protocol. This page describes the BrowserID protocol at a high level.</p>
-<h2 id="Actors">Actors</h2>
-<p>The protocol involves three actors:</p>
-<ul>
-  <li><strong>Users:</strong> The actual people that want to sign into websites using Persona.</li>
-  <li><strong>Relying Parties (RPs): </strong>Websites that want to let users sign in using Persona.</li>
-  <li><strong>Identity Providers (IdPs): </strong>Domains that can issue Persona-compatible identity certificates to their users.</li>
-</ul>
-<p>Persona and the BrowserID protocol use email addresses as identities, so it's natural for email providers to become IdPs.</p>
-<p>Mozilla operates a fallback IdP so that users can use any email address with Persona, even one with a specific domain that isn't an IdP itself.</p>
-<h2 id="Protocol_Steps">Protocol Steps</h2>
-<p>There are three distinct steps in the protocol:</p>
-<ol>
-  <li>User Certificate Provisioning</li>
-  <li>Assertion Generation</li>
-  <li>Assertion Verification</li>
-</ol>
-<p>As a prerequisite, the user should have an active identity (email address) that they wish to use when logging in to websites. The protocol does not require that IdP-backed identities are SMTP-routable, but it does require that identities follow the <code>user@domain</code> format.</p>
-<h3 id="User_Certificate_Provisioning">User Certificate Provisioning</h3>
-<p>In order to sign into an RP, a user must be able to prove ownership of their preferred email address. The foundation of this proof is a cryptographically signed certificate from an IdP certifying the connection between a browser's user and a given identity within the IdP's domain.</p>
-<p>Because Persona uses standard <a href="http://en.wikipedia.org/wiki/Public-key_cryptography" title="http://en.wikipedia.org/wiki/Public-key_cryptography">public key cryptography</a> techniques, the user certificate is signed by the IdP's private key and contains:</p>
-<ul>
-  <li>The user's email address.</li>
-  <li>The user's public key for that address on that browser.</li>
-  <li>The time that the certificate was issued.</li>
-  <li>The time that the certificate expires.</li>
-  <li>The IdP's domain name.</li>
-</ul>
-<p>The user's browser generates a different keypair for each of the user's email addresses, and these keypairs are not shared across browsers. Thus, a user must obtain a fresh certificate whenever one expires, or whenever using a new browser or computer. Certificates must expire within 24 hours of being issued.</p>
-<p>When a user selects an identity to use when signing into an RP, the browser checks to see if it has a fresh user certificate for that address. If it does, this step is complete and the browser continues with the assertion generation step below. If the browser does not have a fresh certificate, it attempts to obtain one from the domain associated with the chosen identity.</p>
-<ol>
-  <li>The browser fetches the <a href="/en-US/docs/Persona/.well-known-browserid" title="/en-US/docs/Persona/.well-known-browserid">/.well-known/browserid</a> support document over SSL from the identity's domain.</li>
-  <li>Using information from the support document, the browser passes the user's email address and associated public key to the IdP and requests a signed certificate.</li>
-  <li>If necessary, the user is asked to sign into the IdP before provisioning proceeds.</li>
-  <li>The IdP creates, signs, and gives a user certificate to the user's browser.</li>
-</ol>
-<p>With the certificate in hand, the browser can continue with generating an identity assertion and signing into an RP.</p>
-<p><img alt="user-certificate-provisioning.png" class="internal default" src="/@api/deki/files/6043/=user-certificate-provisioning.png"></p>
-<h3 id="Assertion_Generation">Assertion Generation</h3>
-<p>The user certificate establishes a verifiable link between an email address and a public key. However, this is alone not enough to log into a website: the user still has to show their connection to the certificate by proving ownership of the private key.</p>
-<p>In order to prove ownership of a private key, the user's browser creates and signs a new document called an "identity assertion." It contains:</p>
-<ul>
-  <li>The domain of the RP that the user wants to sign into.</li>
-  <li>An expiration time for the assertion, generally less than five minutes after it was created.</li>
-</ul>
-<p>The browser then presents both the user certificate and the identity assertion to the RP for verification.</p>
-<h3 id="Assertion_Verification">Assertion Verification</h3>
-<p>The combination of user certificate and identity assertion is sufficient to confirm a user's identity.</p>
-<p>First, the RP checks the domain and expiration time in the assertion. If the assertion is expired or intended for a different domain, it's rejected. This prevents malicious re-use of assertions.</p>
-<p>Second, the RP validates the signature on the assertion with the public key inside the user certificate. If the key and signature match, the RP is assured that the current user really does possess the key associated with the certificate.</p>
-<p>Last, the RP fetches the IdP's public key from its <a href="/en-US/docs/Persona/.well-known-browserid" title="/en-US/docs/Persona/.well-known-browserid">/.well-known/browserid</a> document and verifies that it matches the signature on the user certificate. If it does, then the RP can be certain that the certificate really was issued by the domain in question.</p>
-<p>Once verifying that this is a current login attempt for the proper RP, that the user certificate matches the current user, and that the user certificate is legitimate, the RP is done and can authenticate the user as the identity contained in the certificate.</p>
-<p><img alt="assertion-generation-and-verify.png" class="internal default" src="/@api/deki/files/6042/=assertion-generation-and-verify.png"></p>
-<h2 id="The_Persona_Fallback_IdP">The Persona Fallback IdP</h2>
-<p>What if a user's email provider doesn't support Persona? In that case, the provisioning step would fail. By convention, the user's browser handles this by asking a trusted third party, <a href="https://login.persona.org/" title="https://login.persona.org/">https://login.persona.org/</a>, to certify the user's identity on behalf of the unsupported domain. After demonstrating ownership of the address, the user would then receive a certificate issued by the fallback IdP, <code>login.persona.org</code>, rather than the identity's domain.</p>
-<p>RPs follow a similar process when validating the assertion: the RP would ultimately request the fallback IdP's public key in order to verify the certificate.</p>
diff --git a/files/nl/mozilla/persona/quick_setup/index.html b/files/nl/mozilla/persona/quick_setup/index.html
deleted file mode 100644
index 1b29167556..0000000000
--- a/files/nl/mozilla/persona/quick_setup/index.html
+++ /dev/null
@@ -1,199 +0,0 @@
----
-title: Quick Setup
-slug: Mozilla/Persona/Quick_Setup
-translation_of: Archive/Mozilla/Persona/Quick_Setup
----
-<p>Adding the Persona login system to your site takes just five steps:</p>
-<ol>
- <li>Include the Persona JavaScript library on your pages.</li>
- <li>Add “login” and “logout” buttons.</li>
- <li>Watch for login and logout actions.</li>
- <li>Verify the user’s credentials.</li>
- <li>Review best practices.</li>
-</ol>
-<p>You should be able to get up and running in a single afternoon, but first things first: If you’re going to use Persona on your site, <em>please</em> take a moment and subscribe to the <a href="https://mail.mozilla.org/listinfo/persona-notices">Persona notices</a> mailing list. It’s extremely low traffic, only being used to announce changes or security issues which may adversely impact your site.</p>
-<h2 id="Step_1_Include_the_Persona_library">Step 1: Include the Persona library</h2>
-<p>Persona is designed to be browser-neutral and works well on <a href="https://developer.mozilla.org/docs/persona/Browser_compatibility">all major desktop and mobile browsers</a>.</p>
-<p>In the future we expect browsers to provide native support for Persona, but in the meantime we provide a JavaScript library that fully implements the user interface and client-side part of the protocol. By including this library, your users will be able to sign in with Persona whether or not their browser has native support.</p>
-<p>Once this library is loaded in your page, the Persona functions you need ({{ domxref("navigator.id.watch()", "watch()") }}, {{ domxref("navigator.id.request()", "request()") }}, and {{ domxref("navigator.id.logout()", "logout()") }}) will be available in the global <code>navigator.id</code> object.</p>
-<p>To include the Persona JavaScript library, you can place this <code>script</code> tag at the bottom of the page body:</p>
-<pre class="brush: html;">&lt;script src="https://login.persona.org/include.js"&gt;&lt;/script&gt;
-</pre>
-<p>You <strong>must</strong> include this on every page which uses {{ domxref("navigator.id") }} functions. Because Persona is still in development, you should not self-host the <code>include.js</code> file.</p>
-<h3 id="Suppressing_Compatibility_Mode">Suppressing Compatibility Mode</h3>
-<p>You should also make sure users of Internet Explorer can't use Compatibility Mode, as this will break Persona. To do this:</p>
-<ul>
- <li>either include <code>&lt;meta http-equiv="X-UA-Compatible" content="IE=Edge"&gt;</code> on your page, before any script elements</li>
- <li>or set the following HTTP header on your page: <code>X-UA-Compatible: IE=Edge</code>.</li>
-</ul>
-<p>For more information, see the notes in <a href="/en-US/docs/persona/Browser_compatibility#Internet_Explorer_.22Compatibility_Mode.22" title="/en-US/docs/persona/Browser_compatibility#Internet_Explorer_.22Compatibility_Mode.22">IE Compatibility Mode</a> and <a href="http://hsivonen.iki.fi/doctype/index.html#ie8" title="http://hsivonen.iki.fi/doctype/index.html#ie8">"IE8 and IE9 Complications"</a>.</p>
-<h2 id="Step_2_Add_login_and_logout_buttons">Step 2: Add login and logout buttons</h2>
-<p>Because Persona is designed as a DOM API, you must call functions when a user clicks a login or logout button on your site. To open the Persona dialog and prompt the user to log in, you should invoke {{ domxref("navigator.id.request()") }}. For logout, invoke {{ domxref("navigator.id.logout()") }}. Note, the call to {{ domxref("navigator.id.logout()", "logout()") }} <em>must</em> be made in the click handler of the logout button.</p>
-<p>For example:</p>
-<pre class="brush: js;">var signinLink = document.getElementById('signin');
-if (signinLink) {
-  signinLink.onclick = function() { navigator.id.request(); };
-}
-
-var signoutLink = document.getElementById('signout');
-if (signoutLink) {
-  signoutLink.onclick = function() { navigator.id.logout(); };
-}
-</pre>
-<p>What should those buttons look like? Check out our <a href="https://developer.mozilla.org/docs/persona/branding">Branding Resources</a> page for premade images and CSS-based buttons!</p>
-<h2 id="Step_3_Watch_for_login_and_logout_actions">Step 3: Watch for login and logout actions</h2>
-<p>For Persona to function, you need to tell it what to do when a user logs in or out. This is done by calling the {{ domxref("navigator.id.watch()") }} function and supplying three parameters:</p>
-<ol>
- <li>
-  <p>The email address of the user currently logged into your site from this computer, or <code>null</code> if no one is logged in. For example, you might examine the browser's cookies to determine who is signed in.</p>
- </li>
- <li>
-  <p>A function to invoke when an <code>onlogin</code> action is triggered. This function is passed a single parameter, an “identity assertion,” which must be verified.</p>
- </li>
- <li>
-  <p>A function to invoke when an <code>onlogout</code> action is triggered. This function is not passed any parameters.</p>
- </li>
-</ol>
-<div class="note style-wrap">
- <p><strong>Note:</strong> You must always include both <code>onlogin</code> and <code>onlogout</code> when you call {{ domxref("navigator.id.watch()") }}.</p>
-</div>
-<p>For example, if you currently think Bob is logged into your site, you might do this:</p>
-<pre class="brush: js;">var currentUser = 'bob@example.com';
-
-navigator.id.watch({
-  loggedInUser: currentUser,
-  onlogin: function(assertion) {
-    // A user has logged in! Here you need to:
-    // 1. Send the assertion to your backend for verification and to create a session.
-    // 2. Update your UI.
-    $.ajax({ /* &lt;-- This example uses jQuery, but you can use whatever you'd like */
-      type: 'POST',
-      url: '/auth/login', // This is a URL on your website.
-      data: {assertion: assertion},
-      success: function(res, status, xhr) { window.location.reload(); },
-      error: function(xhr, status, err) {
-        navigator.id.logout();
-        alert("Login failure: " + err);
-      }
-    });
-  },
-  onlogout: function() {
-    // A user has logged out! Here you need to:
-    // Tear down the user's session by redirecting the user or making a call to your backend.
-    // Also, make sure loggedInUser will get set to null on the next page load.
-    // (That's a literal JavaScript null. Not false, 0, or undefined. null.)
-    $.ajax({
-      type: 'POST',
-      url: '/auth/logout', // This is a URL on your website.
-      success: function(res, status, xhr) { window.location.reload(); },
-      error: function(xhr, status, err) { alert("Logout failure: " + err); }
-    });
-  }
-});
-</pre>
-<p>In this example, both <code>onlogin</code> and <code>onlogout</code> are implemented by making an asynchronous <code>POST</code> request to your site’s backend. The backend then logs the user in or out, usually by setting or deleting information in a session cookie. Then, if everything checks out, the page reloads to take into account the new login state.</p>
-<p>Note that if the identity assertion can't be verified, you should call {{ domxref("navigator.id.logout()") }}: this has the effect of telling Persona that none is currently logged in. If you don't do this, then Persona may immediately call onlogin again with the same assertion, and this can lead to an <a href="/en-US/docs/Persona/The_implementor_s_guide/Call_logout()_after_a_failed_login" title="/en-US/docs/Persona/The_implementor_s_guide/Call_logout()_after_a_failed_login">endless loop of failed logins</a>.</p>
-<p>You can, of course, use AJAX to implement this without reloading or redirecting, but that’s beyond the scope of this tutorial.</p>
-<p>Here is another example, this time not using jQuery.</p>
-<pre class="brush: js;">function simpleXhrSentinel(xhr) {
-    return function() {
-        if (xhr.readyState == 4) {
-            if (xhr.status == 200){
-                // reload page to reflect new login state
-                window.location.reload();
-              }
-            else {
-                navigator.id.logout();
-                alert("XMLHttpRequest error: " + xhr.status);
-              }
-            }
-          }
-        }
-
-function verifyAssertion(assertion) {
-    // Your backend must return HTTP status code 200 to indicate successful
-    // verification of user's email address and it must arrange for the binding
-    // of currentUser to said address when the page is reloaded
-    var xhr = new XMLHttpRequest();
-    xhr.open("POST", "/xhr/sign-in", true);
-    // see http://www.openjs.com/articles/ajax_xmlhttp_using_post.php
-    var param = "assertion="+assertion;
-    xhr.setRequestHeader("Content-type", "application/x-www-form-urlencoded");
-    xhr.setRequestHeader("Content-length", param.length);
-    xhr.setRequestHeader("Connection", "close");
-    xhr.send(param); // for verification by your backend
-
-    xhr.onreadystatechange = simpleXhrSentinel(xhr); }
-
-function signoutUser() {
-    // Your backend must return HTTP status code 200 to indicate successful
-    // sign out (usually the resetting of one or more session variables) and
-    // it must arrange for the binding of currentUser to 'null' when the page
-    // is reloaded
-    var xhr = new XMLHttpRequest();
-    xhr.open("GET", "/xhr/sign-out", true);
-    xhr.send(null);
-    xhr.onreadystatechange = simpleXhrSentinel(xhr); }
-
-// Go!
-navigator.id.watch( {
-    loggedInUser: currentUser,
-         onlogin: verifyAssertion,
-        onlogout: signoutUser } );
-</pre>
-<p>You <strong>must</strong> call <code>navigator.id.watch()</code> on every page with a login or logout button. To support Persona enhancements like automatic login and global logout for your users, you <strong>should</strong> call this function on every page of your site.</p>
-<p>Persona will compare the email address you've passed into <code>loggedInUser</code> with its own knowledge of whether a user is currently logged in, and who they are. If these don't match, it may automatically invoke <code>onlogin</code> or <code>onlogout</code> on page load.</p>
-<p> </p>
-<h2 id="Step_4_Verify_the_user’s_credentials">Step 4: Verify the user’s credentials</h2>
-<p>Instead of passwords, Persona uses “identity assertions,” which are kind of like single-use, single-site passwords combined with the user’s email address. When a user wants to log in, your <code>onlogin</code> callback will be invoked with an assertion from that user. Before you can log them in, you must verify that the assertion is valid.</p>
-<p>It’s <em>extremely important</em> that you verify the assertion on your server, and not in JavaScript running on the user’s browser, since that would be easy to forge. The example above handed off the assertion to the site’s backend by using jQuery’s <code>$.ajax()</code> helper to <code>POST</code> it to <code>/auth/login</code>.</p>
-<p>Once your server has an assertion, how do you verify it? The easiest way is to use a helper service provided by Mozilla. Simply <code>POST</code> the assertion to <code>https://verifier.login.persona.org/verify</code> with two parameters:</p>
-<ol>
- <li><code>assertion</code>: The identity assertion provided by the user.</li>
- <li><code>audience</code>: The hostname and port of your website. You must hardcode this value in your backend; do not derive it from any data supplied by the user.</li>
-</ol>
-<p>For example, if you’re <code>example.com</code>, you can use the command line to test an assertion with:</p>
-<pre class="brush: bash;">$ curl -d "assertion=&lt;ASSERTION&gt;&amp;audience=https://example.com:443" "https://verifier.login.persona.org/verify"
-</pre>
-<p>If it’s valid, you’ll get a JSON response like this:</p>
-<pre class="brush: js;">{
-  "status": "okay",
-  "email": "bob@eyedee.me",
-  "audience": "https://example.com:443",
-  "expires": 1308859352261,
-  "issuer": "eyedee.me"
-}
-</pre>
-<p>You can learn more about the verification service by reading <a href="https://developer.mozilla.org/en-US/docs/BrowserID/Remote_Verification_API">The Verification Service API</a>. An example <code>/auth/login</code> implementation, using <a href="http://python.org/">Python</a>, the <a href="http://flask.pocoo.org/">Flask</a> web framework, and the <a href="http://python-requests.org">Requests</a> HTTP library might look like this:</p>
-<pre class="brush: python;">@app.route('/auth/login', methods=['POST'])
-def login():
-    # The request has to have an assertion for us to verify
-    if 'assertion' not in request.form:
-        abort(400)
-
-    # Send the assertion to Mozilla's verifier service.
-    data = {'assertion': request.form['assertion'], 'audience': 'https://example.com:443'}
-    resp = requests.post('https://verifier.login.persona.org/verify', data=data, verify=True)
-
-    # Did the verifier respond?
-    if resp.ok:
-        # Parse the response
-        verification_data = json.loads(resp.content)
-
-        # Check if the assertion was valid
-        if verification_data['status'] == 'okay':
-            # Log the user in by setting a secure session cookie
-            session.update({'email': verification_data['email']})
-            return 'You are logged in'
-
-    # Oops, something failed. Abort.
-    abort(500)
-</pre>
-<p>For examples of how to use Persona in other languages, have a look at the <a href="https://github.com/mozilla/browserid-cookbook" title="https://github.com/mozilla/browserid-cookbook">cookbook</a>.</p>
-<p>The session management is probably very similar to your existing login system. The first big change is in verifying the user’s identity by checking an assertion instead of checking a password. The other big change is ensuring that the user’s email address is available for use as the <code>loggedInUser</code> parameter to {{ domxref("navigator.id.watch()") }}.</p>
-<p>Logout is simple: you just need to remove the user’s session cookie.</p>
-<h2 id="Step_5_Review_best_practices">Step 5: Review best practices</h2>
-<p>Once everything works and you’ve successfully logged into and out of your site, you should take a moment to review <a href="https://developer.mozilla.org/docs/BrowserID/Security_Considerations">best practices</a> for using Persona safely and securely.</p>
-<p>If you're making a production site, have a look at the <a href="/en-US/docs/Persona/The_implementor_s_guide" title="/en-US/docs/Persona/The_implementor_s_guide">implementor's guide</a>, where we've collected tips for adding the kind of features often needed in real-world login systems.</p>
-<p>Lastly, don’t forget to sign up for the <a href="https://mail.mozilla.org/listinfo/persona-notices">Persona notices</a> mailing list so you’re notified of any security issues or backwards incompatible changes to the Persona API. The list is extremely low traffic: it’s only used to announce changes which may adversely impact your site.</p>
-<p> </p>
diff --git a/files/nl/mozilla/persona/samenvatting/index.html b/files/nl/mozilla/persona/samenvatting/index.html
deleted file mode 100644
index 4fd1ce21bd..0000000000
--- a/files/nl/mozilla/persona/samenvatting/index.html
+++ /dev/null
@@ -1,61 +0,0 @@
----
-title: Woordenlijst
-slug: Mozilla/Persona/Samenvatting
-translation_of: Archive/Mozilla/Persona/Glossary
----
-<h2 id="‘Persona’_vs._‘BrowserID’">‘Persona’ vs. ‘BrowserID’</h2>
-<p>Persona is een volledige implementatie van een nieuw gedistribueerd aanmeldingssysteem van Mozilla.</p>
-<p>BrowserID is het open protocol dat bepaalt hoe Persona werkt.</p>
-<h2 id="Veelgebruikte_Persona-terminologie">Veelgebruikte Persona-terminologie</h2>
-  <dl>
-  <dt>
-     BrowserID</dt>
-   <dd>
-     Een open, gedecentraliseerd protocol voor het athenticeren van gebruikers, gebaseerd op e-mailadressen.</dd>
-   <dt>
-     Identity Provider (‘IdP’)</dt>
-   <dd>
-     Services die referenties aan hun gebruikers uitgeven.</dd>
-   <dd>
-     E-mailproviders kunnen Identity Providers voor hun gebruikers worden door ondersteuning voor het BrowserID-authenticatieprotocol aan hun service toe te voegen. Als een e-mailprovider geen Persona ondersteunt, werkt Mozilla als een terugval-Identity Provider op <a class="link-https" href="https://login.persona.org" title="https://login.persona.org">login.persona.org</a>.</dd>
-   <dt>
-     login.persona.org</dt>
-   <dd>
-     Een terugval-Identity Provider die wordt gehost door het Identity-team bij Mozilla.</dd>
-   <dt>
-     Persona</dt>
-   <dd>
-     De voor de gebruiker zichtbare naam van een complex pakket aan identiteitsgerelateerd services van Mozilla, waaronder de door Mozilla beheerde terugval-Identity Provider. Eindgebruikers horen de term ‘BrowserID’ nooit te zien.</dd>
-   <dd>
-     Persona kan uiteindelijk functies bevatten die verder gaan dan het BrowserID-protocol, zoals onderdelen van Firefox Sync of een dashboard voor Open webapps.</dd>
-   <dt>
-     Relying Party (‘RP’)</dt>
-   <dd>
-     Websites, toepassingen of services waarmee gebruikers zich kunnen aanmelden via Persona.</dd>
-</dl>
-<h2 id="Projectcodenamen">Projectcodenamen</h2>
-<dl>
-  <dt>
-    BigTent</dt>
-  <dd>
-    Een pakket met drie terugval-Identity Providers die instaan voor gebruikers van respectievelijk Hotmail, Gmail en Yahoo Mail. BigTent werkt door voor elke e-mailprovider het BrowserID-protocol te ‘bridgen’ met OpenID of OAuth. De broncode is beschikbaar op <a href="https://github.com/mozilla/browserid-bigtent" title="https://github.com/mozilla/browserid-bigtent">https://github.com/mozilla/browserid-bigtent</a>.</dd>
-   <dt>
-     Vinz Clortho</dt>
-   <dd>
-     Een Identity Provider voor <code>@mozilla.com</code>- en <code>@mozilla.org</code>-e-mailadressen. Werkt door LDAP te raadplegen. De bron is beschikbaar op <a href="https://github.com/mozilla/vinz-clortho" title="https://github.com/mozilla/browserid-bigtent">https://github.com/mozilla/vinz-clortho</a>. De naam is een verwijzing naar de film Ghostbusters uit 1984.</dd>
-</dl>
-<h2 id="Ongebruikelijke_Persona-terminologie">Ongebruikelijke Persona-terminologie</h2>
-<dl>
-  <dt>
-    Primary Authority (‘Primary’)</dt>
-  <dd>
-    Verouderde term voor e-mailproviders die zich ook als Identity Providers kunnen gedragen.</dd>
-  <dt>
-    Secondary Authority (‘Secondary’)</dt>
-  <dd>
-    Verouderde term voor een terugval-Identity Provider die kan instaan voor gebruikers wiens e-mailproviders geen Identity Providers zijn. Mozilla werkt als een terugval-Identity Provider op <a class="link-https" href="https://login.persona.org" title="https://login.persona.org">login.persona.org</a>.</dd>
-  <dt>
-    Verified Email Protocol</dt>
-  <dd>
-    Een oude, niet meer gebruikte naam voor het BrowserID-protocol.</dd>
-</dl>