What are the negatives? I'm currently taking a closer at look at what to essentially use as the parent identity

Reply to this note

Please Login to reply.

Discussion

I don’t know enough about DIDs to diss them. Just don’t see anything built with it yet I guess - unless I’m just not looking in the right places.

The biggest question id have is where does your data live? If it’s at a single place then I don’t see the point of a DID.

The idea with DIDs is that it would live with the user, and you would be able to exchange data across networks. So from a design POV this would mean that the accumulation of online education is stored with the user - doesn't matter if they completed lectures on Linkedin, Udacity, etc.

However if being able to transmit a simple data store across relays is possible then I can see DIDs losing value for that specific use case

thinking ⛈️

nostr:note1gdr4xqeh0tqld0c7xpwapcsjl8j5auyryhf7udw4d2t3thnp4w9qkwftph

I don’t get it, how does data live with user , where? Browser cache? Local cache? Relays send data back and forth to clients - and that’s why we use nostr - neither your ID nor your data is stored in one place

From my understanding it seems like Web5 is using something called a decentralized web node that is either self hosted or hosted by providers. I believe they're using blockchain under the hood for storage.

The commentary by one of the architects is interesting because it seems like nostr affords more privacy, and users have a proclivity to organize around clients/services by way of nature.

Web node sounds exactly like a relay. The screenshot is nonsense. You can absolutely run your own relay and your data will be there. Don’t know what he’s talking about.

Who is running these web nodes? How many? How easy is it to run your own? What if they rug your data?

Isn’t this what nostr:npub1sg6plzptd64u62a878hep2kev88swjh3tw00gjsfl8f237lmu63q0uf63m's TBD setup is all about - https://developer.tbd.website/docs/web5/

NB. I understand very little about this.