Peter Šurda
2d34e73648
- fixes and feedback from @gfanti and @amiller - addresses #1049 - minor refactoring - two global child stems with fixed mapping between parent and child stem - allow child stems which don't support dandelion - only allow outbound connections to be stems - adjust stems if opening/closing outbound connections (should allow partial dandelion functionality when not enough outbound connections are available instead of breaking) |
6 years ago | |
|---|---|---|
| build | 7 years ago | |
| desktop | 6 years ago | |
| dev | 6 years ago | |
| man | 11 years ago | |
| packages | 7 years ago | |
| src | 6 years ago | |
| .gitignore | 7 years ago | |
| COPYING | 8 years ago | |
| INSTALL.md | 7 years ago | |
| LICENSE | 8 years ago | |
| MANIFEST.in | 7 years ago | |
| PULL_REQUEST_TEMPLATE.md | 6 years ago | |
| README.md | 9 years ago | |
| checkdeps.py | 6 years ago | |
| configure | 11 years ago | |
| setup.py | 6 years ago | |
README.md
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.
Development
Bitmessage is a collaborative project. You are welcome to submit pull requests although if you plan to put a non-trivial amount of work into coding new features, it is recommended that you first solicit feedback on the DevTalk pseudo-mailing list: BM-2D9QKN4teYRvoq2fyzpiftPh9WP9qggtzh