Learning about the nostr killer #web5 
Discussion
π€£ Damus is deadβ¦ again? π€£
only the good things die β¦ again and again π§‘π
That slide is big threatening.
Oh my god just when you think the "credentials on a chain" idea has been absolutely shitcoined to death...It is like the evergreen conference timeslot filler.
Except, there's no credentials on chain.
Whew, luckily I looked into it and that's not how it works at all. Verifiable Credentials are just a signed proof format where you take a statement about something/person and signing it with your ID's key. No blockchain involved. Pretty cool that's been standardized, and I heard even LinkedIn is accepting VCs for proof of employment now.
Quick question: I've seen so many inaccurate takes here that are wildly off when I go check out those materials and code they published, so is it possible that there's a sort of highly tribal bias here that's preventing people from being thoughtful in their assessments? I like learning about all these protocols, and find it a bit odd people aren't willing to do so.
Thanks for looking into it. I have PTSD from drowning in industry bullshit slideshows for years and I knee-jerk reacted to yet another DID thing.
But is there an app for it?
wen ?
Can I download Web5 ?
π
Soon:
They've been trying to canonicalize RDF for 20 years
RDF 1.2 is also about to hit, which is a whole new world of complexity
Props to fiatjaf who did it all in under a week!
wow! thank you .. an all new world for me :)
Nothing about Web5 relies on RDF, from my understanding of their work, so why are you talking about it?
I found the link to their reference implementation, and it looks like soon = now, at least for a fair amount of the features from that areweyet site: https://www.npmjs.com/package/@tbd54566975/web5
Also, looks like nothing relies on RDF, so what was all that about again?
Canonicalization is easy using the existing CBOR and JCS RFCs (as I noted before), and implementation of JCS is something you might use as a test for a junior dev, because it's such a trivial to write: https://github.com/erdtman/canonicalize/blob/master/lib/canonicalize.js
Self sovereign identity?
#Damus need more work
Where can I find the livestream of this??
Why a Nostr killer ?
Yeah, I'm confused too and asked the same from folks here with no real responses. Why would VCs be posed as a "Nostr killer"? I never heard their team claim that. I think the app data, comms, binary streams, etc. part is what they're calling "DWeb Nodes", something that seems entirely separate from VCs.
How is W3C VC a nostr killer?
Yeah, been asking the same question. Seems like folks are confusing an orthogonal signed credential format that's used outside the system with what looks like a completely separate app/data layer they're calling "DWeb Nodes" , which don't appear to have anything to do with VCs π€·ββοΈ
In fact, a verifiable credential issuer could issue a VC with a nostr npub within the subject (now that we have nostr DID schema in draft).
And W3C's Verifiable Presentations JSON can already be signed by a nostr nsec.
Nostr loves JSON after all and VC/VPs are ultimately just signed JSONs encoded in Base64.
Probably all these were lost in translation when presented on stage by non-devs.
Lolz
Given this complexity I very much worry that "Web5" will be able to easily bridge with #nostr
But the team at block are fighting the good fight, if anyone can find a way, its them.
What could such a 'bridge' look like for them, as you understand the two systems?
Are you suggesting a VC is used as a tag system for the data records? Think VCs are rather separate, and nothing about the system/VCs relies on JSON-LD, so perhaps you can clarify?
Does this mean... (looking side to side) ... Nostr is Web 4?
#WhatHappenedToWeb4? #Conspiracy
Why is what appears to be the Verifiable Credentials portion of that work, which is specific to signed proofs and not the app data layer, being labeled as a "Nostr killer"? Wouldn't the DWeb Node part they talked about be the superset thing that's more related to things Nostr does? Did they talk about anything as a "Nostr killer", or is that some narrative created here/by others?
#web5 looks like a big bald spot to me.
What hoppened to web4 π
Cool