#netid — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #netid, aggregated by home.social.
-
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!
-
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!
-
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.
-
#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.
#RelAuthMe #OAuth #Identity #Authenticity #SSI #Privacy #NetID #YouID #WebID #ABAC
-
Here's the @oplyouid generated Link In Bio profile document used in my #RelAuthMe demonstration.
https://kingsley.idehen.net/DAV/home/kidehen/Public/YouID/link-in-bio-credentials-5/index.html
That's a single profile doc, and associated #Identity, that's under my control and usable for authentication using #OAuth.
-
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.
-
@youid Here's an end-to-end #screencast demonstration of pseudonymous #Identity #Authenticity facilitated by the verifiable credentials generated by #YouID.
#NetID #NetIDTLS #WebID #WoT #SemanticWeb #LinkedData #Privacy #SSI
-
New blog post about the newly released @youid 1.6.9 that now includes simplified Link In Bio Profile Doc generation without any cross-reference limits. Naturally, these docs embed a powerful Verifiable Credentials #KnowledgeGraph.
Another step towards pseudonymous #Identity #Authenticity that scales to both the #Internet and #Web.
-
@tilvids @simon.caine_channel,
Great presentation about the fundamental issues afflicting data access and control across the #Web and #Internet.
#NetID #WebID #YouID #RWW #WebWeWant #Identity #Authenticity #Solid
-
How verifiable credentials generated by @youid enable self-sovereign identity (#SSI): a user-controlled approach to #identity, via #HTTPS session initialization using Client Certificate Authentication (CCA).
Watch: https://youtu.be/n6DZeqcqkwM
Adding this as an identity verification option, alongside "rel=me", enhances user #privacy and identity authenticity across the #Fediverse.
-
@openlink @youid @atomicpoet @judell,
By more.. I mean:
The Link In Bio profile document generation is going to get a lot easier i.e., cross-references to other profile pages will be handled via the @youid credentials capturing form; and this is restricted to an arbitrary number i.e., you can provide more than 4 cross-references if so required.
-
@openlink @youid @atomicpoet @judell,
Also note, @youid generated profile documents also include powerful #metadata that manifest a Personal Profile #KnowledgeGraph (expressed in a variety of notations).
For instance, Public Keys belong to you (not YouID an app that simply offers a verifiable credentials generation service); meaning, that Public Key is usable by 3rd parties that what to communicate with you using encrypted content.
-
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
-
#Identity #Authenticity demo using #DPKI:
[1] https://kingsley.idehen.net/public_home/kidehen/Public/YouID/public-credentials-1/index.html -- profile document comprising credentials
[2] https://tinyurl.com/376bncdc -- credentials verification via a #NetIDTLS server equipped with an extended #TLS handshake that de-references #hyperlink used in #X509 cert en route to credentials reconciliation
[3] https://kingsley.idehen.net/public_home/kidehen/Public/YouID/public-credentials-1/ -- artifacts from my #ODSBriefcase folder
-
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. 😀
-
#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!
-
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
-
@youid @Mastodon Regarding verification of claims in my profile doc, here's how that objective is achieved via #HTTPS using a custom handshake.
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
-
@youid @Mastodon Updated my #HTML profile doc's #QRcode, since the version posted yesterday was actually broken 😀
See: https://kingsley.idehen.net/~kidehen/Public/index.html
#LinkInBio #Identity #Authenticity #SSI #YouID #NetID #WebID
-
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: https://id.myopenlink.net/public_home/KingsleyUyiIdehen/Public/index.html
/cc @Mastodon
#SSI #NetID #Privacy #Web30 #LinkedData #SemanticWeb #HTTPS #TLS #SMIME #KnowledgeGraph
-
Woot!
I've used the Plain Old Semantic HTML (POSH) based "rel=me" for #Identity #Authenticity via a #LinkInBio page (generated by @youid) from my personal #DataSpace.
https://id.myopenlink.net/public_home/KingsleyUyiIdehen/Public/index.html
The #Fediverse as a #SemanticWeb enclave continues to give++
-
@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
-
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.
-
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.