Fixing Kademlia's K constant.

The current number of 80 defeats the whole purpose of
Kademlia routing, specially since the network is so small,
if we get to have 3 buckets it's probably luck (out of possible 160 buckets
used for routing if the routing has been implemented correctly).

With a K=80, there's very little chance for bucket splits, which
means, each peer is always contacting all the nodes that it knows
for searches. The idea of having buckets which separate peers by
their XOR distance is that we can half the number of searches necessary
if all nodes are organized by these rules.

If we have smaller K sized lists (buckets), we'll start contacting less
peers and getting results a lot faster, as these peers get to ask less peers
in an efficient way.
Quick fix test for sqlite different thread issue.

Found this solution on a stackoverflow thread.
I'm not sure if it fixes the problem as I can't replicate it
myself.

If you are getting this issue, please test this pull request

git remote add gubatron https://github.com/gubatron/OpenBazaar
git fetch gubatron
git checkout experimental-fix-sqlite-different-thread-issue-654

run openbazaar and let me know if the issue persists, or if now
this is causing even weirder issues.

This is far from the ideal solution, but it might fix the problem.

The right solution might be (if we need db fetched objects on another
thread) having a DB-querying thread which is responsible for performing
all DB fetch operations and keeping the consumable outputs
in a temporary container (dict or queue) which is then consumed by
other threads.
Merge pull request #918 from gubatron/experimental-fix-sqlite-different-thread-issue-654

Quick fix test for sqlite different thread issue. (Issue #654)
Fixing Node Addition UI

This commit adds a notification on the success or failure of adding a
new node. It will still report success if the GUID of an unreachable
store is given.

Fixing typo

Conistency
Merge pull request #932 from VivaLaPanda/develop

Fixing Node Addition UI
use thread locking to serialize all db access

also reenable check_same_thread so we get exceptions instead of crashes,
although that shouldn't be possible anymore with this locking in place

Signed-off-by: Thomas Stilwell <stilwellt@openlabs.co>
Merge pull request #937 from benemorius/db-locking

use thread locking to serialize all db access
Use booleans properly.
Use new octal notation (PEP 3127).
Added a Namecoin id input in settings
Added test for dbstore.getOrCreate

Fixed syntax
Merge pull request #939 from carolinux/test_coverage_improvements

Added test for dbstore.getOrCreate
move custom loglevel setup to node/__init__.py

Signed-off-by: Thomas Stilwell <stilwellt@openlabs.co>
log output: initial move to DATADUMP

Signed-off-by: Thomas Stilwell <stilwellt@openlabs.co>
add custom logging level DEBUGV=9

Signed-off-by: Thomas Stilwell <stilwellt@openlabs.co>
log output: initial move to DEBUGV

Signed-off-by: Thomas Stilwell <stilwellt@openlabs.co>
Merge pull request #884 from Renelvon/modern

Use forward-compatible python (part 1).
Merge pull request #889 from benemorius/log-datadump

log output: add DEBUGV and begin cleanup
When running configure.sh in Ubuntu, specify python2.7 for virtualenv.
Merge pull request #951 from tortxof/develop

When running configure.sh in Ubuntu, specify python2.7 for virtualenv.