Peter Šurda
a0bbd21efc
- outbound peers now have a rating - it's also shown in the network status tab - currently it's between -1 to +1, changes by 0.1 steps and uses a hyperbolic function 0.05/(1.0 - rating) to convert rating to probability with which we should connect to that node when randomly chosen - it increases when we successfully establish a full outbound connection to a node, and decreases when we fail to do that - onion nodes have priority when using SOCKS |
7 years ago | |
|---|---|---|
| build | 7 years ago | |
| desktop | 7 years ago | |
| dev | 7 years ago | |
| man | 11 years ago | |
| packages | 7 years ago | |
| src | 7 years ago | |
| .gitignore | 7 years ago | |
| COPYING | 8 years ago | |
| INSTALL.md | 7 years ago | |
| LICENSE | 8 years ago | |
| MANIFEST.in | 7 years ago | |
| README.md | 9 years ago | |
| configure | 11 years ago | |
| setup.py | 7 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