Oct 6 08:37
Was wondering if anyone's working on bitmessage implementations in anything else than the current Python reference?
Oct 6 08:47
bmd is a Bitmessage full node written in go https://github.com/DanielKrawisz/bmd
Oct 6 08:48
It seems in open-transactions bitmessage is implemented in C++. At least it mentioned in their doc: https://github.com/Open-Transactions
Oct 6 08:58
Open-Transactions doesn't implement bitmessage - it uses the PyBitmessage API
Oct 6 09:30
The caveat here is that bmd is a just a relay hence the use of "node". I'm not really sure what "full" is supposed to mean but bmd does not do any encryption/decryption.
Oct 6 09:45
I remember reading some months ago that some group was working (or planning?) on a red/black implementation of bitmessage - not sure about the details though?
Oct 6 09:54
Sounds like bmd/bmclient by Justus Ranvier. Is this what you had in mind? bmd bmd is the network daemon (the equivalent of btcd) which connects to the P2P network, relays and stores messages, and contains no private keys or user-specific metadata. bmclient bmclient is the user daemon (the equivalent of btcwallet) which stores a user's private keys, messages, and metadata. bmclient obtains incoming messages from, and routes outgoing messages through, a trusted instance of bmd. Users interact with bmclient via standard mail clients rather than a dedicated GUI.
Oct 6 10:03
Probably, though I think I heard about it via Daniel's fork. Anyway, is anybody here running either of these? Which one is more current / maintained?
Oct 6 10:06
Daniel Krawisz bmd - 152 commits, last Mar 30 2017 Justus Ranvier bmd - 123 commits, last Jun 5 2016
Oct 6 10:13
Daniel is here at HCPP17, I plan on talking about further development with him anyway. I believe OpenTransactions also uses Daniel's bmd fork but I'll ask him about it. I've known Daniel for a couple of years, he was the first person to interview me about my Bitcoin research which I was doing at that time. Peter Surda Bitmessage core developer
Oct 6 11:08
Now I see some Jabit-0.0.1 on "Network Status" tab. It's written in Java: https://github.com/Dissem/Jabit
Oct 7 10:50
Daniel authorised me to say this in his name regarding bmd: The node works, but there is no active development at the moment. He also promised that they'll reach out when there is further development so that we can coordinate. Peter Surda Bitmessage core developer
Oct 7 11:56
Chinese whispers, so trustless, much cypherpunk. /s
Oct 7 13:48
I am working on a messaging protocol that will scale to centrillions of nodes without any single node passing much bandwidth, equalizing packet flow across all nodes. It will probably be a couple more years before I release a whitepaper due to several issues, a few of which I will detail here. 1. All novel crypto. a. done from scratch in a unique programming language. b. uses no public keys. c. uses no mathematical operations. d. is provably secure and provably unbreakable (will be a first). e. uses tricks that apparently have never been tried with crypto. f. will be to messaging what bitcoin is to unit of account or value. 2. Zero dependencies, all libs baked from scratch. 3. Packaged with its own hardened kernel linux distro. 4. A complete replacement for Tor included as part of the protocol. 5. A protocol function that allows nodes to find each other without bootstrap servers. 6. Functions that prevent fake node addresses and other attack mitigation require more work and code than the main messaging protocol, which itself would be only several kilobytes. I decided to share this with you so that you know that someone is working on it.
Oct 7 15:36
Your point being?
Oct 7 18:39
It'll never happen!
Oct 7 20:57
You just rid yourself of any bit of credibility at 1.d
Oct 7 23:59
It would never happen if it were up to you. But it's not up to you.
Oct 8 01:23
Your opinion does not matter to people who actually achieve things in life.
Oct 8 01:27
Pretty ambitous, so far I see 3 major projects that will all be a piece of shit, just due to physics and human nature, not you 1 (yet another) Anonymizing network, 2a hardened kernel distro, a PhD level thesis on having bootstrapless Dht - you'll win awards for that. 3 bitmessage like protocol Just in case you were actually serious I'd try to knock some out and tighten your focus a bit. Do "one thing", and do it well. Shit gets overwhelming fast - I have 1000s of projects that started a bit too ambitious and all encompassing. 1c. uses no mathematical operations. kind of hard to do crypto bruh 4 - just force them to use tor or i2p (pick one). You'll help anonymzie those network more as well as help anonymize your users better - only users of your network, are also users of your network... 5 - use tor or i2p hidden services. they're supposed to be hard for the NSA and popo to find your actual locations. 6 - there's already some and it's *all* they do
Oct 8 02:57
I was not asking for your advice or consent. I have discovered a method of messaging cryptography that requires no mathematical crypto. Rather than mathematical operations it is a very clever scheme of swapping bits in a new way that is provably secure, requiring no key exchange between parties, with zero possibility of successful cryptanalysis. It is like OTP, but it is not OTP, because it does not require prior exchange of keys. As for the bootstrapless DHT (you guessed nearly correctly) I discovered a method of finding peers that is not new, but has not been used in that way. Instead of hashing individual peer addresses, it hashes ring signatures of groups of peers, and sends the IP addresses through other channels. It would hardly be worth a PhD thesis, rather it would just make the PhD's scratch their heads and wonder how such a tiny technique evaded them, since hackers already know how to do it, but simply just haven't felt the need of it. The anonymizing network is already done by another group of programmers, and requires only a few tweaks to work with my system, about a month of sundays all told.
Oct 8 10:35
Ah, one of THOSE people, are we? You can now either go on and elaborate on said crypto, which will indeed prove your intentions AND that you're not full of shit. Oooooor, you can, which so far has been the far more likely to happen variant, go around, tell people to fuck off, give out more vague but completely meaningless bits of information and dodge any serious question, which has been time and time again the default reaction of someone who has absolutely nothing to show for and was just trying to troll the more-intelligent people here into wasting brainpower on deciphering your mess.
Oct 8 10:36
So trolls achieve things in life nowadays?
Oct 9 03:50
No, you have never amounted to anything.
Oct 9 04:00
I don't have to prove anything to you, supercillious twit. Shit in a jar and sniff it, then stick your superior rationale in there with it.
Oct 9 10:34
I've achieved a massive boner. Does that count?
Oct 9 11:16
Aaaand further messages ignored and previous messages deleted.
Oct 9 12:21
Yes, you are a big wanker.
Oct 10 03:45
|Bitmessage security suggestion||Feb 21 04:26||3|
|Bitmessage feature request for API commands||Feb 20 23:00||1|
|bitmessage launches cmd and then powershell||Feb 20 19:23||43|
|I want the FEDS on this chan to know I identified one of their new tactics.||Feb 20 12:03||2|
|Mitigating exploited software with firejail||Feb 19 22:42||8|
|Critical vulnerability in v0.6.2||Feb 19 16:51||50|
|message database seems to be corrupted after all that upgraes and attacks||Feb 19 14:55||7|
|Since upgrading yesterday to 6.3.2, Bitmessage is not connecting||Feb 19 11:12||7|
|Inflood of old messages||Feb 18 19:16||23|
|It is slow making connection.||Feb 18 18:04||1|
|Globewashing||Feb 18 17:44||1|
|how to make bitmessage secure||Feb 18 05:02||1|
|Are you blacklisted/whitelisted?||Feb 18 04:19||2|
|Are Linux systems vulnerable to recent attack?||Feb 18 02:19||12|
|Are you blacklisted?||Feb 18 02:09||1|
|address on Peter's reddit account||Feb 17 23:51||3|
|Can't add entries to black list using Add Entry button||Feb 17 15:20||4|
|Errors while trying to run 0.6.2 or 0.6.1||Feb 17 15:20||4|
|Bitmessage project looking for auditors and/or security specialists (reddit crosspost)||Feb 17 13:21||6|
|HIRE A HACKER/CHANGE GRADES||Feb 17 08:59||2|
|Download it.||Feb 17 07:59||2|
|passphrase strength ?||Feb 16 20:34||8|
|$ cd PyBitmessage ; git log | grep Author | sort -u | blacklist||Feb 16 15:54||18|
|diagram||Feb 16 01:46||1|
|Bitmessage components security seclusion example||Feb 16 01:24||1|
|⩩ 𐄉 ㎮ ䷦ 🞳 🆁 ㍝ f 𝙲 🄦 ➇ ⨘ ㊳ 𝐗 ⦱ 🄹 𝟒 ䷄ Ｋ 🆙 ䷤ 𝐙 ⒄ ₹ ꠲ ||Feb 16 00:04||1|
|NOTICE: Address Revocation||Feb 15 18:28||12|
|Cannot connect since yesterday||Feb 15 17:59||2|
|Questions regarding recent bitmessage data exploit||Feb 15 03:46||2|
|Latest commit borked||Feb 14 05:26||5|
|BM-onion||Feb 14 05:22||5|
|That's my new address||Feb 14 03:40||1|
|BM massacre!||Feb 13 21:23||2|
|Namecoin integration||Feb 13 20:18||11|
|Hashwalling Functions for Security||Feb 13 17:58||2|
|Same old problem connecting to network||Feb 13 17:12||4|
|Injection attack mitigation||Feb 13 16:52||7|
|This denial of service shit needs to be patched||Feb 13 12:00||7|
|Test||Feb 13 11:37||1|
|Proving that BM was sent?||Feb 13 11:07||10|
|bitmessage ...||Feb 13 08:13||1|
|Improve icon for chan + messages: important or not||Feb 13 05:25||2|
|pickle puzzle||Feb 13 01:03||20|
|so happy||Feb 12 16:32||2|
|Fwd: Re: Did everyone else's BM starting freezing up||Feb 11 03:54||10|
|hacker service||Feb 10 03:48||2|
|another feature request||Feb 10 01:12||1|
|bitmessage feature request||Feb 10 01:10||1|
|feature request||Feb 10 01:04||1|
|Questions for the Bitmessage Community||Feb 9 21:30||7|
|Did everyone else's BM starting freezing up||Feb 9 03:21||4|
|A light weight version of the denial of service message||Feb 8 13:22||3|
|RE: Hello.||Feb 8 11:48||1|
|WWtest||Feb 8 10:44||1|
|test1||Feb 8 10:37||1|
|WARNING! denial of service message||Feb 8 10:19||3|
|extended encoding||Feb 8 01:24||7|
|bountyfy -- 7 € payout||Feb 5 20:59||2|
|clean up pyBM github landing page, please||Feb 4 23:00||2|
|Running BM daemon as a service||Feb 4 13:47||6|
|hidden service - long names||Feb 4 12:37||7|
|RAM consumption - RAM not released||Feb 3 21:05||4|
|Bug? First connection quickly breaks||Feb 3 11:41||6|
|Request: debug.log initialization / termination||Feb 2 18:30||2|
|kqueue poller in asyncore bounty -- no payout||Feb 2 14:23||5|
|Bitmessage bug in Help > About||Feb 2 13:59||7|
|Message size is metadata||Feb 2 13:25||6|
|New warning "sni-qt/5864" WARN||Feb 2 12:12||2|
|ordering||Feb 1 10:38||12|
|RAM consumption||Feb 1 10:14||5|
|discrepancy in transmit/receive byte counts||Feb 1 07:53||6|
|BM CPU time||Feb 1 02:39||5|
|kqueue poller in asyncore bounty||Feb 1 00:13||15|
|new theme for beamstat||Jan 31 11:35||2|
|Support request -- dontconnect in pyBM 062 not being honoured||Jan 31 10:16||1|
|python IDE||Jan 31 10:15||2|
|My BM is connected to one peer twice||Jan 30 06:36||7|
|Support request/Bug report: keys.dat gets corrupted when running out of disk space||Jan 29 15:44||2|
|Feature request/idea/suggestion: user-defined data directory (command-line argument)||Jan 29 15:16||2|
|GUI dontsendack||Jan 29 05:15||1|
|Another message problem||Jan 29 03:49||3|
|Message deletion broken||Jan 29 00:28||3|
|bitmessage on android device||Jan 29 00:03||1|
|#1||Jan 27 10:12||1|
|/src/helper_* python files ?||Jan 27 04:53||3|
|Dandelion + supervising BM ?||Jan 26 18:41||2|
|CPU time : connection frequency - patch||Jan 24 22:40||4|
|huge spike||Jan 24 12:31||1|