/r/bitmessage
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 also aims to hide "non-content" data, like the sender and receiver of messages, from eavesdroppers. If Bitmessage is completely new to you, you may wish to start by reading the whitepaper.
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 also aims to hide "non-content" data, like the sender and receiver of messages, from eavesdroppers.
/r/bitmessage
Very interesting client and relatively up-to-date, being in Java it works on any operating system (it even has a version for Android)
I predict that BM will become more popular as the extent of the spying on everyone's communications becomes obvious to the ordinary citizen.
The official PyBitmessage still runs with outdated Python2 and PyQt4.
Recently, I'm trying to port PyBitmessage to run with Python3 and PyQt5. Although it's unofficial version and still should have some bugs, it seems now running as expected as long as I use it. I use PyBitmessage mostly for communications on chans. One-to-one messaging is not tested well since I have no friends at all.
The source code is published at GutHub: https://github.com/kashikoibumi/PyBitmessage . The default branch 'py3qt' is most matured among other many branches.
If you try to use it, at first backup your PyBitmessage databases and settings which are found $HOME/.config/PyBitmessage/ if you are using Linux.
Any bug reports or comments are welcome.
I'm using it on Devuan GNU+Linux Daedalus which is mostly compatible to Debian GNU/Linux bookworm except systemd utilizations. All dependencies are installed from Devuan (Debian) packages.
Hey,
Just wondering, what changes would need to be made to the code to increase the maximum message size? I understand that any change would make that node incompatible with the rest of the existing bitmessage network.
I'm exploring setting up a private network and increasing the message size. I get that the PoW required would need to be adjusted when increasing message length otherwise the processing time may be insane.
Hello! can anyone help me please?
I need to find my old bitmessage account (i have only part of the mail name)
Could some 1 help me please?
Hello,
Where can I download the latest BitMessage AppImage for a debian version.
Thanks.
I want to share a few issues that I had to deal with when working with PyBitmessage on Windows 10 (x64) 22h2 (build 19045.2965).
If you did not build, but simply took this library when importing the module, I get an error (Win Error 126 "The specified module could not be found"), while the library file exists.
This is due to a missing dependency - the LIBEAY32.dll library is missing. When compiling the library, an outdated version of openssl was used.
Now just copy "C:\Windows\System32\libcrypto.dll" to "C:\Windows\System32\LIBEAY32.dll" to solve this problem.
Perhaps this library should be rebuilt.
I don't know what it's about. It is possible that network participants are using an alternative implementation of the bitmessage protocol that allows message packets to exceed a certain number of elements. I just commented out the output after detecting this behavior:
In the "./class_receiveDataThread.py" file, line 509 is "# return" instead of "return" (version 0.6.3, latest on GitHub).
Yes, it is possible that the calculations being made will indeed be too large - but they must be done in the background for the specific key added. This is not the most expected behavior, you have to delete all messages in order to update the data.
Let's look back at some memorable moments and interesting insights from last year.
Your top 5 posts:
Received a message from a BM user addressed to me tonight as follows:
He writes:
"You have set the Proof of Work for your address rather high. I am having trouble sending messages to you, even using a very short Time to Live."
What specific settings can I change, and where, on my end to facilitate and speed up message delivery?
Thanks!
On my windows 10 laptop, bitmessage will connect, then disconnect after a few seconds and never connect again. Bm connects fine on my pi4 and linux laptop. Does anyone have any idea howto fix this. Running the latest BM.
Hello,
like said above, I wanna install PyBitmessage on Fedora, but the Compiling instructions on the Wiki seem to be really outdated.
I cannot resolve the dependencies, especially the 'bitcoin-release-1-4.noarch.rpm' cannot be retrieved, since the ringingliberty-Website seems to be down, which provided it, and I cannot find any replacement.
I thus also couldnt install python-qt4 and co, and installing 'six' via dnf also still showed that it wasnt found when I executed the bitmessagemain.py .
Anyone got any help on this?
I’m trying to get Pybitmessage running again but my distros are all Debian 11 based. I haven’t been able to figure out how to solve the dependencies that are no longer supported.
Anyone solve this issue?
Linux (GUI):
https://sourceforge.net/projects/pechkin/
https://github.com/Bitmessage/PyBitmessage
Linux (CLI, Command Line)
https://github.com/bpeel/notbit
Nodes ("message router")
https://github.com/TheKysek/MiNode
Android
https://github.com/JonathanCoe/bitseal
https://sourceforge.net/projects/android.pechkin.p/
According to my research I found some "chans" below:
"Chans" in Portuguese Brazil
Site extern
Name: Pechkin in Java, not need installed https://sourceforge.net/projects/pechkin/
Chan: Reddit
please help me! i donwloaded all the stuff for it but when i try to run the .exe nothing happens. and if i open the src folder from github and run it from the python file it still does nothing. error says Faulting application name: Bitmessage-0.6.1_64.exe, version: 0.0.0.0, time stamp: 0x00000000
Faulting module name: nvopencl64.dll, version: 31.0.15.1694, time stamp: 0x62d9e699
Exception code: 0xc0000005
Fault offset: 0x000000000000c715
Faulting process id: 0x2f00
Faulting application start time: 0x01d8bc1f115bd721
Faulting application path: C:\Users\johnl\OneDrive\Desktop\bit\Bitmessage-0.6.1_64.exe
Faulting module path: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_47917a79b8c7fd22\nvopencl64.dll
Report Id: b6c1cecf-47c0-4c1c-8b41-19d5aebc1f8e
Faulting package full name:
I am using what I believe to be the latest available version of pyBitmessage, an appimage file called PyBitmessage-0.6.3.2.glibc2.15-x86_64.AppImage
. I use that appimage to run it without problems on Debian 11.
Question: Did the format of return values for API calls change lately? I use the API call getAllInboxMessages
, and as far as I can see for a long time it used to give back a JSON array as a value of some single <string>...</string>
XML node. Now it looks as if the answer is fully XML.
If this analysis is correct: Is there a way to switch back to the old format? Or is it, from now on, XML "all the way"?
That earlier mix of XML and JSON was certainly special, but it spared me to implement full XML parsing because it was so easy to get at the JSON. Now it looks as if the job just got quite a bit more difficult ...
By the way, that appimage version still identifies as PyBitmessage 0.6.3.2. Maybe a new version would be merited with such a change in bevavior?
EDIT, to add: Nevermind, I think I found the answer in this post from half a year ago. The trick to get the old (and in my case, compatible-with-my-app) bevavior back is to add the following line to the keys.dat
file:
apivariant = legacy
Are the spam wars over? For a week or two, Bitmessage was flooded with hundreds of thousands of double-space spam. Have they stopped generating this junk, or has there been developed a way to filter this stuff out?
It doesn't matter from a message perspective, because if the message isn't meant for you, you won't see it, but it matters from a bandwidth perspective - these messages have to be downloaded in any case, and this can take time and bandwidth.
Hey I basically know nothing about bitmessage and was wondering if anybody had any advice?....how to download..where to find download...I have a android and Alienware laptop...and help would be greatly appreciated!!
This is to follow up from my last post, "C Pow module unavailable" on Windows snapshots > 20211126"
I submitted the problem and solution to the pybitmessage github and in less than two weeks bitmessage's author allowed an approved user to merge the changes I proposed.
If you had problems using bitmessage on windows in the past and saw a "C Pow module unavailable" that should no longer be the case.
If you have some other problem with bitmessage, I recommend mentioning it on the pybitmessage gitbhub, especially if you are also able to implement the solution.
If only the rest of the crypto exchange industry would use this tech! Great work Devs!
I was browsing available chans and subscriptions listed at https://bittext.ch/bmaggradrs. I was wondering, why do every chan is listed with 2 addresses? I tried adding them both of a random chan, but apparently only one of them receives message at any time. Why is that?
As seen here:
https://i.imgur.com/jnJxFoW.png
This solved issue on github suggests a missing dependency, but that is in reference to building bitmessage. I am getting the message while trying to run the Windows binaries from:
https://download.bitmessage.org/snapshots/
For convenience, a link to the current most recent build that does not display the issue:
https://lokilist.com/about.php
AMA.
Rather, "ask me anything that respects anonymity / privacy", although that seems a more loaded initialism.
The documentation @
https://wiki.bitmessage.org/index.php/API_Reference
says:
##> The PyBitmessage API uses XML-RPC.
As if that ended the matter.
The source code @
https://github.com/Bitmessage/PyBitmessage/blob/v0.6/src/api.py
says:
The PyBitmessage API is provided either as
XML-RPC <http://xmlrpc.scripting.com/spec.html>
_ or
JSON-RPC <https://www.jsonrpc.org/specification>
_ like in bitcoin.
It's selected according to 'apivariant' setting in config file.
What a surprise to learn of the API's JSON support contrary to the documentation.
Presumably "config file" means keys.dat, which has no 'apivariant' setting. Let's keep reading that source code and find:
Special value
apivariant=legacy
is to mimic the old pre 0.6.3
behaviour when any results are returned as strings of json.
...
* - apivariant = xml
- current default for backward compatibility, 'json' is recommended
Is there up-to-date information / documentation about the pybitmessage API? Ideally with the JSON-RPC method, which I understand is recommended.
I want to read the messages outside of the pybitmessage client - it's very crashy. Sometimes I restart it 1 to 2 times. I don't want to send, merely to read. Is there a tool that can read messages.dat?
my messages.dat is only 58 MB.
Is there any documentation for messages.dat available? I've looked in a bunch of places, but can't find any. I can easily find the SQL that's used to build the SQLite tables, but no actual documentation on what some of those fields mean.
For example, in the inventory table, there's a field called "objecttype", but I'll be damned if I can find any sort of documentation on what actually goes in this field. In the source, I can see notes that objecttype used to contain a text field that described what objecttype is, but nothing further.
Thanks!