Reference client for Bitmessage: a P2P encrypted decentralised communication protocol:
Go to file
fuzzgun b40f68023b Changes for the OpenSUSE build service 2013-09-28 15:26:10 +01:00
archpackage Changes for the OpenSUSE build service 2013-09-28 15:26:10 +01:00
debian Changes for the OpenSUSE build service 2013-09-28 15:26:10 +01:00
desktop Packaging for multiple distros 2013-07-12 10:36:28 +01:00
ebuildpackage -aChanged version to 0.3.5 2013-07-29 22:19:15 +01:00
man Packaging for multiple distros 2013-07-12 10:36:28 +01:00
puppypackage Packaging updated to be architecture independent 2013-08-11 12:07:54 +01:00
rpmpackage Changelog update for 0.4.0 2013-09-28 13:09:15 +01:00
slackpackage Packaging for multiple distros 2013-07-12 10:36:28 +01:00
src Changelog update for 0.4.0 2013-09-28 13:09:15 +01:00
.gitignore Adding src/.settings/ to .gitignore (for Eclipse developers) 2013-06-23 21:17:34 +01:00
COPYING Debian packaging 2013-04-01 20:23:32 +01:00
INSTALL.md Responded to comment from jvz; fixed brew install instructions. 2013-08-16 19:02:40 -04:00
LICENSE Debian packaging 2013-04-01 20:23:32 +01:00
Makefile Increment version number to v0.4.0 2013-09-22 23:29:30 -04:00
README.md add installation 2013-08-13 22:18:16 -07:00
arch.sh Changelog update for 0.4.0 2013-09-28 13:09:15 +01:00
configure Packaging for multiple distros 2013-07-12 10:36:28 +01:00
debian.sh Increment version number to v0.4.0 2013-09-22 23:29:30 -04:00
ebuild.sh Increment version number to v0.4.0 2013-09-22 23:29:30 -04:00
generate.sh Changes for the OpenSUSE build service 2013-09-28 15:26:10 +01:00
osx.sh Removed sudo when building DMG 2013-08-25 04:43:32 -04:00
puppy.sh Increment version number to v0.4.0 2013-09-22 23:29:30 -04:00
rpm.sh Increment version number to v0.4.0 2013-09-22 23:29:30 -04:00
slack.sh Increment version number to v0.4.0 2013-09-22 23:29:30 -04:00

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.

references