Mauve Signweaver RangerMauve

DHT Walkthrough Notes

I've put together these notes as I read about DHT's in depth and then learned how the libtorrent implementation based on the Kademlia paper actually works.

What problem does this solve?

400,000,000,000 (400 billion stars), that's a 4 followed by 11 zeros. The number of atoms in the universe is estimated to be around 10^82. A DHT with keys of 160 bits, can have 2^160 possible numbers, which is around 10^48

Bridging Native & React for iOS & Android

js -> native

native -> js

low level primitives (in ascending abstraction)

hypercore works with individual posts in an append-only feed
hyperdrive abstracted filestore / works with files
hyperdiscovery create p2p swarms for hypercores, hyperdrives, and hyperdbs
hyperdb key-value database

higher level abstractions

webdb database; basically a document(?) store
dat-node built ontop of hypercore & hyperdrive, abstracts a bunch of stuff; less complex but also less flexible

So, as I mentioned last time, I have two fundamental goals with dat that are not addressed by simply running dat share.

Uptime: making sure that the site is seeded even if my local laptop is closed, eaten by a bear, or disconnected from the internet
Resilience: ensuring that there's a way to restart my website if the original seeding computer is lost. I try to make everything on my primary work/personal computer work in such a way that I can recover it all, easily, onto a new machine if I need to

To break these down a bit more, uptime is a combination of two things:

Ensuring that there are seeders
Ensuring that those seeders are seeding, and they're up-to-date

New APIs in Beaker 0.8

This Gist is a quick writeup for devs using the beta or master build. We'll get a more complete writeup in the Beaker site docs on 0.8's final release. Feel free to open issues for discussion.

DatArchive

We've done some work on the DatArchive API to make it easier to use. Prior to 0.8, Dats had a "staging area" folder which you had to commit() to publish. In 0.8, Beaker will automatically sync that folder. As a result, the staging-area methods (diff() commit() and revert()) were deprecated. There are also some new methods, and a few changes to how events work.

Here's a full reference:

	var Browserify = require('browserify');
	var Readable = require('stream').Readable;

	function stringStream(content) {
	var s = new Readable();
	s.push(content);
	s.push(null);
	return s;
	}

	language: node_js

	node_js:
	- iojs

	env:
	global:
	# https://docs.saucelabs.com/ci-integrations/travis-ci/
	# SAUCE_USERNAME
	- secure: Daa...

	RN < 0.50 - watchman watch-del-all && rm -rf $TMPDIR/react-* && rm -rf node_modules/ && npm cache clean && npm install && npm start -- --reset-cache
	RN >= 0.50 - watchman watch-del-all && rm -rf $TMPDIR/react-native-packager-cache-* && rm -rf $TMPDIR/metro-bundler-cache-* && rm -rf node_modules/ && npm cache clean && npm install && npm start -- --reset-cache
	RN >= 0.63 - watchman watch-del-all && rm -rf node_modules && npm install && rm -rf /tmp/metro-* && npm run start --reset-cache

	npm >= 5 - watchman watch-del-all && rm -rf $TMPDIR/react-* && rm -rf node_modules/ && npm cache verify && npm install && npm start -- --reset-cache

	Windows - del %appdata%\Temp\react-native-* & cd android & gradlew clean & cd .. & del node_modules/ & npm cache clean --force & npm install & npm start -- --reset-cache

	// Create a Promise that resolves after ms time
	var timer = function(ms) {
	return new Promise(resolve => {
	setTimeout(resolve, ms);
	});
	};

	// Repeatedly generate a number starting
	// from 0 after a random amount of time
	var source = async function*() {

	adb devices

	adb shell screencap -p /sdcard/screen.png
	adb pull -p -a /sdcard/screen.png
	adb shell rm /sdcard/screen.png

	For /f "tokens=2-4 delims=/ " %%a in ('date /t') do (set mydate=%%c-%%a-%%b)
	For /f "tokens=1-3 delims=/:" %%a in ("%TIME%") do (set mytime=%%a-%%b-%%c)
	set mytime=%mytime: =%