brianparks

FYI: No longer using a self-signed cert.

This is no longer the case. I was using a self-signed cert temporarily.

From your page: "I tried jq, which seems very good. However I was not quite able to grasp its syntax, so I gave up searching and I created my own."

I use jq on an almost daily basis, so I can sympathize with your plight. jq's syntax is documented quite well (if rather succinctly), but one non-intuitive thing is that it is possible to end up with non-JSON output if you use jq's array ([]) operator rather than the map() filter. However, I still prefer its syntax as one pipeline similar to UNIX one-liners rather than several command-line args, probably purely out of similarity to how I think about the data. I think about its transformations, rather than as independent selection and projection steps. This may be personal preference, but I'm curious as to your thoughts on syntactical choices.

Thanks for the comments. I don't use crypto-in-browser, nor do I generate keys on the server. I built a (very simple) protocol specifically for this purpose to avoid the issue that current email has of requiring at least 3 different protocols to handle the entire round-trip (add to that if you're doing SPAM filtering, databased user authentication, etc.). XMPP, from my brief experience with it, is well suited to "instant"-type communications, but the vast majority of "legitimate" emails are significantly more substantive than "instant" messages, so I believe the NeoMsg protocol is superior for this particular task.

As of right now, the source is not open, but it is definitely my plan to open source the building blocks (the server, the reference implementation client, the client libraries, and the web client) in an effort to reach everybody I can (some people would rather pay for hosting; some would rather host themselves and I respect that -- I ran my own SMTP/IMAP server for almost a decade)

This is an early-stage project that is an infrastructure play. Can be seen as a replacement for current "secure email" providers that also has a complete infrastructure attached so that as the network grows, the likelihood that you have to "log into someone else's mail infrastructure to access it" decreases. Feel free to sign up, tell friends, send messages to them, etc. (please forgive the self-signed cert)