3dbb4d5ce9
- it shows that it needs to wait for PoW to finish - it waits a bit for new objects to be distributed - it displays a better progress indicator in the status bar Previously, people who don't understand how PyBitmessage works sometimes shut it down immediately after they wrote a message. This would have caused the message to be stuck in the queue locally and not sent. Now, it will indicate that the PoW still needs to work, and it will wait a bit longer so that the message can spread. It's not a completely correct approach, because it does not know whether the message was really retrieved after the "inv" notification was sent. |
||
|---|---|---|
| archpackage | ||
| debian | ||
| desktop | ||
| man | ||
| puppypackage | ||
| pyinstaller | ||
| 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.
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