start new:
tmux
start new with session name:
tmux new -s myname
// http://w3c-test.org/webperf/specs/NavigationTiming/ | |
(function( window ) { | |
// Skip unsupported browsers | |
if ( ! window.performance || ! window.performance.timing ) { | |
return; | |
} | |
// Output | |
function perf(){ |
(function() { | |
function DateDiff(date1, date2) { | |
this.days = null; | |
this.hours = null; | |
this.minutes = null; | |
this.seconds = null; | |
this.date1 = date1; | |
this.date2 = date2; |
#301 Redirects for .htaccess | |
#Redirect a single page: | |
Redirect 301 /pagename.php http://www.domain.com/pagename.html | |
#Redirect an entire site: | |
Redirect 301 / http://www.domain.com/ | |
#Redirect an entire site to a sub folder | |
Redirect 301 / http://www.domain.com/subfolder/ |
/*! | |
* backbone.collectioncache.js v0.0.2 | |
* Copyright 2012, Tim Branyen (@tbranyen) | |
* backbone.collectioncache.js may be freely distributed under the MIT license. | |
*/ | |
(function(window) { | |
"use strict"; | |
// Dependencies |
package main | |
import ( | |
"fmt" | |
"net/http" | |
"time" | |
) | |
var urls = []string{ | |
"https://splice.com/", |
require 'rubygems' | |
require 'net/ssh' | |
# Run this on the machine (node) which needs to tunnel out to forward the UI to the remote system (console) | |
Net::SSH.start("remote_host", "remote_user") do |ssh| | |
# since we are running sinatra locally we will forward 43210 on the remote_host to our localhost 4567 | |
# This is effectively the same as: | |
# ssh -R 4567:localhost:43210 remote_user@remote_host | |
ssh.forward.remote(4567, "localhost", 43210) | |
ssh.loop { true } |
// Just before switching jobs: | |
// Add one of these. | |
// Preferably into the same commit where you do a large merge. | |
// | |
// This started as a tweet with a joke of "C++ pro-tip: #define private public", | |
// and then it quickly escalated into more and more evil suggestions. | |
// I've tried to capture interesting suggestions here. | |
// | |
// Contributors: @r2d2rigo, @joeldevahl, @msinilo, @_Humus_, | |
// @YuriyODonnell, @rygorous, @cmuratori, @mike_acton, @grumpygiant, |
With the scarecity of IPv4 addresses, and IPv6 still not available at large, NAT traversal is becoming a necessity. Especially with the generalisation of Carrier-grade NATs that you can find on mobile connections. Even with IPv6 you may suffer NAT66. Imagine your mobile device that gets only a single Ipv6 address, and you want to share it on your computer.
The solution might be in a decentralized protocol for address attribution such