home.social

#youid — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #youid, aggregated by home.social.

  1. @openlink,

    Yep!

    Creating user-controlled profile documents that streamline the decoupling of #identity, #identification, #authentication, #authorization, and #dataspaces (databases, knowledge graphs, and other document collections).

    Crucial in the age of #AI!

    #Privacy #GenAI #YouID #NetID #RWW

  2. Creating user-controlled profile documents that streamline the decoupling of #identity, #identification, #authentication, #authorization, and #dataspaces (databases, knowledge graphs, and other document collections).

    Crucial in the age of #AI!

    #Privacy #GenAI #YouID #NetID #RWW

  3. This is what user-controlled identity, preferences, and profile information look like—entirely built on existing open standards to address the longstanding challenge of online identity authenticity.

    #YouID #NetID #WebID #LinkInBio #PDS #DataSpaces

  4. New edition of my weekly #newsletter is out! This week’s focus is Verifiable #Identity & Personal Profile Pages using:

    1. #Hyperlink-based Entity Naming
    2. Profile-oriented Knowledge Graphs
    3. Loose coupling with #AI Agents

    linkedin.com/pulse/ai-agents-p

    #UseCase #GenAI #YouID

  5. @chrismessina @dontpanic @Mastodon,

    Finally cracked it. Here's how.

    Over here I was pointing to threads.net/@kidehen (which does resolve) rather than threads.net/@kidehen.

    That was it, bar confusion introduced by caching in my particular #Chrome instance.

    This is a big move by #Threads re #identity authenticity, especially in regards to the burgeoning #CreatorEconomy (where the next major battle for curators is about to break out).

    #RelMeAuth #OpenWeb #SSI #YouID

  6. @chrismessina @dontpanic @Mastodon,

    Finally cracked it. Here's how.

    Over here I was pointing to threads.net/@kidehen (which does resolve) rather than threads.net/@kidehen.

    That was it, bar confusion introduced by caching in my particular #Chrome instance.

    This is a big move by #Threads re #identity authenticity, especially in regards to the burgeoning #CreatorEconomy (where the next major battle for curators is about to break out).

    #RelMeAuth #OpenWeb #SSI #YouID

  7. @chrismessina @dontpanic @Mastodon,

    Finally cracked it. Here's how.

    Over here I was pointing to threads.net/@kidehen (which does resolve) rather than threads.net/@kidehen.

    That was it, bar confusion introduced by caching in my particular #Chrome instance.

    This is a big move by #Threads re #identity authenticity, especially in regards to the burgeoning #CreatorEconomy (where the next major battle for curators is about to break out).

    #RelMeAuth #OpenWeb #SSI #YouID

  8. #Screencast demonstrating the power of hyperlinks as tools for self-sovereign identity, featuring usage of the RelAuthMe authentication protocol in our #VirtuosoRDBMS atop #OAuth Identity Provider (IdP) services provided by #Mastodon and #GitHub.

    youtu.be/9nHoRLVIGQg

    #RelAuthMe #OAuth #Identity #Authenticity #SSI #Privacy #NetID #YouID #WebID #ABAC

  9. #Screencast demonstrating the power of hyperlinks as tools for self-sovereign identity, featuring usage of the RelAuthMe authentication protocol in our #VirtuosoRDBMS atop #OAuth Identity Provider (IdP) services provided by #Mastodon and #GitHub.

    youtu.be/9nHoRLVIGQg

    #RelAuthMe #OAuth #Identity #Authenticity #SSI #Privacy #NetID #YouID #WebID #ABAC

  10. #Screencast demonstrating the power of hyperlinks as tools for self-sovereign identity, featuring usage of the RelAuthMe authentication protocol in our #VirtuosoRDBMS atop #OAuth Identity Provider (IdP) services provided by #Mastodon and #GitHub.

    youtu.be/9nHoRLVIGQg

    #RelAuthMe #OAuth #Identity #Authenticity #SSI #Privacy #NetID #YouID #WebID #ABAC

  11. #Screencast demonstrating the power of hyperlinks as tools for self-sovereign identity, featuring usage of the RelAuthMe authentication protocol in our #VirtuosoRDBMS atop #OAuth Identity Provider (IdP) services provided by #Mastodon and #GitHub.

    youtu.be/9nHoRLVIGQg

    #RelAuthMe #OAuth #Identity #Authenticity #SSI #Privacy #NetID #YouID #WebID #ABAC

  12. #Screencast demonstrating the power of hyperlinks as tools for self-sovereign identity, featuring usage of the RelAuthMe authentication protocol in our #VirtuosoRDBMS atop #OAuth Identity Provider (IdP) services provided by #Mastodon and #GitHub.

    youtu.be/9nHoRLVIGQg

    #RelAuthMe #OAuth #Identity #Authenticity #SSI #Privacy #NetID #YouID #WebID #ABAC

  13. Here's the @oplyouid generated Link In Bio profile document used in my #RelAuthMe demonstration.

    kingsley.idehen.net/DAV/home/k

    That's a single profile doc, and associated #Identity, that's under my control and usable for authentication using #OAuth.

    #SSI #YouID #NetID #WebID

  14. Here's the @oplyouid generated Link In Bio profile document used in my #RelAuthMe demonstration.

    kingsley.idehen.net/DAV/home/k

    That's a single profile doc, and associated #Identity, that's under my control and usable for authentication using #OAuth.

    #SSI #YouID #NetID #WebID

  15. Here's the @oplyouid generated Link In Bio profile document used in my #RelAuthMe demonstration.

    kingsley.idehen.net/DAV/home/k

    That's a single profile doc, and associated #Identity, that's under my control and usable for authentication using #OAuth.

    #SSI #YouID #NetID #WebID

  16. Here's the @oplyouid generated Link In Bio profile document used in my #RelAuthMe demonstration.

    kingsley.idehen.net/DAV/home/k

    That's a single profile doc, and associated #Identity, that's under my control and usable for authentication using #OAuth.

    #SSI #YouID #NetID #WebID

  17. Here's the @oplyouid generated Link In Bio profile document used in my #RelAuthMe demonstration.

    kingsley.idehen.net/DAV/home/k

    That's a single profile doc, and associated #Identity, that's under my control and usable for authentication using #OAuth.

    #SSI #YouID #NetID #WebID

  18. There are approx. 5.25 billion+ people on the internet (and growing). These numbers also highlight importance of the ubiquitous Transport Layer Security (#TLS) protocol as critical infrastructure for solving #identity authenticity challenges afflicting Internet & Web users.

    I shed some simplified light on the workings of this protocol in a new blog post that also doubles as a #ChatGPT, #Mermaid, and #KnowledgeGraph utility showcase.

    community.openlinksw.com/t/how

    #DPKI #PKI #NetIDTLS #YouID

  19. @BillKimler,

    Yes, but you can still be in control via a simple trick:

    Own your #identity thereby demoting all the #SurveillanceCapitalism captures to mere guesstimates.

    Don't let any technology vendor hoodwink you out of this fundamental power that's totally yours to control.

    #Identity #Authenticity #YouID #NetID

  20. @openlink @youid Wonderful!

    What is this about?

    User-controlled self-sovereign #identity (#SSI) that scales to both the #Internet & #Web.

    @youid generates:

    [1] Public & Private Credentials that can be reconciled as part of an extended #TLS handshake

    [2] An #HTML-based profile doc comprising verifiable credentials -- what's also referred to as a Link In Bio doc

    More to come..

    /cc @atomicpoet @judell

    #YouID #NetID #NetIDTLS #Privacy #RWW #X509 #WebID #PKI #DPKI

  21. @meneer,

    An individual doesn't need a CA in the mix to attain trust, that's required on the backend if you are providing e-commerce (e.g., Amazon.com etc).

    An individual can use a #ZeroTrust algorithm as the basis for establishing trust with family, groups etc..

    That's what #DPKI solves for, via #X509, #TLS, and machine-computable entity relationship type semantics.

    These issues have been deeply thought through over the years. 😀

    /cc @aniltj @w3c

    #NetID #YouID #NetIDTLS

  22. @aniltj,

    #LinkedData is essential to user-controlled #Identity #Authenticity and #Privacy.

    I can demonstrate that with ease, and debate (with live examples) any #BigTech vendor rep that would like to covertly claim otherwise.

    #DPKI is real, and it works for users seeking full control over their identity and privacy. It doesn't work for vendors seeking to exploit users covertly via the "bit of privacy" approach!

    /cc @atomicpoet @Mastodon @youid

    #NetID #YouID #NetIDTLS #TLS #WebID

  23. @rmrfslashbin,

    Somewhat in that public and private credentials are cross-referenced.

    In the case of #NetIDTLS (what I write about), an #X509 certificate holds private credentials cross-referenced to public equivalents by looking-up a #Hyperlink that serves as a certificate subject identifier.

    Basically, it's all based on existing open standards 😀

    /cc @atomicpoet @youid

    #NetID #HTTPS #TLS #WebID #YouID

  24. @youid @Mastodon Regarding verification of claims in my profile doc, here's how that objective is achieved via #HTTPS using a custom handshake.

    tinyurl.com/2p923xap

    Custom Handshake?
    Credentials in my public profile doc are looked-up and matched to equivalents in my locally held #X509 cert, following completion of the conventional handshake.

    #LinkInBio #Identity #Authenticity #SSI #YouID #NetID #WebID #Privacy #TLS

  25. We are finalizing a new release of our @youid browser extension that includes a major new #LinkInBio feature that helps users acquire more control over their digital profile and associated #Identity #Authenticity.

    Items contained in the ZIP bundle generated by #YouID include: an #HTML based profile doc, #PKCS12 credentials bundle, #vCard, #QRCode, etc.

    Example: id.myopenlink.net/public_home/

    /cc @Mastodon

    #SSI #NetID #Privacy #Web30 #LinkedData #SemanticWeb #HTTPS #TLS #SMIME #KnowledgeGraph

  26. @ben,
    Here’s what a user has to do:

    1. Copy a #SHA hash of #PublicKey from what #YouID outputs (via a #html doc) to their @Mastodon profile page

    2. Download #PKCS12 doc

    3. Double click on downloaded #PKCS12 and leave OS #UI/#UX to handle credentials storage to its native credentials store (e.g., #macos #keychain).

    1-3 works on any modern #OS since they all understand what a #PKCS12 file management.

    Personally, I don’t believe these steps are beyond the capabilities of end-users.

  27. @ben ,
    It isn’t more complicated if there’s a user-friendly solution delivered as an app or browser extension for:

    1. Generating Certificate

    2. Extracting #PublicKey hash in copy & paste friendly form

    3. Packaging credentials in a #PKCS12 file (understood by all modern operating systems)

    That’s exactly what our #YouID browser extension offers 😀

    /cc @Mastodon

    #DPKI #NetID #WebID #X509 #TLS #Identity #Authenticity

  28. @acjay,

    Yes, the #Fediverse and #Web at large.

    #Identity #Authenticity can be handled using existing open standards; it just needs new thinking on the parts of both end-users and solution providers.

    If you lookup any of the following tags you will see related posts on this important self-sovereign (#SSI) matter: #YouID, #NetID, or #WebID, or #DPKI.

    #X509 #TLS #HTTPS

  29. @fshr,

    In my profile page you will notice how I have an #SSI (self-sovereign identity) tag associated with an #SHA hash of a public key. That entry enables my @Mastodon page function as a verifiable credentials source used for #identity #authenticity via a mutual #TLS handshake.

    I can explain further if need be re how this is just a different way ( based on existing open standards) of the #keybase protocol.

    #NetID #YouID #WebID #HTTPS

  30. @bobwyman,

    Yes, users will not be in a position to configure the “.well-known/{whatever}” #metadata document offered by a service provider.

    Requiring that and a custom-resolver have always been hurdles.

    Furthermore, the notion of canonical #identity is rife with issues.

    This is why I’ve always used a collection of hyperlinks for denotation and entity relationship type semantics for reconciliation.

    /cc @blaine @ben

    #SSI #Identity #NetID #WebID #YouID

  31. @bobwyman @Mastodon @blaine @brewsterkahle @christina @sheldrake @dsearls @jpanzer ,

    Currently, #Identity #Authenticity on this platform is handled via a single option that depends on an ability to place #HTML in a page you control.

    The #HTTPS based system I demonstrate simply requires possession of credentials (#X509 cert and #PrivateKey) stored in your local keystore (e.g., Keychain on #macOS) or a #PKCS12 file.

    #NetID #YouID #TLS #DPKI