terinjokes

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

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

heapwolf

Namespacing

The concept of namespacing keys will probably be familiar if you’re used to using a key/value store of some kind. By separating keys by prefixes we create discrete buckets, much like a table in a traditional relational database is used to separate different kinds of data.

It may be tempting to create separate LevelDB stores for different buckets of data but you can take better advantage of LevelDB’s caching mechanisms if you can keep the data organised in a single store.

Because LevelDB is sorted, choosing a namespace separator character can have an impact on the order of your entries. A commonly chosen namespace character often used in NoSQL databases is ':'. However, this character lands in the middle of the list of printable ASCII characters (character code 58), so your entries may not end up being sorted in a useful order.

Imagine you’re implementing a web server session store with LevelDB and you’re prefixing keys with usernames. You may have entries that look like this:

MoOx

language: node_js

node_js:
- iojs

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

jessehattabaugh

/* Config - set the right values in the PhoneGap config.xml
******************************************************************************/
gulp.task('config', function () {
  return gulp.src([srcDir + '/config.xml'])
    .pipe(cheerio({
      run: function ($) {
        // get the version number from package.json
        $('widget').attr('version', require('./package').version); 
        
        // in development launch the app with a different html file

vaidd4

'use strict';
const parseMs = require('parse-ms');
const plur = require('plur');
const units = [{ s: 'y', l: 'year' },
	       { s: 'd', l: 'day' },
	       { s: 'h', l: 'hour' },
	       { s: 'm', l: 'minute' },
	       { s: 's', l: 'second' },
	       { s: 'ms', l: 'millisecond' }];

cblgh

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

pfrazee

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:

campadrenalin

Getting started with Meshnet

This document is for people who want to help but have no technical knowledge. It assumes you won't be getting involved in squabbles over which relay technology to use, etc.

Step 1: Set up CJDNS

One of the few things widely agreed upon at the time of this writing is the use of CJDNS. Currently Windows is not supported, but if you have Linux or can run Linux in a virtual machine, you can follow the step-by-step instructions lower on that page to install and start up an instance of CJDNS on your system. If you're using Ubuntu 11.10 (latest version), you can follow these simplified instructions.

One thing you should know is cjdns currently isn't a wireless meshnet. A physical meshnet consisting of nodes geographically close to each other is a long way off. Instead, cjdns offers a "mixnet"-like system. cjdns is routable over the current Internet, so this means right now its like a giant VPN (virtu

tmcw

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

constantology

// use like this:
// process.emit( 'app:log', module, arg1, arg2, ..., argN );

var Module = require('module');

function logConsole(method, module) {
  var args = [(new Date()).toJSON(), method];
  var index = 1;

  if (module instanceof Module) {