Jeff Rade jeffrade

Published as BIP 103

Most VPN Services are Terrible

Short version: I strongly do not recommend using any of these providers. You are, of course, free to use whatever you like. My TL;DR advice: Roll your own and use Algo or Streisand. For messaging & voice, use Signal. For increased anonymity, use Tor for desktop (though recognize that doing so may actually put you at greater risk), and Onion Browser for mobile.

This mini-rant came on the heels of an interesting twitter discussion: https://twitter.com/kennwhite/status/591074055018582016

(The below text is licensed with CC0, which means that if you want to use or translate it, that is OK by me.)

Ok, I geeked out, and this is probably more information than you need. But it completely answers the question. Sorry. ☺

Locally, I'm at this commit:

$ git show
commit d6cd1e2bd19e03a81132a23b2025920577f84e37
Author: jnthn <[email protected]>

Date: Sun Apr 15 16:35:03 2012 +0200

(a gist based on the old toolmantim article on setting up remote repos)

To collaborate in a distributed development process you’ll need to push code to remotely accessible repositories.

This is somewhat of a follow-up to the previous article setting up a new rails app with git.

For the impatient

Set up the new bare repo on the server:

	public class TwoMains {
	public static void main(String[] args) {
	System.out.println("main");
	mаin(args);
	}

	public static void mаin(String[] args) {
	System.out.println("other mаin");
	}
	}

	from TwitterAPI import TwitterAPI
	import json
	import logging
	import time
	from collections import OrderedDict
	from random import random

	"""
	Assume 3 participants. You will need to create a Twitter account for each participant, and get API keys for each one.
	"""

	// After you think you understand this program, try writing it yourself until
	// you can get it to work, the first time, without error ^_^
	//
	// ALSO: remember:
	// $ gcc program.c # compile
	// $ ./a.out # run

	// We'll get `printf` from standard input/output's header file
	#include <stdio.h>

	Beyond IP Transactions: towards a payment protocol
	==================================================

	IP transactions were originally introduced as a first "out-of-band" protocol
	for negotiating a transaction output's public key. Being inconvenient and
	insecure, they became obsolete, and recent versions of bitcoin don't support
	them anymore.

	The result is that static bitcoin addresses have become the most common way of
	defining requested payments. This may be fine for anonymous donations, but is not