mrry

# Copyright 2015 The TensorFlow Authors. All Rights Reserved.
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
#     http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,

martinwicke

duluca

{
  "name": "playground",
  "version": "1.0.0",
  "main": "server/app.js",
  "private": true,
  "scripts": {
    "clean": "npm run clean:client && npm run clean:server",
    "clean:client": "rm -rf public/*.* && rm -rf public/**/*.* && rm -rf src/ts/*.js && rm -rf src/ts/**/*.js",
    "clean:server": "rm -rf server/*.{js,d.ts} && rm -rf server/**/*.{js,d.ts}",
    "compile": "npm run compile:client && npm run compile:sass && npm run compile:server && npm run compile:static",

joepie91

Your blockchain must have all of the following properties:

• It's a merkle tree, or a construct with equivalent properties.
• There is no single point of trust or authority; nodes are operated by different parties.
• Multiple 'forks' of the blockchain may exist - that is, nodes may disagree on what the full sequence of blocks looks like.
• In the case of such a fork, there must exist a deterministic consensus algorithm of some sort to decide what the "real" blockchain looks like (ie. which fork is "correct").
• The consensus algorithm must be executable with only the information contained in the blockchain (or its forks), and no external input (eg. no decisionmaking from a centralized 'trust node').

If your blockchain is missing any of the above properties, it is not a blockchain, it is just a ledger.

therightstuff

Please see the original article for a full explanation. Please feel free to comment, question and criticize there as well!

Prerequisites

Requires https://www.npmjs.com/package/simple-free-encryption-tool

Notes

• compiled from multiple sources and much trial and error, feel free to use and pass on
• this is not exhaustive, it's meant only as a guide

royling

Install tmux

brew install tmux

Start tmux (https://gitlab.com/gnachman/iterm2/wikis/TmuxIntegration)

Run tmux -CC or tmux -CC attach in iTerm2 and then menu is shown on terminal:

• ESC to detach
• C to run commands
• X to force quit
• L for log

subfuzion

Go has excellent build tools that mitigate the need for using make. For example, go install won't update the target unless it's older than the source files.

However, a Makefile can be convenient for wrapping Go commands with specific build targets that simplify usage on the command line. Since most of the targets are "phony", it's up to you to weigh the pros and cons of having a dependency on make versus using a shell script. For the simplicity of being able to specify targets that can be chained and can take advantage of make's chained targets,

EncodeTS

VGG-Face model for Keras

This is the Keras model of VGG-Face.

It has been obtained through the following method:

• vgg-face-keras:directly convert the vgg-face matconvnet model to keras model
• vgg-face-keras-fc:first convert vgg-face caffe model to mxnet model,and then convert it to keras model

Details about the network architecture can be found in the following paper:

vasanthk

System Design Cheatsheet

Picking the right architecture = Picking the right battles + Managing trade-offs

Basic Steps

1. Clarify and agree on the scope of the system

• User cases (description of sequences of events that, taken together, lead to a system doing something useful)
  • Who is going to use it?
  • How are they going to use it?

julz

package main

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

func main() {