RubenSomsen

L2 protocols

Trust protocols (not always auditable)

• Full custody (Coinbase)
• 2-of-3 arbitration / DLC
• Threshold multisig (ecash, Liquid)
• Off-chain peg-out tx (statechains)
• Collateralized custody

Payment channels

zzmp

/* REPO UNWATCHER
 *
 * This unwatches any repo that you don't specify.
 * It must be run from the console while you are at https://github.com/watching
 *
 * *No need to edit any code - the instructions will prompt you to list out the repos you'd like to keep watching!*
 */

var repo;
var repos = [];

bjtitus

#!/bin/bash 
# A simple script to backup an organization's GitHub repositories.
 
GHBU_BACKUP_DIR=${GHBU_BACKUP_DIR-"github-backups"}                  # where to place the backup files
GHBU_ORG=${GHBU_ORG-"<CHANGE-ME>"}                             # the GitHub organization whose repos will be backed up
GHBU_API=${GHBU_API-"https://api.github.com"}                        # base URI for the GitHub API
GHBU_GITHOST=${GHBU_GITHOST-"<CHANGE-ME>.github.com"}                            # the GitHub hostname (see comments)

# I recommend using an API token so it is easily trackable and removable.
# Note that you MUST have SSH keys for a user with the access to all repos set up

tcz

<?php

if ($argc !== 2)
{
	die("Usage: php {$argv[0]} hypem_user_name\n\n");
}

$user = $argv[1];
$page = 1;
$all_songs = array();

katowulf

/***************************************************
 * Simple and elegant, no code complexity
 * Disadvantages: Requires warming all data into server memory (could take a long time for MBs of data or millions of records)
 * (This disadvantage should go away as we add optimizations to the core product)
 ***************************************************/
 
var fb = firebase.database.ref();

/**
 * @param {string} emailAddress

nzakas

I'm doing some research on how companies use GitHub Enterprise (or public GitHub) internally. If you can help out by answering a few questions, I'd greatly appreciate it.

1. What is the primary setup? Is there an organization and each official repo is owned by that organization?
2. Does every engineer have a fork of each repo they're working on?
3. Are engineers allowed to push directly to the official repo? Or must all commits go through a pull request?
4. Do engineers work on feature branches on the main repo or on their own forks?
5. Do you require engineers to squash commits and rebase before merging?
6. Overall, what is the workflow for getting a new commit into the main repository?
7. What sort of hooks do you make use of?
8. Are there any ops issues you encountered? (Scaling, unforeseen downtime, etc.)

johntyree

#!/usr/bin/env sh

# Download lists, unpack and filter, write to stdout
curl -s https://www.iblocklist.com/lists.php \
  | sed -n "s/.*value='\(http:.*=bt_.*\)'.*/\1/p" \
  | xargs wget -O - \
  | gunzip \
  | egrep -v '^#'

brandonb927

#!/bin/sh

###
# SOME COMMANDS WILL NOT WORK ON macOS (Sierra or newer)
# For Sierra or newer, see https://github.com/mathiasbynens/dotfiles/blob/master/.macos
###

# Alot of these configs have been taken from the various places
# on the web, most from here
# https://github.com/mathiasbynens/dotfiles/blob/5b3c8418ed42d93af2e647dc9d122f25cc034871/.osx

nicerobot

To run this, you can try:

curl -ksO https://gist.githubusercontent.com/nicerobot/2697848/raw/uninstall-node.sh
chmod +x ./uninstall-node.sh
./uninstall-node.sh
rm uninstall-node.sh

jlong

var parser = document.createElement('a');
parser.href = "http://example.com:3000/pathname/?search=test#hash";

parser.protocol; // => "http:"
parser.hostname; // => "example.com"
parser.port;     // => "3000"
parser.pathname; // => "/pathname/"
parser.search;   // => "?search=test"
parser.hash;     // => "#hash"
parser.host;     // => "example.com:3000"