jphastings / credence Goto Github PK

How should a new peer find other broadcasters to listen to?

I'm repeating a lot of HTML between even the three HTML files in the application so far. It'd be nice to be able to use rails-esque layouts or some other templating mechanism.

Credence needs a way of storing external files.

• It needs to be portable (mac os x, linux, windows - though how I'll test the latter I've no idea)
• It needs to be able to store configuration file(s)
• It needs to be able to store (securely!) the private key for signing creds

Build the component which listens to other broadcasters and routes them accordingly.

• Must be able to store creds
• Must be able to pass creds on (only if they haven't been seen before)
• Must be able to pass search requests on (incrementing proximity), if the proximity isn't too distant

Do I need to worry about bandwidth of incoming message here? Or does ZMQ automatically drop things when it gets too busy?

Build an informative UI at the root of the webserver, to help people get acquainted with what's going on.

The info page gives useful information about that Cred, but no information about other Creds on the system that may agree or disagree with that one.

Add a graph for other Creds with the same StatementHash on the creds/info page

If the user doens't have a private key, then only the webserver starts (with limited functionality?) and the UI forces you to generate a private key (and create the 'self' user of id 1) before continuing.