Hi Sean, Glad to see you share my frustrations with RetroShare. I can at least tell you how the vaporware system I have been slowly tinkering with the preliminary components to will stack up:
On Mon, Jan 14, 2013 at 10:27 PM, Sean Lynch <[email protected]> wrote: > 1. Use Ed25519 keys, and have them always be URIs. They should not ever > be visible to the user except when it's unavoidable, like sending > contact info via email. > I am shooting for Ed25519 keys which identify nodes, and I certainly want for the Ed25519 public keys to be URIs. A distinction to be made between a node and a person is to me a node represent the analogue of an IP address, whereas people might potentially use many nodes. In a capability-based system, I don't think this distinction really matters provided you have a way to synchronize capabilities between multiple nodes you operate the same way you might synchronize 1Password safes over Dropbox. And fortunately the system itself can be used for this purpose. > 2. Hide any settings or stats related to the network. People should > either be connected or not. > I don't think having this sort of thing is necessarily bad but it would definitely be helpful to de-emphasize this information, perhaps by putting it in the footer. > 3. Use a modern UI paradigm not decended from the old all-in-one > internet browsers like Netcruiser and AOL. I definitely agree having a slick, modern UI that makes the entire system easy-to-use is one of the necessary ingredients for adoption. Here's some of what I've been working on: http://www.youtube.com/watch?v=CvocJh8wMxI -- Tony Arcieri
_______________________________________________ p2p-hackers mailing list [email protected] http://lists.zooko.com/mailman/listinfo/p2p-hackers
