Apr 26 04:12
I want to tell you that your BM now it is dangerous look ------------- SHA224 (-) = bd408fd84cd2c79e12d6e8e79d82ec6b22f4e9bab7fa3c5e4615d281 ===================== group fold 44 hash unfolded ===================== ZZZZZ YHEEI DHFBD DEDHB GGECE IFCFI GIEDG CFBGF GFHJG HELFJ GCELG NEOEM FBHBH BHFGP YHBDF ENGKE HHAFE DEFAE FEBHG HGFFH EHFFG EIHFG OHGHD GPDGD DGGGJ DGDEH HDCEC YDHDH EHDHG PDGDC FFEND EEHGG EFGCH JEBFA DAEKE FFJHF FDEFE CDGDH EBDHG EEGEO YEFEJ FFEDG KGGEL FJGEH BHKDA EHGKE LHFGH DFENE CGNGO HKEKH KHKGH DJGFH CECGJ YFEGC EFGHD GHGGJ FDHGE CGJFA DFECG FEIFH DDGPD FDIFH HIFFF BEDGK FBGEG DHDDJ YEHGE HFGPF IDIHA HJGGE EFHHC GKDBG HHDHH HBFHD CGFDD ENEFG JEFFA EEHBF HEOGI YFGED FDGOE NFIFD DCDJG OGNHA GFDDD ADJGF GBELF CGPFE EGDHE FDGFG HGFAG OGBEE YEBDE EFGGF BEDGP HIGHH EENDG EIECG KGKED GNHAF JEBGE EDHHD AHHFE HBDDE JGIDC VACHC AKEFG GFBED GPHIG HHEEN DGEIE CGKGK EDGNH AFJEB GEEDH HDAHH FEHBD DEJGI UHGAA AAAAD PAAKC AALGE BKGAF EGIEC ACIII LGCAG MGPBE KBCAO MJFLN GBEHI IGGCA WWWWW
Apr 26 08:45
What do you mean, collided? The address you're posting from I've never seen used before. And the post you seem to reply to has been posted by the bitmessage channel address, which everyone has.
Apr 26 09:11
Why is this dangerous?
Apr 26 12:26
fuck ure talking bout ?
Apr 26 18:42
I think he means Bowel Movement
Apr 27 06:49
Yes indeed! You should never try to fart if you have diarrhoea.
Aug 1 01:37
I guess you use a custom password to create a BM address By chance, I used the same password as you would like to create an address, resulting in a set of the same address So I can see you with other people's BM communication content. I do not know how to change this situation at the moment This is the latest message I see
Aug 1 01:43
Can you speak Chinese, my English is very bad, the above is generated by translation software
Aug 1 02:19
Is that doxed content juicy? Mind leaking?
Aug 1 02:21
How does the text below make BM dangerous?
Aug 1 05:39
The following information is what you communicate with other people,And I can see this. Do you think this is a problem?
Aug 1 05:41
You make zero, nada, null, nil, zip, none, no, nyet sense whatsoever. Was your answer supposed to be English? The question was, "How does the text below make BM dangerous." Either answer the question or go away. Thank you so much.
Aug 1 06:11
好吧！我的英语确实太烂了，虽然借助了翻译软件，但是看来依然词不达意。 因为一个巧合，我可以看到你跟其他人的所有交流内容。 我觉得真的不可思议，于是试图告诉你这些而已。 无所谓你是否看得懂英语了，以上。
Aug 2 04:54
protip: don't use passWORDs, but random passPHRASEs If your adversary learns your address passphrase (they can try 1 trillion per second), they can derive your keypair. With that they can decrypt ALL MESSAGES EVER SENT from that address and send fake messages from your address. You won't see the latter yourself. So either use a random address (without passphrase) or a passphrase long enough you need 2 months to memorize.
Aug 2 05:21
The deterministic address algorithm is exactly the same as the chan address algorithm except the chan address algorithm stops at the first valid address found while the deterministic algorithm keeps going until the desired number of valid addresses are generated. This means that the first address generated by the deterministic algorithm is the chan address for whatever passphrase you used. Hopefully at some point an improved deterministic algorithm distinct from the chan algorithm is implemented for the poor sods who prefer to remember a passphrase to regenerate their addresses rather than backup their addresses.
Aug 2 10:21
passphrase should be at least 40 alphanumeric characters with some punctuation. It should be complex enough that you should have to write it down and would take quite some time to memorize it.
Aug 2 13:20
You don't have to limit yourself to ascii - unicode is supported as well. Whatever can be typed or pasted into the passphrase textbox will work. Newer characters like emojis probably won't work but most older characters from unicode 4.0 should work.
Aug 2 13:51
They are pushing emojis into the unicode standard.
|how to export keys from Bitmessage||Aug 20 19:55||5|
|Bitmessage Rocks||Aug 20 17:37||1|
|block a BM address from a chan||Aug 20 11:03||3|
|Is anyone even online at this moment?||Aug 20 08:43||4|
|All green peers 127.0.0.1?||Aug 19 09:07||5|
|Chips without backdoors||Aug 18 19:10||4|
|New warnings in log||Aug 17 21:00||20|
|Yellow peers and green peers||Aug 16 20:59||4|
|cannot import name bmpow||Aug 15 12:36||2|
|Brute forcing BM addr's||Aug 15 07:58||2|
|Bitmessage crashes when posting||Aug 14 05:51||10|
|plz assist. are you a netcat or SSH tunnel guru?||Aug 14 05:01||4|
|shorter bitmessage addresses||Aug 14 04:56||14|
|Why Python?||Aug 13 10:45||16|
|Nerd Bully||Aug 13 05:17||1|
|Bitmessage not connecting||Aug 12 04:16||64|
|Feature idea||Aug 10 03:30||10|
|Local nodes won't connect properly||Aug 9 15:51||28|
|I do any thing in iran for BTC||Aug 7 15:36||3|
|Bitmessage feature request||Aug 7 12:50||4|
|query about short addresses||Aug 7 06:54||4|
|Curious||Aug 5 22:39||8|
|Full time nodes||Aug 5 13:50||9|
|changes to the dodobit server||Aug 5 11:05||2|
|Received Date||Aug 5 06:04||13|
|apinotifypath||Aug 4 06:04||9|
|BM <-> TOR||Aug 3 13:19||12|
|BM Bandwidth||Aug 2 14:11||11|
|When I try to register BM, collided with your key||Aug 2 13:51||12|
|Received Date||Aug 1 21:34||4|
|Bitmessage reminds me of ...||Aug 1 14:36||3|
|I need help||Aug 1 13:08||3|
|Response from Bitmessage Dodo Server||Aug 1 02:25||1|
|Streams and bloom filter||Jul 31 21:25||3|
|Questions about bitmessage streams||Jul 31 21:25||1|
|TTL question||Jul 31 08:03||3|
|API JSON index error||Jul 31 07:22||3|
|API question||Jul 30 11:22||7|
|MiNode||Jul 30 07:19||3|
|Yes it's obvious my BM private keys have been stolen....||Jul 29 19:50||2|
|Keys.dat options||Jul 29 04:56||3|
|Bitmessage and I2P no longer working||Jul 28 22:39||10|
|Connect Bitmessage only to .onion nodes||Jul 27 13:22||3|
|peers||Jul 26 11:36||4|
|© 2013-2016 The Bitmessage Developers||Jul 26 07:12||4|
|0.6.3||Jul 24 20:52||3|
|Bug with chan creation||Jul 24 10:15||2|