gaearon

import React, { Component } from 'react';
import { createStore, combineReducers, applyMiddleware, bindActionCreators } from 'redux';
import { provide, connect } from 'react-redux';
import thunk from 'redux-thunk';

const AVAILABLE_SUBREDDITS = ['apple', 'pics'];

// ------------
// reducers
// ------------

Istar-Eldritch

'use static';

const http = require('http');
const most = require('most');

const port = 3000;

const server = http.createServer();

most.fromEvent('listening', server).forEach(() => {

forabi

❯ rollup --version
rollup version 0.25.3

❯ time rollup -c ./rollup.js                      
rollup -c ./rollup.js  4.65s user 0.22s system 118% cpu 4.131 total

❯ time webpack                      
Hash: ebb00bbccd954c114d3c
Version: webpack 2.0.7-beta
Time: 3623ms

whiteinge

/**
Proof-of-concept server-sent events HTTP server using Node.js and RxJS

Open http://localhost:8000 in a browser and view the console.
**/
var http = require('http'),
    https = require('https');

var Rx = require('rx');

rmtsrc

PostgreSQL JSON Cheatsheet

Using JSON in Postgres by example.

Quick setup via Docker

1. Download and install: Docker Toolbox
2. Open Docker Quickstart Terminal
3. Start a new postgres container:
   docker run --name my-postgres -e POSTGRES_PASSWORD=mysecretpassword -d postgres

TylorS

import {Stream} from 'most'

const fromNodeCallBack = fn => (...args) => new Stream(new CallBackSource(fn, args))

class CallBackSource {
  constructor (fn, args) {
    this.fn = fn
    this.args = args
  }

bloodearnest

#!/bin/bash
set -eu
_UID=$(id -u)
GID=$(id -g)

# give lxd permission to map your user/group id through
grep root:$_UID:1 /etc/subuid -qs || sudo usermod --add-subuids ${_UID}-${_UID} --add-subgids ${GID}-${GID} root

# set up a separate key to make sure we can log in automatically via ssh
# with $HOME mounted

bithavoc

CREATE OR REPLACE FUNCTION notify_trigger() RETURNS trigger AS $$
	DECLARE
		channel_name varchar DEFAULT (TG_TABLE_NAME || '_changes');
	BEGIN
		IF TG_OP = 'INSERT' THEN
			PERFORM pg_notify(channel_name, '{"id": "' || NEW.id || '"}');
			RETURN NEW;
		END IF;
		IF TG_OP = 'DELETE' THEN
			PERFORM pg_notify(channel_name, '{"id": "' || OLD.id || '"}');

sagivo

to check if the server works - https://webrtc.github.io/samples/src/content/peerconnection/trickle-ice

stun:
stun.l.google.com:19302,
stun1.l.google.com:19302,
stun2.l.google.com:19302,
stun3.l.google.com:19302,
stun4.l.google.com:19302,
stun.ekiga.net,
stun.ideasip.com,

colophonemes

Postgres Distributed Key Generation

This SQL creates a Postgres function to generate sequential, numeric, unique IDs in a consistent format across services. Useful for database sharding or microservices.

Draws heavily on Instagram's ID generator, via Rob Conery, with minor modifications.

The main changes are that the unique number resolution is per-second rather than per-millisecond. This is to reduce key size below 2^53^-1 so that generated IDs that are under Javascripts Number.MAX_SAFE_INTEGER limit . This is important if you're using these on a Node.js server (e.g. our use case is an Express API using Hashids).

Max IDs are in the order of 51 bits, broken down as follows:

• 31 bits for the timestamp difference