austintgriffith

pragma solidity ^0.4.11;

contract LinkedList {

  event AddEntry(bytes32 head,uint number,bytes32 name,bytes32 next);

  uint public length = 0;//also used as nonce

  struct Object{
    bytes32 next;

ageis

YubiKey 4 series GPG and SSH setup guide

Written for fairly adept technical users, preferably of Debian GNU/Linux, not for absolute beginners.

You'll probably be working with a single smartcard, so you'll want only one primary key (1. Sign & Certify) and two associated subkeys (2. Encrypt, 3. Authenticate). I've published a Bash function which automates this slightly special key generation process.

chrisallick

#https://medium.com/crypto-currently/lets-build-the-tiniest-blockchain-e70965a248b
#http://ruby-for-beginners.rubymonstas.org/writing_classes/self.html
#https://stackoverflow.com/questions/33768598/ruby-sha-256-hexidigest-values-are-different-from-what-python-generates

#import hashlib as hasher
require "rubygems"
require "digest"

# class Block:
#   def __init__(self, index, timestamp, data, previous_hash):

evertonfraga

First, install the required software:

• Geth: http://geth.ethereum.org/downloads/
• Mist: http://github.com/ethereum/mist/releases

Instructions for Windows

• Open CMD (windows > run > type "cmd" > enter).
• Run geth.exe --dev --ipcpath geth.ipc console

zcaceres

Nested Routers in Express.js

Express makes it easy to nest routes in your routers. But I always had trouble accessing the request object's .params when you had a long URI with multiple parameters and nested routes.

Let's say you're building routes for a website www.music.com. Music is organized into albums with multiple tracks. Users can click to see a track list. Then they can select a single track and see a sub-page about that specific track.

At our application level, we could first have a Router to handle any requests to our albums.

const express = require('express');

tayvano

Originall From: Posted 2015-05-29 http://ubwg.net/b/full-list-of-ffmpeg-flags-and-options

This is the complete list that’s outputted by ffmpeg when running ffmpeg -h full.

usage: ffmpeg [options] [[infile options] -i infile]… {[outfile options] outfile}…

Getting help:
    -h — print basic options
    -h long — print more options
    -h full — print all options (including all format and codec specific options, very long)

sarveshseri

First of all, lets understand few date-time standard definitions.

ISO Time String

The standard that we are talking about is formally named ISO 8601:1988 but is popularly also called ISO 8601

ISO 8601 also has support for

• years before 0 AD or after 9999
• Week based dates
• Ordinal dates

k33g

<div id="demo">
    <h1>{{bob.fields.firstName}} {{bob.fields.lastName}}</h1>
</div>

<ul id="humans-list">
    <li v-repeat="humans">
        {{fields.firstName}} {{fields.lastName}}
    </li>
</ul>

reiki4040

package main

import (
	"fmt"
	"os"
	"os/signal"
	"syscall"
)

func main() {

brson

A Guide to Rust Syntax

A very brief guide to Rust syntax. It assumes you are already familiar with programming concepts.

This was written in 2014. It is not a good reference for Rust today, though the content is still correct.

cheats.rs looks like a good alternative.

Assert macro