Topic: [ANNOUNCE] Bitmessage - P2P Messaging system based partially on Bitcoin - page 19. (Read 89882 times)

Do I have to be logged in 24-7 to not miss any bitmessages? (or at least once every day)

Bitmessage v0.3.0 is available. It is an important release with a new change relevant to everyone.
The most significant change is the move from version 2 to version 3 addresses.
With version 3 addresses, users may set the minimum-Proof-of-Work-difficulty that they require of others in order to receive a message. The network-minimum difficulty is 1 but you may, for example, demand that people who send you messages accomplish a proof of work with a difficulty of 1.5.
Before making new addresses, see the 'Demanded difficulty' tab in the settings menu.
The next new feature is encrypted broadcasts. Broadcasts sent from v3 addresses will now all be encrypted. Broadcasts sent from v2 addresses will remain in clear-text until 2013-05-28 at 10:00 UTC at which time all upgraded clients will automatically switch to using encrypted broadcasts for all addresses.
Note that broadcasts are only encrypted with the address of the person sending them.
Anyone who has the address may read the broadcast. Some people may try to decrypt all broadcasts with all addresses ever seen on the network; this is expected.
The purpose of this feature is to encrypt the data sufficiently well such that unencrypted data will not flow through your Internet connection that you are not actually interested in.
Going forward, all new addresses will be v3 addresses thus it would be wise to upgrade soon so that you may receive messages from new Bitmessage users. v2 and v3 addresses will remain mutually-compatible indefinitely.
The next new feature is Daemon mode which allows Bitmessage to run without a graphical user interface. https://bitmessage.org/wiki/Daemon
You may report issues to the Github issue tracker or by replying to this bitmessage. https://github.com/Bitmessage/PyBitmessage/issues
Users who downloaded the source code with git may use 'git pull origin master' to upgrade.
All the best, Atheros
https://bitmessage.org/
https://github.com/Bitmessage/PyBitmessage

Unfortunately Debian, Fedoria, (and thus others like Mint Linux) cannot run it as easily because their copies of OpenSSL doesn't include Elliptic Curve cryptographic functions for patent reasons.

Couple of pages ago (#102), I was asking for help with Debian Testing compilation, as Testing is provided with python2.7, but there is no PyQt4.QtCore for python2.7, only for python3.0, which is not supported by Bitmessage.

But on Ubuntu it's working fine, thanks I just compiled binary and installed it without problems.
I will have to look again on my Debian laptop

Hi,
I wasn't using BitMessage for couple of weeks. Is there any more support for Linux, or I still cannot use it on Linux as ready-to-go? Binaries, or something?
Why is only crappy Windows supported? 

My theory is that if you leave your client online for several hours you'll collect a bunch of IP addresses of nodes that connect for a few minutes and then disconnect.  When you restart the client it goes though that list of IP addresses one at a time trying to connect.  Since most of them are now offline and it takes about 5-10 seconds per connect attempt, it could take a long time to find the first live one.

I don't know this for sure, but deleting knownodes.dat seems to force the client to first connect to a known, hard-coded IP address that's online all the time.  That would explain why deleting the file speeds up the cold connect process.