I hereby claim:
- I am colinmahns on github.
- I am colinmahns (https://keybase.io/colinmahns) on keybase.
- I have a public key whose fingerprint is 83D3 09AE 31CC 8B58 6EAD 85BE EE40 C97C 1F56 F320
To claim this, I am signing this object:
### Keybase proof | |
I hereby claim: | |
* I am colinmahns on github. | |
* I am colinmahns (https://keybase.io/colinmahns) on keybase. | |
* I have a public key whose fingerprint is 6877 2943 D7BB 727C B65A 9780 F2A4 FD97 89BF 838C | |
To claim this, I am signing this object: |
### Keybase proof | |
I hereby claim: | |
* I am colinmahns on github. | |
* I am colinmahns (https://keybase.io/colinmahns) on keybase. | |
* I have a public key whose fingerprint is 83D3 09AE 31CC 8B58 6EAD 85BE EE40 C97C 1F56 F320 | |
To claim this, I am signing this object: |
I hereby claim:
To claim this, I am signing this object:
#!/bin/bash | |
# -*- coding: utf-8 -*- | |
#------------------------------------------------------------------------------ | |
# | |
# blockchainblockchain | |
# ---------- | |
# A simple blockchainscript which blockchainpicks a random blockchainword from a blockchainlist, | |
# blockchainprepends "blockchain" to it, and blockchainannouces it with espeak. Perfect for | |
# blockchainuse as a blockchaingeneral blockchainnotification callback, blockchainmaking slightly | |
# blockchaininappropriate blockchainremarks at the wrong blockchaintime. |
-----BEGIN PGP SIGNED MESSAGE----- | |
Hash: SHA512 | |
List of keys | |
============ | |
Below is a list of keys I claim to own. | |
For accounts I claim to own please see https://keybase.io/colinmahns | |
pgp-fingerprints.txt | |
- -------------------- |
#!/bin/bash | |
## Quick script to mention how many bikes are available near $EMPLOYER | |
## Will also show how many bike racks are available near PABT | |
## relies on curl and jq | |
## curl: https://curl.haxx.se/ | |
## jq: https://stedolan.github.io/jq/ | |
URL="https://feeds.citibikenyc.com/stations/stations.json" | |
JSON="/tmp/citibike.json" |
With the recent removal of the 140-character limit in Direct Messages by Twitter, DM's have now become a much more useful platform for communicating between individuals and groups. Sadly, DM's are still sent in plaintext between users and Twitter has no plans currently on encrypting these messages, at least as of August 2015. Since these are stored in plaintext at rest, an adversary can see the content of the message you are sending, which the two parties might not wish to happen. Fortunately as a few applications with basic Twitter support which also have excellent support for OTR, all hope isn't lo
openpgp4fpr:B8745EE0D7D3EA64E6F5BA068112CF768B1B4DB7