Reference client for Bitmessage: a P2P encrypted decentralised communication protocol
07b67051c9
[Broadcast Subscribers] gets the Bitmessage Icon for identification. This is hard-coded now, I would favour to put [Broadcast Subscribers] as a fixed item into the Address Book, so you can set an avatar as soon as i implement avatars. Still no options yet: There will be an option to disable Identicons and Avatars separately. Another option will be for the suffix (to mimic adresses like "BM-...@bitmessage.ch" or to add a personal "salt" to prevent identicon attacks where someone creates an address with an identicon that looks alike the one of a known address). Also, identicon size (coupled with row height) should be available, but is of low priority. Next step (after the settings) is to load specific avatars for each address. |
||
|---|---|---|
| archpackage | ||
| debian | ||
| desktop | ||
| ebuildpackage | ||
| man | ||
| puppypackage | ||
| rpmpackage | ||
| slackpackage | ||
| src | ||
| .gitignore | ||
| arch.sh | ||
| configure | ||
| COPYING | ||
| debian.sh | ||
| ebuild.sh | ||
| generate.sh | ||
| INSTALL.md | ||
| LICENSE | ||
| Makefile | ||
| osx.sh | ||
| puppy.sh | ||
| README.md | ||
| rpm.sh | ||
| slack.sh | ||
PyBitmessage
Bitmessage is a P2P communications protocol used to send encrypted messages to another person or to many subscribers. It is decentralized and trustless, meaning that you need-not inherently trust any entities like root certificate authorities. It uses strong authentication which means that the sender of a message cannot be spoofed, and it aims to hide "non-content" data, like the sender and receiver of messages, from passive eavesdroppers like those running warrantless wiretapping programs.