Peter Surda
ca031dc421
- namecoin lookup now also includes name of the record in the recipient field - namecoin lookups now support multiple semicolon-separated recipients like the other recipient-related functions. If there are multiple recipients, namecoin lookup will look up the last entry on the line, for example if you have "a; b; c" in the recipient line, it will lookup "c" |
||
---|---|---|
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