3 ms·
I haven't look at the specs deeply, but it would be nice to have a system that did not need any kind of server at all, but the browser itself could be the Perso
by cromwellian 14y ago
I haven't look at the specs deeply, but it would be nice to have a system that did not need any kind of server at all, but the browser itself could be the Persona identity provider. The actual local data needed to pull it off could be replicated (encrypted) to cloud storage so it would work across all your devices and browsers, but the actual profile data itself would never be readable by the servers.
I started looking at the feasibility of building something like Persona into a 'serverless' social network a while ago using Broadcast Encryption techniques to define social sharing groups with revocation (de-friending) and Identity Based Encryption, but it seems like the state of the art IBE always requires a trusted server somewhere. But someone with more expertise in cryptography than me can maybe make it work. My original essay that prompted it (http://timepedia.blogspot.com/2008/05/decentralizing-web.html http://timepedia.blogspot.com/2008/05/decentralizing-web.htm...) based on the sad state of affairs these days where everything is non-federated.
- deleted 14y ago[deleted]
- jackbravo 14y agothere is webid: http://webid.info/ http://webid.info/ which is like ssh keys for the web.
- graue 14y agoIsn't this the ultimate goal of Persona - native browser support?
- mook 14y agoThat would end up requiring your identity to be a key of some sort, though, since ultimately the thing you're logging into needs to check _something_. Email-like things are useful because somebody has to control the domain; if you don't have that, it's harder to establish something. Of course, you can say things like "Hi, I'm random prime number 534473", but that's much less memorable...
- drdaeman 14y agoThe displayed name is a bit different concept from identity. It's like a server and it's DNS name. The point is, nothing prevents the site from knowing me as 70BD6432E50DFB65FF679B32364C3C7840DE4453, but displaying me everywhere as "Aleksey".