Bryan English bengl

Create a GitHub account (if you don't already have one)
On the command line, in your home directory or a directory you have for projects, run: git clone https://github.com/nodejs/node.git
When that is done: cd node
Go to https://github.com/nodejs/node and use the "Fork" button to fork your own repo of node
On the page for your fork, use the "Clone or download" button and copy the URL for cloning to your clipboard, then run: git remote add mine <paste that URL here!>
Follow the instructions at https://github.com/nodejs/node/blob/master/BUILDING.md to build Node.js.
Email [email protected] or tweet at @NodeTodo to get a good first contribution to work on or to get help with any of the above steps.

Keybase proof

I hereby claim:

I am bengl on github.
I am bengl (https://keybase.io/bengl) on keybase.
I have a public key whose fingerprint is 37D2 6669 8039 4F22 43B7 FF45 145D 4E0D 7970 799A

To claim this, I am signing this object:

ham / amateur radio gear list for nodeconf

Elecraft KX3 (HF transciever)
Yaesu VX-8DR (VHF/UHF transciever)
AlexLoop Walkham (magnetic loop antenna, 40m - 10m)
RadioWavz G5RV Jr. (dipole antenna, 40m - 6m)
HackRF One
RTL SDR Dongle
Crappy power supply + battery power.
Probably more to come...

Populating npm caches with BitTorrent

NOTE: This concept has probably been covered before, so if anyone can point me in the direction of some prior art, that would be great.

This past June, I attended NodeConf for the first time. While it was an amazing event, and I've love to go next year, it wasn't without its hiccups. In particular, all the sessions involved some npm install, and with hundreds of programmers on a small pipe to the internet, this became rather tiresome rather quickly.

First of all, cheers to everyone involved in setting up npm registry mirrors at the event (npm, Inc. and others). This worked out reasonably well, but often the mirrors were just slightly out of date, which was problematic because many instructors were updating their course material in real-time.

This sort of situation seems like it can be relatively common, so lots of solution ideas came from this. Here is one such solution.

Keybase proof

I hereby claim:

I am bengl on github.
I am bengl (https://keybase.io/bengl) on keybase.
I have a public key whose fingerprint is F2FE 3552 09D6 F280 BF6A B807 FE32 AE04 E6BF 5E9E

To claim this, I am signing this object:


	// tern: const Thing = require('./thing.js')

	/**
	* @param {Thing} thing
	*/
	module.exports = function (thing) {
	thing.foo();
	}

	/**
	* Plop this in your node git repo and run:
	*
	* $ node commits.js [num of commits you want to analyse (default 1000)]
	*/

	var exec = require('child_process').exec;

	function gitDiffTree(commit, recursive, cb) {
	exec('git diff-tree --name-only --no-commit-id ' + (recursive ? '-r ' : '') + commit, function(err, data) {

	function ExtendedPromise (resolver) {
	Promise.call(this, resolver)
	}

	require('util').inherits(ExtendedPromise, Promise)
	ExtendedPromise.__proto__ = Promise

	new ExtendedPromise(function (resolve) {
	resolve(1)
	}).then(console.log)

	# hundreds of lines like this...
	info attempt registry request try #1 at 14:45:50
	http request GET https://registry.npmjs.org/media-typer/
	info attempt registry request try #1 at 14:45:50
	http request GET https://registry.npmjs.org/mime-types/
	info attempt registry request try #1 at 14:45:50
	http request GET https://registry.npmjs.org/mime-db/
	info attempt registry request try #1 at 14:45:50
	http request GET https://registry.npmjs.org/util-extend/
	info attempt registry request try #1 at 14:45:50

	var tessel = require('tessel');
	var camera = require('camera-vc0706').use(tessel.port['A']);

	var notificationLED = tessel.led[3];

	camera.on('error', function(err) {
	console.error(err);
	});

	camera.on('ready', function() {