Peter Surda
ca567acab3
- instead of being processed in the ReceiveQueue thread, uploads are now done in a dedicated thread. Only the parsing is done in ReceiveQueue thread. - the UploadThread is modelled based on the DownloadThred, but simpler. - it checks for intersection attack, eliminates duplicates and restricts the write buffer size to 2MB (may still grow slightly higher if too many big objects are requested, but the absolute limit appears to be about 4.5MB in the worst case scenario). - the restriction of the write buffer may cause some upload throttling (to about 2MB per second per connection), but can be optimised later - fixes #1414 |
||
|---|---|---|
| build | ||
| desktop | ||
| dev | ||
| docs | ||
| examples | ||
| fabfile | ||
| man | ||
| packages | ||
| src | ||
| .gitignore | ||
| .travis.yml | ||
| android_instruction.rst | ||
| bandit.yml | ||
| checkdeps.py | ||
| configure | ||
| COPYING | ||
| INSTALL.md | ||
| LICENSE | ||
| MANIFEST.in | ||
| PULL_REQUEST_TEMPLATE.md | ||
| README.md | ||
| requirements.txt | ||
| setup.cfg | ||
| setup.py | ||
PyBitmessage
Bitmessage is a P2P communication 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. BM aims to hide metadata from passive eavesdroppers like those ongoing warrantless wiretapping programs. Hence the sender and receiver of Bitmessages stay anonymous.
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
Feel welcome to join chan "bitmessage", BM-2cWy7cvHoq3f1rYMerRJp8PT653jjSuEdY which is on preview here: https://beamstat.com/chan/bitmessage