home.social

#webid — Public Fediverse posts

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

fetched live
  1. Ich hab gestern ein neues WG Konto angelegt. Neue Bank, also einmal rüber mit allen Daten inkl. #schufa und einem sehr sehr weirden #WebID Telefonat zur Verifizierung... Zum Dank bekam ich keine Bestätigungs SMS.... Wurde aber nur Minuten später dreifach von privaten Nummern als "PayPal" wegen angeblicher Zahlungs Schwierigkeiten anrufen.... #Bots #datasecurity #databroker #privacymatters

    Ergo: im Prinzip kann ich davon ausgehen, das mein gesamter Datensatz (Mal wieder?) für mehr Geld verkauft wurde als ich auf dem Konto je bewegen werde..... Danke #ING

  2. 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

  3. Habe soeben 7 verschiedene Mitarbeiter*innen von #WebID kennengelernt.

  4. With this protocol, it was easy to change ID provider without changing my ID URL. Now we have other several proposals for IDs. For example, #WebID. I don't manage the technicalities of these different identification systems, but I think that separating people's identities from services would have many benefits.

  5. #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

  6. 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

  7. 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.

    medium.com/openlink-software-b

    Another step towards pseudonymous #Identity #Authenticity that scales to both the #Internet and #Web.

    /cc @atomicpoet @judell @blaine

    #SSI #NetID #WebID #SemanticWeb #LinkedData #WoT #Privacy

  8. @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

  9. @strypey identity in #solid is based on #WebID and the Solid-OIDC protocol, there is no blockchain involved

  10. @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

  11. @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

  12. @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

  13. @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

  14. @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

  15. @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

  16. @bobwyman,

    Yes!

    BTW -- using an #HTTP-based #Hyperlink as an Entity Name addresses the concerns you've raised.

    Thanks to the #Fediverse, the power of hyperlink-base entity names will become increasingly obvious, as hashtags demonstrate right now 😀

    Here's a publicly accessible #GoogleSpreadsheet that demonstrates hyperlink-based unambiguous entity names (a/k/a #WebID).

    docs.google.com/spreadsheets/d

    /cc @ben @MildlyAggrievedScientist

    #DataConnectivity #OpenWeb #Identity

  17. @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

  18. Keeping 2018 SAFE and Solid

    You may have noticed a recurring theme across the SAFE ecosystem this year. The conversation around the ownership of data is picking up pace.

    Perhaps you were at SAFE DevCon 2018. Perhaps you’ve stumbled across a podcast discussing words such as #rdf and Socially Linked Data (or SOLID).

    The word #solid is appearing more frequently in conversations — but why? And what does it mean for the #SAFENetwork?

    medium.com/safenetwork/keeping

    #MaidSafe #tbl #webid

  19. SAFE Crossroads Podcast #49, What's so Special about the SAFE Browser?

    #MaidSafe just released a completely in-house version of the SAFE Browser with some very cutting-edge features. It's still rough-cut but it opens the door to some advanced development options as the #SAFENetwork matures toward readiness for launch.

    Devs Gabriel Viganotti and Josh Wilson explain.

    safenetforum.org/t/safe-crossr

    #decentralized #solid #rdf #webid #web3