Peter Surda
4865659d72
- handles old dialog versions better if using curses - can spawn SMTP delivery thread if configured (only when in daemon mode) - daemonized mode now works more like it's properly supposed to on unix (double fork etc). You may have to adjust your init scripts, when when using upstart for example you should now use "expect daemon" - daemon mode now cleanly shuts down when TERM/INT signal is received |
||
---|---|---|
archpackage | ||
debian | ||
desktop | ||
man | ||
puppypackage | ||
pyinstaller | ||
rpmpackage | ||
slackpackage | ||
src | ||
.gitignore | ||
arch.sh | ||
compiletest.py | ||
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