Patrick Connolly patcon

Problem

Reduplication of work is very common in both the civic tech and open source space.

For lots of reasons (expand).

To address this, in the community it is often proposed to have a list of resources or existing projects. While an obvious solution, it has several fundamental challenges, such as:

It is hard for one or a small group of people to know everything that is going on
Someone has to maintain this resource or else relevance slowly declines and leads to stagnation

We prefer to have audit logging in our services that leverage databases. It gives us clarity into sources of where ACL issues might originate as well as gives us a general timeline of activity in our application.

Audit logging is tedious to set up so this gist contains our latest iteration of audit logging support for a sequelize based service.

{% include timelinejs.html json-source="" %}

"Scar Tissues Make Relationships Wear Out"

04/26/2103. From a lecture by Professor John Ousterhout at Stanford, class CS142.

This is my most touchy-feely thought for the weekend. Here’s the basic idea: It’s really hard to build relationships that last for a long time. If you haven’t discovered this, you will discover this sooner or later. And it's hard both for personal relationships and for business relationships. And to me, it's pretty amazing that two people can stay married for 25 years without killing each other.

[Laughter]

> But honestly, most professional relationships don't last anywhere near that long. The best bands always seem to break up after 2 or 3 years. And business partnerships fall apart, and there's all these problems in these relationships that just don't last. So, why is that? Well, in my view, it’s relationships don't fail because there some single catastrophic event to destroy them, although often there is a single catastrophic event around the the end of the relation

Tinder API documentation

Note: this was written in April/May 2014 and the API may has definitely changed since. I have nothing to do with Tinder, nor its API, and I do not offer any support for anything you may build on top of this. Proceed with caution

http://rsty.org/

I've sniffed most of the Tinder API to see how it works. You can use this to create bots (etc) very trivially. Some example python bot code is here -> https://gist.github.com/rtt/5a2e0cfa638c938cca59 (horribly quick and dirty, you've been warned!)

	worker_processes 1;

	events {
	worker_connections 1024;
	}

	rtmp {
	server {
	listen 1935;
	chunk_size 8192;

	contract BinarySearch {
	///@why3
	/// requires { arg_data.length < UInt256.max_uint256 }
	/// requires { 0 <= to_int arg_begin <= to_int arg_end <= arg_data.length }
	/// requires { forall i j: int. 0 <= i <= j < arg_data.length -> to_int arg_data[i] <= to_int arg_data[j] }
	/// variant { to_int arg_end - to_int arg_begin }
	/// ensures {
	/// to_int result < UInt256.max_uint256 -> (to_int arg_begin <= to_int result < to_int arg_end && to_int arg_data[to_int result] = to_int arg_value)
	/// }
	/// ensures {


	import "owned";

	contract RevokableOwned is owned {
	address previousOwner;
	uint8 revokableV;
	bytes32 revokableR;
	bytes32 revokableS;

	// In order to make a contracts ownership revokeable you must