Checking out a bit.

I like how, for logging in and keeping track of ownership/rights, they separate identity (with ) and authentication (with ): 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.

Follow

The -based mechanisms ( solid.github.io/authentication ) sure seem complicated/convoluted though!

It *might* all be necessary/essential complexity to be able to meet the design goals, of course - but I'm not quite convinced yet. Getting a strong "If this is the answer, are we *sure* we're asking the right question?" vibe.

Sign in to participate in the conversation
Merveilles

Revel in the marvels of the universe. We are a collective of forward-thinking individuals who strive to better ourselves and our surroundings through constant creation. We express ourselves through music, art, games, and writing. We also put great value in play. A warm welcome to any like-minded people who feel these ideals resonate with them.