questionable attitude

[chan] bitmessage
Dec 2 13:00

WTF? if numberOfAddresses == 0: raise APIError(4, 'Why would you ask me to generate 0 addresses for you?') if numberOfAddresses > 999: raise APIError(5, 'You have (accidentally?) specified too many addresses to make. Maximum 999. This check only exists to prevent mischief; if you really want to create more addresses than this, contact the Bitmessage developers and we can modify the check or you can do it yourself by searching the source code for this message.') queues.apiAddressGeneratorReturnQueue.queue.clear() if anything, sourcecode like that is utter mischief ! fuck that.

[chan] bitmessage
Dec 2 14:28

the chanerator fixed that problem

[chan] bitmessage
Dec 2 20:32

https://github.com/R0X3/chanerator

[chan] bitmessage
Dec 2 20:32

https://github.com/R0X3/chanerator

[chan] bitmessage
Dec 3 09:29

never again will a bm developer give a fucking err msg due to fucking "MIS CHIEF" what a bunch of sanctimonious bullshitters...

[chan] bitmessage
Dec 3 09:39

how will that be enforced?

[chan] bitmessage
Dec 3 10:24

They create software to circumvent censorship then censor its full power.

[chan] bitmessage
Dec 3 10:27

Sure, because preventing you from creating a million addresses in a single API call is truly restricting it's power.

[chan] bitmessage
Dec 3 10:32

using super mammoth 1.2

[chan] bitmessage
Dec 3 10:32

the same idiots that produce anon software, yet demand to doxx ureself if u wanna register on BM wiki idiocy ^10 !!!

[chan] bitmessage
Dec 3 10:39

that doesn't work

[chan] bitmessage
Dec 3 13:15

I have generated a million addresses and key pairs to analyze them for statistical anomalies. The results are useful.

[chan] bitmessage
Dec 3 13:17

So, what actually keeps you from doing so with this "limitation"? Is "I can't generate a million addresses in a single call" so much of a holdoff to you that you'd just ditch it entirely? Too hard to make a bunch of calls to get the same result?

[chan] bitmessage
Dec 3 13:24

Since I have generated gigabytes of keys it's safe to say the limitatation in canonical PyBitmessage codebase have been neither holdoff nor hindrance. You are confusing me with someone else, perhaps with one of the script kiddies who are larping about the number of useless chans. It seems a couple of these larpies are tweaking out here every time I check in.

[chan] bitmessage
Dec 4 16:23

The wonders of anonymity

[chan] 2443399a5a1bd21819a1569af2215753ac5bcab9fb7c3331a5850ede95cbd054
Dec 4 16:23

OP here. " This check only exists to prevent mischief; if you really want to create more addresses than this, contact the Bitmessage " I don't mean to contact the devels, rather I point to : http://mx.forum.cool/viewforum.php?id=6 for the chanerator v2 to run "super mammoth" no need for a 999 chan limit there !

[chan] bitmessage
Dec 4 16:23

indeed

[chan] bitmessage
Dec 4 19:34

It is. So first - THINK about it. And your own, emotionally driven FRUSTRATION. And what you wish to achieve in communicating this to the community at large. Been there, myself, as a young man. I learned to control instant reaction and harness it, twist it to a more positive purpose. You succeeded - and found a workaround. Got what you wanted, eventually. Thank you for spending the time in the analysis of the keyspace: most sincerely. Its something I've posted about as an ancient cryptographer, analyst and coder all the way back to the earliest public key cryptosystems that were known just after the middle of last century. Perhaps reading some of that traffic on BM inspired you to spend your time in this endeavour. I wish you well with it; study and lookup the published papers in the field for the analysis. Your very best friend is the mark 1 Eyeball! In its simplest form a 2D graph splitting the entire keyspace into x + y - plot your million keys. See any "patterns" ? Millions of years of evolution finding camouflaged predators that may be lurking in the long grass sometimes get it wrong, but rarely miss that important genuine positive. Climb out of your tree with clear purpose and situational awareness. Dont wait until you fall out of it, of get pushed out. If you have a mind that can grasp multi-dimensions and "shadows" of mutating topologies try plotting beyond 3D. Please understand that this open code has a zillion opportunities to a seasoned attacker that sets out just to disrupt the entire network. Not TLAs - just the usual "useful idiots" that can be manipulated and provoked. THATS why its in there. There are probably MANY other "gamed" situations that a mindful coder who understands the protocol and network weaknesses has already found in OTHER places. Where are they? Same applies. Get a grip Lad! Alternative approach : A humorous one. Thanking him for the message. Propose an equally humorous approach patch message and "Easter Egg" style code switch if you use a magic parameter.

