We were working on something like this before. IIRC, the problem might be in the SQL library.

Yes, they are (see keys.dat in the config folder).  There's been some talk from time to time about implementing a master password and I think it will happen at some time, but so far the keys are stored in the clear.

Yup.... but things should be easier.

BTW: A "reply to channel" feature would be nice.

it is an useful feature to have the html displayed formatted, allows things like image sending, which might be a necessary feature for this to spread
but unfortunately as soon as you unselect the message you were looking at the display changes to unformatted and needs to be changed for seeing it formatted again, which is a barrier to general users

so is there a way to have it format html by default that is acessible to people not compiling their own clients?
ideally at some point this would be accessible through a checkbox in the settings, but for the time being is there a config to edit or something like that?

also, what would be nice for a future release is a image to base64 converter built into the client, that could vastly broaden the userbase for bitmessage

attachments sound like a good solution, thank you
is there any time frame for that?

https://bitmessage.org/forum/index.php?topic=3327.0
is that the solution or will it be something different?

Is it possible to monitor the BitMessage blockchain for responses to an address and then parse the incoming message?

I have done similar in Bitcoin using Bitcoinmonitor.net, which uses an http callback but I understand the same can be done without using BitcoinMonitor.net.

In Bitmessage I see the function getAllInboxMessages. Would that do what I am wanting?

Thanks

If you want to fund an audit, we'll find out.


There have been a number of concerns over scalability and security which have only been partially addressed. I can't speak too much about them because I've been rather distant from the project for a while, but AFAIK the scaling is still an unsolved issue, practically in the brainstorming stage. There are also a number of unfortunate misconceptions which have been propagated around the interwebs. Whenever Aetheros pops up with a well-reasoned response, he gets crickets. These include:

- But proof of work isn't a viable spam solution!
Email has no spam solution either, and yet it's done well for two decades. Spam in email is handled clientside, and this does not change with Bitmessage. Thunderbird (and other client) integration makes this simple. Proof-of-work is merely used to prevent flooding of the network.

- But wasn't it de-anonymized?!
No, some guy harvested addresses (which are public, because the existence of a particular address leaks no information), then sent out some spam. Users then copied and pasted an unclickable (by GUI design) link to an unknown website from an unknown sender into an unsecured web-browser, and were surprised when their IP address was then correlated with their intentionally disposable Bitmessage address which had no associated metadata. This still baffles me.

- But what about that one post on the Bitmessage forums with criticism?
Yes, we read the post. And then we discussed it. If you believe it contained an as-yet-unaddressed critical flaw, please let me know.

heartbleed? using openSSL...

..I had to quote this, for all that happened lately with heartbleed.. :-)

Finally I read through this whole thread.

- where is my (linux) userstuff? I'd expect something like ~/.bitmessage, but can't find anything. The program folder is 6mb, which can't contain the "blockchain".

- I believe it would help adoption *a lot* to have plugins for the common chatclients. Like kopete, for example. No matter if it's the whole bitmessage implementation, with huge size, as long as it visually fully integrates into the common clients. What do you people think?


Also, I am BM-2cWuHRsRAwfbCdzKKEKRf1nc2BwzPgRLN2

Ente