Reference client for Bitmessage: a P2P encrypted decentralised communication protocol:
Go to file
Gatien Bovyn 242981755f fixed "libpng warning: iCCP: known incorrect sRGB profile" error
=== before ===
(find . -iname '*.png' -type f -exec identify -verbose '{}' +) |& grep 'known incorrect sRGB profile'
identify: iCCP: known incorrect sRGB profile `./can-icon-24px-green.png' @ warning/png.c/MagickPNGWarningHandler/1830.
identify: iCCP: known incorrect sRGB profile `./greenicon.png' @ warning/png.c/MagickPNGWarningHandler/1830.
identify: iCCP: known incorrect sRGB profile `./can-icon-24px-yellow.png' @ warning/png.c/MagickPNGWarningHandler/1830.
identify: iCCP: known incorrect sRGB profile `./redicon.png' @ warning/png.c/MagickPNGWarningHandler/1830.
identify: iCCP: known incorrect sRGB profile `./can-icon-24px.png' @ warning/png.c/MagickPNGWarningHandler/1830.
identify: iCCP: known incorrect sRGB profile `./can-icon-24px-red.png' @ warning/png.c/MagickPNGWarningHandler/1830.
identify: iCCP: known incorrect sRGB profile `./can-icon-16px.png' @ warning/png.c/MagickPNGWarningHandler/1830.
identify: iCCP: known incorrect sRGB profile `./yellowicon.png' @ warning/png.c/MagickPNGWarningHandler/1830.
2013-06-13 10:30:30 +02:00
debian Remove invalid characters from debian/changelog 2013-06-03 20:22:02 +01:00
desktop Add missing trailing semicolons to pybitmessage.desktop 2013-06-04 15:32:14 -05:00
src fixed "libpng warning: iCCP: known incorrect sRGB profile" error 2013-06-13 10:30:30 +02:00
.gitignore add .dat files to .gitignore 2013-04-23 15:59:10 -04:00
COPYING Debian packaging 2013-04-01 20:23:32 +01:00
LICENSE Debian packaging 2013-04-01 20:23:32 +01:00
Makefile Merge pull request #197 from Atheros1/master 2013-06-07 15:59:28 -07:00
README.md Debian packaging 2013-04-01 20:23:32 +01:00
debian.sh Correct ECDSA verify 2013-06-07 18:58:28 -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