kobigurk

import "owned";

contract NameReg is owned {
  	event AddressRegistered(address indexed account);
  	event AddressDeregistered(address indexed account);

	function NameReg() {
		toName[this] = "NameReg";
		toAddress["NameReg"] = this;
		AddressRegistered(this);

chrismdp

# You don't need Fog in Ruby or some other library to upload to S3 -- shell works perfectly fine
# This is how I upload my new Sol Trader builds (http://soltrader.net)
# Based on a modified script from here: http://tmont.com/blargh/2014/1/uploading-to-s3-in-bash

S3KEY="my aws key"
S3SECRET="my aws secret" # pass these in

function putS3
{
  path=$1

thorwebdev

SELECT
  pickup_polyId,
  SUM(fare_amount)/COUNT(*) AS average_fare,
  COUNT(*) AS no_of_trips
FROM
  [nyctaximap:dataflow.nyc_output_join_fare_distinct]
WHERE
  fare_amount!=0
GROUP BY
  pickup_polyId

tylr

var elasticsearch = require('elasticsearch');
var client = new elasticsearch.Client();
var eventPattern = /([^ ]*) ([^ ]*) ([^ ]*) ([^ ]*) ([^ ]*) ([^ ]*) ([^ ]*) \"(.*?)\" \"(.*?)\" \"(.*?)\" \"(.*?)\" \"(.*?)\"/;

exports.handler = function(data, context) {
  var events = [];
  var encodedEvent, rawEvent, 
      matchedEvent, event, i,
      commands;  

genadyo

{
    "491289025" : "ijinshan-kappmarket://",
    "301521403" : "fb103361823069955://",
    "492178411" : "ils492178411://",
    "346142396" : "fb234434003713://",
    "310633997" : "whatsapp://",
    "370614765" : "com.condenet.newyorker://",
    "325058491" : "rnmddisco://",
    "382952264" : "epichttp://",
    "477048487" : "predictwind://",

ThisIsMissEm

var child_process = require('child_process');

exports.handler = function(event, context) {
  var proc = spawn('./test', [ JSON.stringify(event) ], { stdio: 'inherit' });

  proc.on('close', function(code){
    if(code !== 0) {
      return context.done(new Error("Process exited with non-zero status code"));
    }

jaceklaskowski

Rough Notes about CQRS and ES

Once upon a time…

I once took notes (almost sentence by sentence with not much editing) about the architectural design concepts - Command and Query Responsibility Segregation (CQRS) and Event Sourcing (ES) - from a presentation of Greg Young and published it as a gist (with the times when a given sentence was heard).

I then found other summaries of the talk and the gist has since been growing up. See the revisions to know the changes and where they came from (aka the sources).

It seems inevitable to throw Domain Driven Design (DDD) in to the mix.

kachayev

Channels Are Not Enough

... or Why Pipelining Is Not That Easy

Golang Concurrency Patterns for brave and smart.

By @kachayev

Intro

kostaz

Assuming the username of the Ubuntu user is "theusername".

Preparation
-----------

```
sudo apt-get update
sudo apt-get upgrade

sudo apt-get install build-essential libtool autotools-dev autoconf pkg-config libssl-dev

gavinandresen

Now that we are finally starting to see the use of multi-signature and other more complicated transaction forms in applications I think it is time to open up the "IsStandard" transaction rules on the main Bitcoin network.

There are two main risks to doing this:

1. The risk that one of the seldom-used opcodes has a not-yet-discovered chain-forking bug. I believe that risk to be very low; we have never seen such a bug on the test network (where all transaction forms are allowed) and have never found a bug after writing extensive unit tests.
2. The risk of opening up a denial-of-service attack (either bloat the blockchain or use an excessive amount of CPU time) via a very expensive-to-store-or-verify transaction. This proposal does not entirely eliminate IsStandard checks to mitigate the potential for DoS attacks.

Proposal

Allow any Script containing 15 or fewer signature operations as a pay-to-script-hash (P2SH) Script to be relayed and mined by the reference implementation.