Gittr.rb
Git as a key-value store! Build with Grit, it supports SET, GET, KEYS, and DELETE operations. In addition, we can also get the change history of key/values.
And since it's Git, we can easily enhance it to include other awesome Git features such as branches, diffs, reverting, and more!
Example:
Copy this file to: /Library/LaunchDaemons/fwd-80-to-3000.plist and then reboot:
$ sudo -s
$ curl -L https://gist.github.com/TooTallNate/3372589/raw/ace6451e9e47f59550f12d09cb924a64531cfd1f/fwd-80-to-3000.plist > /Library/LaunchDaemons/fwd-80-to-3000.plist
$ rebootWork in progress, I'll write this up properly when I'm done.
Almost all credit goes to @maxogden for putting me on to this and pointing me in the right direction for each of these items.
Prerequisites:
| ### MARKHAM'S NOTES: | |
| # This Makefile includes the Arduino core sources. (Set ARDDIR here:) | |
| ARDDIR = /d/arduino | |
| # You should build a tiny Makefile for each of your projects and just declare a few | |
| # things in it, then include this Makefile in it. Your Makefile should be in the same | |
| # directory as your TARGET file (see below). | |
| # | |
| # Exemplia gratia: |
Each of these commands will run an ad hoc http static server in your current (or specified) directory, available at http://localhost:8000. Use this power wisely.
$ python -m SimpleHTTPServer 8000
| import os | |
| import numpy | |
| from pandas import DataFrame | |
| from sklearn.feature_extraction.text import CountVectorizer | |
| from sklearn.naive_bayes import MultinomialNB | |
| from sklearn.pipeline import Pipeline | |
| from sklearn.cross_validation import KFold | |
| from sklearn.metrics import confusion_matrix, f1_score | |
| NEWLINE = '\n' |
Tahoe LAFS is a distributed file system with an interesting permissions model. (whitepaper)
Both Immutable and Mutable files are supported (Mutable is the most complex and interesting)
There are three levels of permissions, Write, Read, and Verify. Each permission is
granted by giving a user a special key called a "capability". If you have the Write capability
you can update the file, if you have the Read capability you can retrieve the plain text,
but if you only have the Verify capability you can only validate the file integrity, but not read the contents.
The lower level capabilities are generated deterministically from the higher level capabilites.
| # using such a setup requires `apt-get install lua-nginx-redis` under Ubuntu Trusty | |
| # more info @ http://wiki.nginx.org/HttpLuaModule#access_by_lua | |
| http { | |
| lua_package_path "/etc/nginx/include.d/?.lua;;"; | |
| lua_socket_pool_size 100; | |
| lua_socket_connect_timeout 10ms; | |
| lua_socket_read_timeout 10ms; | |
| server { |
(dominic: this list of papers was originally recommended to me by Brain Noguchi @bnoguchi, and was a great start to understanding distributed systems)
Here's a selection of papers that I think you would find helpful and interesting:
The seminal paper about event ordering and concurrency. The important result is that events in a distributed system define a partially ordered set. The connection to what we're working on is fundamental, as this defines how to detect concurrent updates. Moreover, the chosen algorithm to turn the partially ordered set into a totally ordered set defines the conflict resolution algorithm.
http://research.microsoft.com/en-us/um/people/lamport/pubs/time-clocks.pdf
Robert Axelrod; William D. Hamilton http://citeseer.ist.psu.edu/viewdoc/download?doi=10.1.1.147.9644&rep=rep1&type=pdf
Great paper on Iterated Prisoners Delimma. Many citations of biological research. Shows that Tit4Tat is dominant strategy and gives parameters in which t4t players become dominant agaisnt allD.