pages/assets/garden_decentralized-identity_index.md.BEIMlpi0.js

import{d as i}from"./chunks/git.data.BcrWSzMU.js";import{M as r,q as n,Q as e,K as o,u as t,ag as s,p as d}from"./chunks/framework.Sr2_9k8k.js";const l=e("h1",{class:"p-name"},"Decentralized Identity",-1),h=["innerHTML"],c=s('<hr><details><summary>Referenced by:</summary><a href="/garden/commune/index.md">Commune</a><a href="/garden/decentralized-social-media/index.md">Decentralized Social Media</a><a href="/garden/fedi-v2/index.md">Fedi v2</a><a href="/garden/incremental-social/index.md">Incremental Social</a><a href="/garden/nostr/index.md">Nostr</a><a href="/garden/weird/index.md">Weird</a></details><details><summary>Tags:</summary><a href="/garden/decentralized/index.md">Decentralized</a></details><p>Decentralized identity is when someone&#39;s identity can be authenticated without the reliance of a central authoritative source. Keypairs are the most common form of this, where someone generates a pair of keys - one private and one public, with which they can sign a message in a way that allows others to verify it came from someone with access to the private key and was not tampered with. <a href="https://indieweb.org/IndieAuth" target="_blank" rel="noreferrer">IndieAuth</a> is another version of decentralized identity, used by parts of <a href="/garden/the-small-web/">The IndieWeb</a>.</p><h2 id="user-experience" tabindex="-1">User Experience <a class="header-anchor" href="#user-experience" aria-label="Permalink to &quot;User Experience&quot;">​</a></h2><p>Clients can silently generate key pairs, and allow methods for migration or &quot;linking&quot; identities. The client could also include backup methods like saving the private key to Google drive or similar services. The point here would to have convenient default choices that are reasonably secure, while allowing people to have full agency to choose their own storage and backup solutions.</p><p>Sharing your profile with others may be tricky. If you&#39;re registered on a nameserver then you can just share your handle there, similar to fediverse profile handles. Otherwise, I think QR codes are the most user friendly solution. A client could register a URI handler that takes a public key and optionally a relay server that has the information about that identity. Adding the identity to your friends list could happen fully offline, although pulling the profile information would require a connection. Perhaps that, too, could be encoded in a (likely separate) QR code.</p><h2 id="profile-information" tabindex="-1">Profile Information <a class="header-anchor" href="#profile-information" aria-label="Permalink to &quot;Profile Information&quot;">​</a></h2><p>For casual conversation, a nickname in the profile data should be sufficient. Once a client interacts with someone, they can be added as a contact as a way of verifying the next conversation with someone with that username is actually the same person as before.</p><p>For situations where you want to verify an identity actually has a credentials they claim, you can query a nameserver that vouches for them. For example, whitehouse.gov would have a nameserver that specifies which identity is the actual president of the United States (and other government officials).</p><p>There could be nameservers that allow you to openly &quot;register&quot; your identity with them to get a unique human readable username you can include on billboards or other visual media where you want someone to be able to memorize the identifier, rather than scan a QR code or something.</p><p>For more details on how these decentralized usernames would work, check out <a href="https://spritely.institute/static/papers/petnames.html" target="_blank" rel="noreferrer">Petnames</a>.</p><h2 id="identity-recovery" tabindex="-1">Identity Recovery <a class="header-anchor" href="#identity-recovery" aria-label="Permalink to &quot;Identity Recovery&quot;">​</a></h2><p>If you lose access to your account, it&#39;s gone forever. That is why I think there should be defaults to backup your private key to existing reliable servers, even if they&#39;re owned by large corporations. Otherwise I would see someone have their phone stolen, lost, or upgraded and be surprised when their account is now inaccessible.</p><p>If you do lose your account and create a new identity, you could have others &quot;vouch&quot; for the new identity being an alias for the previous identity. You could verify your new identity with people IRL, and then other clients can see those vouches publicly and, after sufficient quantity, just implicitly assume they&#39;re the same (although with some sort of indicator, so if this gets abused, users are at least aware of the possibility of impersonation.</p>',15),w=JSON.parse('{"title":"Decentralized Identity","description":"","frontmatter":{"alias":"Federated Identity","public":"true","slug":"decentralized-identity","tags":["Decentralized"],"title":"Decentralized Identity","prev":false,"next":false},"headers":[],"relativePath":"garden/decentralized-identity/index.md","filePath":"garden/decentralized-identity/index.md"}'),u={name:"garden/decentralized-identity/index.md"},v=Object.assign(u,{setup(m){const a=r();return(p,y)=>(d(),n("div",null,[l,e("p",null,[o("532 words, ~3 minute read. "),e("span",{innerHTML:t(i)[`site/${t(a).page.value.relativePath}`]},null,8,h)]),c]))}});export{w as __pageData,v as default};