Bitmessage vs lavabit full#

It''s the lack of Sr C/C++ developer talent that's slowing us down. Programmers like myself to work on it.) We have designs, mockups etc. It's the client lib & gui that are lagging from limited resources. We've made good progress on the server, aka this repo. but have lots of work to do before it's production ready. It's an ambitious undertaking, and development has been slow, as I've mostly relied on interns to assist me. The user signet format also supports bootstrapping, whereby it can advertise support for an alternative channel (like bitmessage). I suspect this will be a common marriage, which is why I added hooks in the signet (aka public key) data format so domains can advertise their support for access and/or delivery using TOR.

Bitmessage vs lavabit full#

(DIME is focused on privacy, note anonymity.) For a user to get full anonymity they need to combine DIME with TOR (or I2P). Full anonymity can cause problems with sending bounces, and/or spam complaints. However, it's important to note there is no middle (aka relay, aka mix) node.

The new message format is also designed to obscure meta data, in a manner similar to TOR. The new message format allows a client to validate the signature on a message, without having to download the entire message, so a mobile phone user could, in theory validate a message, and then download the headers, but skip the 100 megabyte cat video. This was done to support efficient access and meta data minimization. Unlike OpenPGP & S/MIME which are general purpose formats, DIME uses a format specific to email messages. The message format is MIME-llike (the closest allegory being an S/MIME message) to facilitate efficient access.

Which is a luxury general purpose formats, with long histories, like OpenPGP don't have. Key data formats, ciphers, are also tightly defined, to facilitate strict validation and interop.

Lookups follow a DNS model, ala chaining, only DIME has mechanisms in place to detect when the domain owner tries to publish a fake user key. Cryptographically you can think of DIME as PGP (w ECC), but with key lookup/management operations in the protocol (to facilitate transparent automation).