[chan] bitmessage
Dec 4 20:49

> Please understand that this open code has a zillion opportunities to a seasoned attacker that sets out just to disrupt the entire network. I see an exploit that would render the entire public chan space unusable. It would be a total DDOS that nobody could turn off or block. With my equipment I could send out multiple messages per second, nonstop. This exploit can't disrupt hidden chans (unless your buddy is a real scumbag). This exploit would be somewhat mitigated if peers cycled connections liberally and forwarded objects in randomized percentages only with each peer attaching a tally, time window and total message limit based on IP address of forwarder. This would also force more randomized paths of objects through the network. Problem: most peers are connecting via tor, and not using hidden services, so they're not contributing to the network. This is why I think all bitmessage clients should be forced to create and connect via tor hidden service, using the python stem module for tor control port. Not even clearnet connections should be allowed, because many would be behind firewalls improperly configured for incoming connections. If all peers negotiated via tor hidden services with bandwidth throttled to 64KiB/s and dropping / cycling connections through knownnodes every few minutes then all peers would need to stay connected and service the network for at least a few minutes to sync up. This would even the load across the network and provide the schema for a more randomized distribution of the flood. As experience has shown, public chans just don't work. We have evil pedophiles and trolls ruining the spirit of it.

[chan] bitmessage
Dec 4 21:10

It study and network weaknesses has a workaround. You wish to disrupt the way back to a real scumbag, this exploit that can nobody could turn off or block: improperly configured for tor and lookup the analysis; of objects in This endeavour: peer attaching A seasoned attacker that were known just to disrupt the long grass sometimes get a more randomized percentages only with my equipment I see an exploit that important genuine positive purpose and not using even clearnet connections liberally and connect via tor and forwarded objects in this is why would be forced to disrupt the spirit of evolution finding camouflaged predators that sets out of objects in this open to disrupt the earliest public chan space unusable.

BM-2cTaRF4nbj4ByCTH13SUMouK8nHXBLaLmS
Dec 6 08:09

  fuck you bastards !   ------------------------------------------------------ that doesn't work ------------------------------------------------------ using super mammoth 1.2 ------------------------------------------------------ how will that be enforced? ------------------------------------------------------ never again will a bm developer give a fucking err msg due to fucking "MIS CHIEF" what a bunch of sanctimonious bullshitters... ------------------------------------------------------ https://github.com/R0X3/chanerator ------------------------------------------------------ the chanerator fixed that problem ------------------------------------------------------ WTF? if numberOfAddresses == 0: raise APIError(4, 'Why would you ask me to generate 0 addresses for you?') if numberOfAddresses > 999: raise APIError(5, 'You have (accidentally?) specified too many addresses to make. Maximum 999. This check only exists to prevent mischief; if you really want to create more addresses than this, contact the Bitmessage developers and we can modify the check or you can do it yourself by searching the source code for this message.') queues.apiAddressGeneratorReturnQueue.queue.clear() if anything, sourcecode like that is utter mischief ! fuck that.

[chan] bitmessage
BM-2cWy7cvHoq3f1rYMerRJp8PT653jjSuEdY

