PGP AFAIK is simply encrypting the content of an email with the public key of the person you're going to send it to. The address is public. PGP is a bit of a hassle in terms of exchanging public keys and integrating with legacy email clients/web clients.
Bitmessage has additional features, such as the ability to broadcast messages from a public address to all subscribers.
Especially with this client, Bitmessage is actually much more user friendly and powerful.
To simplify,
PGP hides: content Bitmessage hides: content, recipient, sender.
Re:Bitpost – Private decentralized messaging
by danesparza on Tuesday July 29, 2014 @03:57PM
(#8104596)
PGP isn't just for email.
"PGP is a bit of a hassle in terms of exchanging public keys" this is true, but it's a bit of a necessary evil. How do you accomplish this in a secure and transparent way?
Re:Bitpost – Private decentralized messaging
by autodidakto on Tuesday July 29, 2014 @01:15PM
(#8103401)
BitMessage uses private/public keys, but it isn't built on top of email like PGP. It's meant to replace email. It is its own network and protocol, intended to be private at every level.
Re:Bitpost – Private decentralized messaging
by danesparza on Tuesday July 29, 2014 @03:54PM
(#8104582)
PGP isn't built on top of email.
Source is available here: https://github.com/stevedekorte/Bitpost
This is a client based on the BitMessage protocol. Here is a whitepaper that describes BitMessage: https://bitmessage.org/bitmessage.pdf
What I would like to know (since it seems that the original developers are reviewing comments made here it seems): How is this different from PGP? (Wikipedia article in case you're reading this and haven't heard of PGP: http://en.wikipedia.org/wiki/Pretty_Good_Privacy)