Usage statistics of Bitmessage

If you run your Bitmessage client with nohup (like I am suggesting in this article) you can view the statistics about nodes that are currently online:

$ cd $HOME/PyBitmessage/src/ && tail -f nohup.out  | grep ^knownNodes

knownNodes currently has 2059 nodes for this stream.

This is the estimate of the currently online users.

Also you can see the statistics on the "Network Status" tab.

Comments

  1. AnonymousOctober 9, 2014 at 5:19 PM

    Looks like 20 000 is the hardcoded maximum:

    "knownNodes currently has 20000 nodes for this stream."

    ReplyDelete
  2. AnonymousOctober 9, 2014 at 5:25 PM

    Bitmessage collects up to 20000 node addresses and connect them randomly. It has a "value" algorithm to determine, how reliable a node is. It uses connect/fail ratio and number of offered objects to calculate the value.

    The value has no influence on which node it tries to contact, this is pure random.

    ReplyDelete

Post a Comment

Popular posts from this blog

Do not use (only) flash memory (SSD drives, hardware wallets, USB flash drives) for your precious private keys!

Image
Flash memory is not a reliable medium for archives. Especially when there is no regular power. I have personal experience with usb flash drive not powered for weeks - one file became corrupted . (Read more here: Archiving private keys - TLDR version. ) You should always back up on paper and other mediums. Flash memory is prone to failure if it is not powered for weeks or more and if there are ionizing radiation When you write your precious private keys you should use technologies like Parchive and ZFS . And make several copies of your files. It's OK if you use your USB flash drive for another backup, but don't rely on it! Always back up on DVDs (even small files!), paper and online (after encryption with CPU and RAM intensive key derivative function like scrypt). Here is example of using the scrypt utility: $ sudo apt-get install scrypt $ scrypt enc -M 1073741824 -t 200 secret.txt encrypted.scrypt Do not use default values of "-M" and "-t", they...
Read more

Archiving private keys - TLDR version

0. Make multiple encrypted copies. On DVDs (they are better than CDs and Blu-Ray discs; DVD+R are better than DVD-R), paper, cloud services like DropBox, OneDrive, Google Drive, e-mail it to yourself and to your friends, use P2P storage services like MaidSafe, Storj and Sia , etc. 1. Use proper font when printing PGP encrypted keys on paper. 2. Flash memory (SSD, USB flash drives, hardware wallets) is less reliable when not powered regularly (i.e. every week). 3. Use error correction methods like Parchive and ZFS. 4. Print on paper or store on digital media only encrypted data. 5. Your encryption software should use CPU/RAM-intensive KDF (i.e. scrypt with secure options - do not use defaults! ). First, encrypt with scrypt and then encrypt it again with PGP (using different password!) in ASCII armor mode before print it (other methods like QR codes may not be reliable as multiple copies of the PGP ASCII armor). Do not use the same password for the PGP because it's easy to brute...
Read more
[ad removed]