@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
#https #x509 #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
#html #qrcode #linkinbio #identity #authenticity #ssi #youid #netid #webid
Checking out #SolidProject a bit.
I like how, for logging in and keeping track of ownership/rights, they separate identity (with #webid) and authentication (with #openidconnect ): this means in principle, you could trivially self-host your identity under your own domain (it is just a file), and use some external service for actually logging into stuff with that identity. Would that service go away or stop being trustworthy, you can switch to a different one without losing your identity.
#openidconnect #webid #SolidProject