Bitmessage security breach?

[geofflosophy]

This address: BM-2DAxNoKvxLrSxRM9M19W1tu9mnAuwWrXMx was logged 21 times with various IP because the message was posted on the Internet. Right here: http://www.chronicles.no/2013/08/bitmessage-crackdown.html if my memory is right.

Ah very good point. So that address is about as public as it gets, huh? I guess there's nothing wrong with that really, plenty of people post their bitmessage addresses on the web, the contents of messages still can't be read. If anyone wants to talk dirty to me, you know where to send...

[drawingthesun]

So the addresses are public like Bitcoin addresses that have spent coins are public?

Doesn't sound like a issue with the Bitmessage network.

However about the scaling issue, is that going to be modified or not? Any chance Bitmessage could scale to a billion messages a day?

[01BTC10]

This address: BM-2DAxNoKvxLrSxRM9M19W1tu9mnAuwWrXMx was logged 21 times with various IP because the message was posted on the Internet. Right here: http://www.chronicles.no/2013/08/bitmessage-crackdown.html if my memory is right.

Ah very good point. So that address is about as public as it gets, huh? I guess there's nothing wrong with that really, plenty of people post their bitmessage addresses on the web, the contents of messages still can't be read. If anyone wants to talk dirty to me, you know where to send...

I mean the content of the message was posted online:

A message written to trick users into clicking on the link.

And every address on Bitmessage did receive a unique URL, like:
http://secupost.net/3240982275/bitmessage-security
http://secupost.net/760979548/bitmessage-security
http://secupost.net/4224282573/bitmessage-security
http://secupost.net/4278472862/bitmessage-security
http://secupost.net/1189531455/bitmessage-security

I'm guilty for clicking on one of them. This is why my IP address is there even if I never used BM. Hope that the party van is not on the way 

[geofflosophy]

So the addresses are public like Bitcoin addresses that have spent coins are public?

Doesn't sound like a issue with the Bitmessage network.

However about the scaling issue, is that going to be modified or not? Any chance Bitmessage could scale to a billion messages a day?

I'm just guessing here, but I would think that the network should scale better with usage. Flooding the network with messages without increasing the number of users running the client might not be best stress test of scalability. The two things from this that are of concern RE: scalability though are SPAM potential of public addresses and intentional flooding of the network to slow it down (kind of like a BM DDoS attack). SPAM is a very hard problem to solve in the email world, and anti-spam is literally a billion dollar industry. I don't think the equivalent could develop for BM without compromising security.

All of that said, it seems like a simple solution could solve all of these problems: require a hashing PoW function as part of a message send. The original Hashcash algorithm that the bitcoin hashing algorithm was based on was designed for this purpose. Maybe this is how BM works already? Doubt it though, I'd think it would have been a lot harder for him to send all of those messages out if it was.