citizenaspirant/PyBitmessage
1
0
Fork 0
Code Issues 1 Pull Requests Releases Wiki Activity
Reference client for Bitmessage: a P2P encrypted decentralised communication protocol:
2,144 Commits 3 Branches 24 Tags 13 MiB
Python 96.6%
Shell 1.1%
RPM Spec 0.9%
C 0.6%
C++ 0.2%
Other 0.5%
cff1af1b4f
Go to file
Peter Surda cff1af1b4f
Subscription wrong tab 
- when subscribing from addressbook, it switched to blacklist tab
  instead of subscriptions
2017-02-26 20:03:47 +01:00
build Compiletest for non-Windows systems 2017-01-11 14:21:53 +01:00
desktop Update pybitmessage.desktop with more search friendly GenericName 2016-11-14 18:33:46 -05:00
dev Missing import 2017-01-15 11:42:20 +01:00
man Packaging for multiple distros 2013-07-12 10:36:28 +01:00
packages Pyinstaller warning 2017-02-19 21:53:32 +01:00
src Subscription wrong tab 2017-02-26 20:03:47 +01:00
.gitignore changes needed to get current code to run 2017-02-25 00:06:04 -06:00
configure Packaging for multiple distros 2013-07-12 10:36:28 +01:00
COPYING Copyright year updates 2016-05-02 15:00:26 +02:00
INSTALL.md Fix typos & update link in INSTALL.md 2015-01-14 22:19:06 +08:00
LICENSE Copyright year updates 2016-05-02 15:00:26 +02:00
README.md Made references capitalised 2014-08-06 20:08:37 +01:00
setup.py changes needed to get current code to run 2017-02-25 00:06:04 -06: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.

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

References