gate3

package main

import (
	"database/sql/driver"
	"encoding/json"

	"github.com/jinzhu/gorm"
	_ "github.com/lib/pq"
)

gate3

pragma solidity ^0.4.11;

/**
 * Math operations with safety checks
 */
library SafeMath {
  function mul(uint a, uint b) internal returns (uint) {
    uint c = a * b;
    assert(a == 0 || c / a == b);
    return c;

gate3

# Redis Cheatsheet
# All the commands you need to know


redis-server /path/redis.conf  # start redis with the related configuration file
redis-cli                      # opens a redis prompt


# Strings.

gate3

#!/usr/bin/env bash
# This script is meant to build and compile every protocolbuffer for each
# service declared in this repository (as defined by sub-directories).
# It compiles using docker containers based on Namely's protoc image
# seen here: https://github.com/namely/docker-protoc

set -e

REPOPATH=${REPOPATH-/opt/protolangs}
CURRENT_BRANCH=${CIRCLE_BRANCH-"branch-not-available"}

gate3

const git = require('nodegit')
const fs = require('fs-extra')
const { URL } = require('url')
const REPO_URL = 'git@github.com:org/path.git'
const CLONE_DIR = '/tmp/private-repo-clone-test'

;(async () => {
  await fs.emptyDir(CLONE_DIR)
  let authAttempted = false
  await git.Clone.clone(REPO_URL, CLONE_DIR, {

gate3

Stopping spam

This blog post by Jonathan Brown suggested replacing SMTP with Ethereum blockchain; specifically, utilizing the log channel to monitor events.

With this approach, emails wouldn't actually be stored within the EVM (Ethereum Virtual Machine) storage, but every email would still be present in the blockchain blocks. The EVM log mechanism would make it simple for a full node to monitor and be alerted whenever an email was submitted.

I don't believe that this would be feasible in the real world, for several reasons

• There are lots of email being sent, some of them quite large
• Most people wouldn't want their emails forever on the blockchain, the future resiliency of GPG is unknown, and GPG encryption does not provide perfect forward secrecy. Once a key is compromised, all is revealed.

gate3

default:
	cc ccsmtp.c -o ccsmtpd -lpthread

gate3

<?php
/**
 * Get current Laravel active session from outside laravel instance.
 * Tested Laravel 5.2
 * 
 * 
 */
function getLaravelUser()
{
    require __DIR__ . '\path\to\bootstrap\autoload.php';