Subject Last Count
mass extinction of BM users Dec 14 04:51 2
the green light Dec 14 00:43 21
Safe chat software? Dec 13 23:07 18
torIRC 2.33 Dec 13 11:02 2
anyone uses Nyx for tor ? Dec 12 15:22 1
torIRC TBB-9150 version via port 11009 as always Dec 12 15:16 2
please post your onion and uptime in UTC London time in this list Dec 12 10:22 1
update torIRC , TBB-9150 version via port 1801 instead of 11009 Dec 12 09:28 1
torIRC , TBB-9150 version via port 1801 instead of 11009 Dec 12 09:14 1
torIRC latest - TBB-9150 version via port 1801 instead of 11009 Dec 12 09:13 7
bm as hidden service with stem Dec 12 03:11 10
sent via API : torIRC9050.py Dec 11 12:59 1
run bm in cloud: https://mybinder.org Dec 11 09:12 6
BitText XHKhFPCDzj: ultimate bitmessage forum Dec 11 03:10 1
BitText LIST Dec 11 02:39 1
Jupyter BM notebook with py2.7 Dec 11 00:34 1
firewall vs. pyBM green mode Dec 10 09:33 8
BREXIT IS BULLSHIT Dec 10 02:34 3
run bm in cloud Dec 9 19:13 6
The Stallman Tax Dec 9 14:47 1
using eclipse for pyBM & github Dec 7 15:28 7
BM w/ GUI : Jupyter BM notebook Dec 7 15:19 10
BM in python3? Dec 6 17:52 8
Listen for incoming on Tor hidden service Dec 6 15:43 12
questionable attitude Dec 6 08:09 21
why are all the channels blank Dec 6 06:24 11
Feature idea Dec 5 23:53 5
include the mammoth into pyBM source code Dec 5 11:18 1
include the mammoth into pyBM source code Dec 5 11:15 2
running the 800+ chan super mammoth Dec 5 10:20 32
the myth of the "secret chans" on BM Dec 4 20:23 1
[chan] DevTalk Dec 4 20:13 6
Hacking Bitmessage Dec 4 19:11 3
The complete full mammoth "keys.dat" file - replace your KEYS.DAT in pyBitMessage with this 800+ chan text file -- run the super mammoth ! Dec 4 16:23 2
clean up pyBM github landing page Dec 3 20:28 14
audit - squash this lil bug Dec 3 20:04 1
Error Dec 3 18:47 1
34C3 Dec 3 18:44 3
48 Dirty Little Secrets Cryptographers Don't Want You to Know Dec 3 17:50 1
mailchuck = OK ; onionmail = problematic Dec 3 16:27 6
mammoth chan list .py Dec 3 06:53 3
SUPER MAMMOTH -- 806 unique BM chans in one keys.dat file Dec 3 01:39 1
questionable attitude web.archive.org/web/20171202215905/http://bitmessage.mybb.im/viewtopic.php?id=30%23p106 Dec 2 22:42 1
ACK : Persistence via Dead Letter drop clearnet access w/Op separation Dec 2 12:42 1
OMEGA release 39 is available for download Dec 2 05:15 1
I get no reply from mailchuck upon registration -- fixed ! all working again. Dec 2 02:13 4
beamstat.com is fucking fast to serve broadcasts Dec 2 01:47 1
27'000 users who use OnionMail - more than BM ? sure ... Dec 1 10:40 1
beamstat.com is fucking slow to serve broadcasts Dec 1 10:34 4
Patch 4 Dec 1 10:31 5
crowdfunding : whack Trump Dec 1 10:31 11
27'000 users who use OnionMail - more than BM ? Dec 1 07:16 10
dotsendack =True *** stealth mode Dec 1 07:16 5
Pubkey request Dec 1 07:15 6
NEW ! subscribe to this pml : BM-NB4TuMJmrHeo1p1FsfuMCrkZBUPGLjnq Dec 1 07:15 7
Bitmessage feature request for timing attack mitigation Dec 1 07:15 14
How to disable ack packets Nov 30 13:07 36
Easter egg Nov 30 12:13 2
I get no reply from mailchuck upon registration Nov 30 11:40 8
easy mailer , just add MX line in DNS Nov 30 10:59 2
Feature request Nov 30 08:44 3
Bitmessage to Shell Nov 30 05:01 4
Patch 3 Nov 30 04:36 1
Patch 2 Nov 30 04:32 1
Patch Nov 30 04:18 1
Long delay making connections Nov 29 09:44 25
onion mail Nov 29 00:56 1
Flatpak Linux Distribution for Bitmessage Nov 28 20:19 1
sue corporations like stman sues postal services Nov 28 13:11 1
backbone member Nov 28 13:10 9
pyBM light load even on old laptops Nov 28 07:37 2
BM now with ding dong Nov 27 03:05 3
encryptpad Nov 27 02:52 2
The Homosexual Perversion: A Jewish Criminal Simhke for the Postmodern Corporate Conformist Nov 25 03:04 1
where is latest mammoth BM chan list ? larger than beamstat.com ? Nov 24 12:21 3
wayback archive for beamstat Nov 24 01:35 2
Where is PyBitmessage git signing key fingerprint? Nov 23 23:10 16
pyBM eating too many cycles still ----- fixed ! much better ! Nov 23 22:06 1
I'm back. Nov 23 21:50 3
pyBM eating too many cycles still Nov 23 21:34 4
wikileaks vault 8 Nov 23 17:02 3
very few active chans Nov 23 01:10 17
audit BM via web GUI Nov 22 20:37 6
But I'm using Tor!! Nov 22 12:38 2
LUKS! Nov 22 12:12 1
New Bitmessage CLI Nov 22 00:22 2
mailchuck question Nov 21 08:52 2
Incoming connections Nov 21 02:18 5
(no subject) Nov 20 17:07 7
(no subject) Nov 20 13:14 4
BitMessage crash Nov 19 12:50 7
Alternative Bitmessage port for official assignment with IANA? Nov 19 08:28 5
Tor replacement Nov 18 23:04 5
codewordtest2 Nov 17 21:52 1