To see posts by date, check out the archives

What I Told the FCC
Tyler Cipriani Posted

I think that new FCC proposal for “Restoring Internet Freedom” would completely destroy the internet. Should this proposal go any further, the internet will no longer be recognizable within a very short amount of time. I’m worried that I will no longer have a place on the internet because my internet activity and work isn’t designed to invade people’s homes and privacy to sell them things they don’t need. Non-profits on the internet are dead.

This proposal is entirely rent-seeking by big ISPs. ISPs will make more money without providing any additional service for users, and the FCC would be enabling it all.

Big Disclaimer

This is a post where I feel it is important to make absolutely clear that my views are my own and do not represent the views of my employer(s past or present)

My comments to the FCC

The FCC has opened their proposal to public comment and I encourage you to do so.

Here’s what I wrote:

I am a Colorado resident and I’ve worked as an internet engineer for my entire professional career (small disclaimer that my views are my own and do not represent those of my employer), and I’m worried that new FCC rules may allow large ISPs to destroy the internet.

The current state of the internet is possible because ISPs aren’t selling tiers of websites to their users. If we create internet fast-lanes, then we create a tiered internet. This is currently the way cable channels already work: if you just want CNN and ESPN you can pay one amount, but if you want HBO you pay a little more. The problem is that the internet is constantly in flux, there are constantly new websites being built. This is a major driver of economic growth and is good for everyone who uses the internet.

If you start offering internet fast-lanes, internet tiers become possible: if you just want Facebook and Google then you pay one amount, but if you want Wikipedia you pay a little more. Ipso facto, Wikipedia is unavailable to a portion of the internet population.

There may be those who make the argument that this is how the free market works: if Wikipedia were good, people would be willing to pay more for it; however, this artificial choice between Google and Wikipedia is only made possible by a perversion of the design of the internet. Bits of information are bits of information, an ISP is arguing that websites should pay more while it offers the same service. ISPs want Netflix to pay more than Google for them to move 100 bytes from the internet backbone to your houuse. Moving 100 bytes from the backbone to someone’s house, the so-called “last mile”, is same amount of work whether those bytes are from Google or Netflix so why should Netflix have to pay more?

Meanwhile, large ISPs that move bits from the internet backbone over the “last mile” do not compete with one another by means of designed but unspoken collusion. The suggestion that an internet user should have to choose between Google and my blog is being made by companies that make all of their money by rent-seeking and now demand more money for less service. Consumers are not being protected, only ISP shareholders are.

This proposal has the net-effect of censoring the internet so that only websites that have enough money to pay protection fees to ISPs will be available to people. This proposal is censorship that stifles freedom and innovation and will destroy the internet.

/me drops mic.

Yearly Reading: Done and To Do
Tyler Cipriani Posted

Reading fiction is not that dissimilar from watching a movie in your brain. The ways in which audio-visual consumption of fiction and reading fiction diverge is in their demand on engagement – when reading I must learn new words, I struggle to find meaning, I use my imagination, I slowly strengthen understanding – I meet books more than half-way in my mind’s eye.

Movies and television, in contrast, demand less engagement from the viewer – much of the vision and interpretation is handed (or forced) on the audience. As popular movies and TV demand less, they also seem more apt to acquiesce to popular whim – mirroring the culture that consumes them rather than challenging it. The level of engagement demanded by audio-visual entertainment is also subject to a shifting baseline – that is, it’s gotten less challenging over time.

This is not a knock on all television and movies as a form of art. Often television, movies, and documentaries are the perfect medium to convey a particular message. Also, there are many movies and television programs which are, in fact, very challenging to their audience in addition to being very enjoyable.

Also, it is noteworthy that I tend to read mass-market crap – the book-equivalent of high-fructose corn syrup. I’ve come to terms with this fact. I read some crap, I read some good things, occasionally I’ll read a few great (and nominally “great”) things. I end up with a greater sense of accomplishment and satisfaction from reading crap rather than watching crap – YMMV.

This is a long way of saying – I think that reading is a Good Thing™ and I want to do more of it. To enforce more of a habit, I set reading goals for myself at the start of each year. In 2015 I wanted to read a book a month. In 2016 I wanted to read 2 books a month. In both 2015 and 2016 my grasp has exceeded my reach – which is not how goals are supposed to work.

Books read in 2016

  1. Stranger in a Strange Land by Robert A. Heinlein
  2. Black Hole by Charles Burns
  3. Fun Home by Alison Bechdel
  4. The Girl on the Train by Paula Hawkins
  5. Starship Troopers by Robert A. Heinlein
  6. Ready Player One by Ernest Cline
  7. The Circle by Dave Eggers
  8. Notorious RBG by Irin Carmon and Shana Knizhnik
  9. The Three-Body Problem by Cixin Liu
  10. A Wizard of Earthsea by Ursula K. Le Guin
  11. Stoner by John Williams
  12. Prost! The Story of German Beer by Horst D. Dornbusch
  13. Bock by Darryl Richman
  14. Do Androids Dream of Electric Sheep by Philip K. Dick
  15. Room by Emma Donoghue
  16. Kitchen Confidential: adventures in the culinary underbelly by Anthony Bourdain
  17. H is for Hawk by Helen Macdonald
  18. Watchers by Dean Koontz
  19. The Tombs of Atuan by Ursula K. Le Guin
  20. A Confederacy of Dunces by John Kennedy Toole
  21. Everything but Espresso by Scott Rao
  22. Harry Potter and the Sorcerer’s Stone by J.K. Rowling
  23. Harry Potter and the Chamber of Secrets by J.K. Rowling
  24. Harry Potter and the Prisoner of Azkaban by J.K. Rowling
  25. Naked Lunch by William S. Burroughs
  26. CODE: The Hidden Language of Computer Hardware and Software by Charles Petzold
  27. The Crying of Lot 49 by Thomas Pynchon
  28. The Best Christmas Pageant Ever by Barbara Robinson
  29. Harry Potter and the Goblet of Fire by J.K. Rowling

I also reviewed a couple of these books over the course of 2016, hopefully I can continue down that path in the year to come.

Goals for 2017

I’m going to try to read roughly a book a week in 2017 – 50 books for the year. Hopefully 50 books is an ambitious enough goal. Additionally, I’d like to try to do 6 book reviews on this blog as a means of:

  • Tracking what I’ve read
  • Checking my understanding
  • Engaging and owning what I’ve read

I’d also like to lay claim to my crazy ambitious plan to read 4 whole, real, grown-up (i.e., not beer- or computer-related) non-fiction books this year.

As I’m proclaiming these goals publicly for the first time, I’m sure I’ll come up woefully and shamefully short – yay blogging! :)

Book Review: CODE by Charles Petzold
Tyler Cipriani Posted

CODE: The Hidden Language of Computer Hardware and Software by Charles Petzold

The language of computer hardware and software is not particularly well hidden in my experience. The more I interact with software, the more those interactions reflect their makers and materials. This fact is slowly permeating the zeitgeist as we all, collectively, realize that facebook is not the open internet (no matter how much it may insist on its own benevolence), and that the current state of AI is simply one of money laundering for bias. While it is increasingly true that our high-level interactions with machines are broken, it’s important to recall that we haven’t fixed any of the low-level problems either (tried subtracting 399999999999998 from 399999999999999 in Google’s calculator lately?).

These incredible Rube Goldberg, hacks-all-the-way-down, leaking piles of abstractions that are modern computers are fascinating and powerful. The modern computer reveals its own history – each layer of abstraction representing a previous geologic era. The ancient .plan files of the Sumerians and Hittites.

CODE builds forward through time. Revealing each innovation necessary to create a fully functioning computer. It works its way towards the modern computer starting with binary data representation using morse code. From there it covers non-base-10 number systems, telegraphs, electromagnets and the invention of the relay, the flip-flop switch that allows temporary storage of a single bit. All of this background culminates in a truly wonderful chapter in which you use this technology to build a fully functional computer in your mind’s eye.

The book goes on to explain the Von Neumann architecture and from there moves into topics with which I am more familiar – high level programming languages, object-oriented programming languages, and “The Graphical Revolution”. In these later chapters, an evident object-oriented/graphical/IDE as the logical end-point for computing bias rears its ugly head, but in a book published by Microsoft Press it’s a surprisingly light touch.

CODE is one of the more interesting technical books I have ever read, and also one of the few that I read cover-to-cover over the course of a few reading sessions. It is a story rather than a series of ideas surrounding a theme. It is a history book, not a handbook.

My one critique is that the chapters after the climactic computer construction feel a bit disjointed. There is no real conclusion to the book – I expected a more satisfying wrap-up than I was given. Instead of a tying-up of loose-ends we move on to topics like object-oriented programming, and IEEE 754 floating-point numbers. While the treatment this book provides these topics is interesting, the organization is somewhat lacking.

To spite the lack of organization towards the end of the book, I found CODE a wonderful read and would have no qualms recommending it to anyone at any level of computer literacy.

Rating: 9/10

Meta Note:

As part of my effort to delve more deeply into reading, I will be featuring more review-type content. I will be tagging it all with the “books” tag. If you hate this, you can subscribe to the RSS feed for “computing” to continue to read my insights on something I’m perhaps even the slightest bit qualified to talk about in any sort of informed way.

Coreboot on the ThinkPad X220 with a Raspberry Pi
Tyler Cipriani Posted

My work laptop is terrible. About a year and a half ago, when I started my current gig, I received an Asus Zenbook that has been the bane of my existence ever since. First, it is impossible to work outside on this shiny monstrosity: all you see is your own dumb face squinting back at you, slightly obscured by very noticeable fingerprints from its mirror-like screen. Why are there fingerprints on the screen? Because, oh yeah, it’s a terrible touchscreen for no real reason. While the keyboard is serviceable, it is far from being a joy to use. There are no physical mouse buttons which, on a Linux install, means I’m forever flailing, trying to get middle-click paste to work (LPT: I setup an xdotool shortcut to paste – doesn’t work in Emacs though…). The Asus has also succumb to the Apple-esque use of dongles to replace all necessary ports (like Ethernet, FFS).

The final straw for this ridiculous machine was, for a reason that is beyond me, UEFI occasionally loses track of the boot drives and (although you can still see(!) the .efi file on disk via the UEFI interface) it won’t let you add it as a boot drive until you’ve sweated enough and/or there is a sufficiently powerful cosmic ray to flip the bits necessary to allow you to continue your life. This problem pretty much killed my productivity at my last offsite – as a result I decided to drop $500 and get a refurb ThinkPad X220 with more RAM and a bigger SSD than the ($1800) Zenbook.

X-Series ThinkPads are niiiiice

I have been using a ThinkPad X230t for the past 3 years, and, although the tablet is a little bulky, it has been everything I need in a work laptop – matte screen, physical buttons for all the things, an Ethernet port – it’s basically not an unbelievably stupid laptop design (which is the bar now, evidently). The X220 I purchased for work is even better – it’s slightly smaller (since it’s not also a Wacom tablet), plus the X220 has a nice keyboard – which – holy shit! – remember when anyone actually cared about laptop keyboards‽

I am become hacker, destroyer of laptops

One of the other reasons for buying the X220 is that I’ve heard-tell (A.K.A, did a quick DDG search) that it supports Coreboot (although, sadly, not Libreboot, yet). The actual incantations for flashing the ROM on the X220 are spread over a few sources, with some sizable gaps in process.

I spent the past 2 days pretty lost, flailing in the dark, booting my freshly flashed laptop to a momentary flicker of the green power-light, no fans, nothing, sighing, and compiling again. Now I stand victorious, Debian stable (8.6 as of November 2016) is booting from SeaBIOS.

I kept a lot of notes on the process. Hopefully, these notes save someone some frustration, or make this process a tiny bit more approachable.

Caveat Emptor – I’m terrible at hardware stuff and writing, so follow these steps at your own peril!

Things you need

What the whole flashing setup looked like for me X230 -> USB-to-TTY -> Raspberry Pi -> Pomona Clip -> X220
What the whole flashing setup looked like for me X230 -> USB-to-TTY -> Raspberry Pi -> Pomona Clip -> X220

ThinkPad X220 Disassembly

  1. Remove Keyboard and palmrest (follow Lonovo’s Guide)
    • Power down and remove battery
    • I removed the keyboard and palm rest in 2 separate steps.
    • Flip over and remove the 7 screws holding the keyboard and palmrest in place (they all have a picture of a square with 3 buttons [trackpad, I guess] near them).
    • WARNING – 2 of these screws are different sizes than the other 5! The ones closest to the front-edge of the laptop are shorter, keep them seperate.
    • Locations Diagram:
        Bottom of the ThinkPad -- 'X' marks screws to be removed
       |   xxxxxxxxxxxx Battery xxxxxxxxxxxxxxxxxxxxxxxxx          |
       |   xxxxxxxxxxxxx Area xxxxxxxxxxxxxxxxxxxxxxxxxxx          |
       |                                                           |
       |                                                           |
       |                                                           |
       |              +----X----------------+                      |
       |              |                     |                      |
       |              |      Memory         |                      |
       |              |       Door          |                      |
       |   X          |        X            |             X        |
       |      X       +---------------------+                      |
       |                  X               X                        |
    • Flip it over, push the keyboard back, pull up the tabs near the palmrest.
    • Rest the removed keyboard on the palmrest and remove ribbon cable from the motherboard.
    • Flip palmrest up, and click the ribbon cable holding it in place, remove it.
    • Lift tape on the left side of motherboard covering the chip you’re looking for.
    • The BIOS chip you are looking for is right there – the left-front of the motherboard if the screen is facing you.
Pomona 5250 attached to BIOS clip on ThinkPad X220
Pomona 5250 attached to BIOS clip on ThinkPad X220

Setup Your Pi as a Flasher

Now that you have access to the BIOS chip, you should setup your Raspberry Pi, and attach it to the Pomona 5250 clip via the SPI pins. Unfortunately, you do seem to need a monitor with HDMI to setup the Pi (someone better at Raspberry Pi things may know better).

After the initial setup I was able to switch to using a serial cable interface.

GIANT HUGE WARNING OF DOOM: Hook your Pomona clip to your motherboard ONLY WITH THE BATTERY REMOVED, THE X220 UNPLUGGED, AAAANNDDD THE RASPBERRY PI OFF!!!! You could probably fry this chip. I don’t actually know, but I was paranoid about it throughout the process. Power on the Raspberry Pi only when you’re certain the Pomona clip is secure.

  1. Download the Raspbian Lite torrent
  2. Unzip the rasbian zip file and copy to an sd card

    dd bs=4M if=rasbian-lite.img of=/dev/<partition of sd card>
  3. Hook up your Raspberry Pi to a monitor and boot

  4. Change password using passwd (default user/pass: pi/raspberry)

  5. Setup wifi by editing /etc/wpa_supplicant/wpa_supplicant.conf

  6. Edit /boot/config.txt

  7. Now you can reboot and hook to a serial cable:

    Serial cable hookup diagram:

       Edge of pi (furthest from you)
     L    PWR       GND  TXD  RXD
     E      |         |    |    |
     F +----v---------v----v----v-------------------------------------------------------------------------------+
     T |    x    x    x    x    x    x    x    x    x    x    x    x    x    x    x    x    x    x    x    x    |
       |    x    x    x    x    x    x    x    x    x    x    x    x    x    x    x    x    x    x    x    x    |
     E +--------------------------------------------------------------------------------------------------------+
       Body of Pi (closest to you)
  8. Install all the pre-req software working mostly from github wiki page Hardware Flashing with Raspberry Pi

    sudo apt-get update && sudo apt-get dist-upgrade && sudo reboot
    sudo apt-get update && sudo apt-get install libftdi1 libftdi-dev libusb-dev libpci-dev subversion
    sudo apt-get install build-essential pciutils usbutils libpci-dev libusb-dev libftdi1 libftdi-dev zlib1g-dev subversion
    svn co svn:// flashrom
    cd flashrom
    sudo make install

    Add the SPI kernal modules to /etc/modules so they persist between boots.

    sudo modprobe spi_bcm2835
    sudo modprobe spidev
  9. Power down the Pi, Hook your Pi to your Pomona clip, then hook the Pomona clip to the motherboard, and power back up.

    Raspberry Pi 3 attached to ThinkPad X220 Pomona Clip
    Raspberry Pi 3 attached to ThinkPad X220 Pomona Clip

    X220 BIOS Chip pinout

     Screen (furthest from you)
      MOSI  5 --|  |-- 4  GND
       CLK  6 --|  |-- 3  N/C
       N/C  7 --|  |-- 2  MISO
       VCC  8 --|__|-- 1  CS
       Edge (closest to you)

    PI Pinout

    WARNING!!! This is the pinout for the RASPBERRY PI 3 MODEL B V1.2 it has 40 pins rather than 26

       Edge of pi (furthest from you)
     L                                                             CS
     E                                                             |
     F +--------------------------------------------------------------------------------------------------------+
     T |    x    x    x    x    x    x    x    x    x    x    x    x    x    x    x    x    x    x    x    x    |
       |    x    x    x    x    x    x    x    x    x    x    x    x    x    x    x    x    x    x    x    x    |
     E +--------------------------------------------^----^----^----^---------------------------------------^----+
     D                                              |    |    |    |                                       |
     G                                             3.3V  MOSI MISO |                                      GND
     E                                           (VCC)            CLK
       Body of Pi (closest to you)
  10. See if flashrom can detect your chipset (if you see No EEPROM/flash device found. double check your connections and the pins for your pi – I realized I had my pins setup as if I were on the 26-GPIO pin Raspberry Pi rather than the 40-GPIO pin model 3)

    pi@raspberrypi:~$ sudo flashrom -p linux_spi:dev=/dev/spidev0.0
    flashrom v0.9.9-r1954 on Linux 4.4.26-v7+ (armv7l)
    flashrom is free software, get the source code at
    Calibrating delay loop... OK.
    Found Winbond flash chip "W25Q64.V" (8192 kB, SPI) on linux_spi.
    No operations were specified.
  11. Read your flashchip and verify that the md5sums match. If the md5sums of your reads don’t match repeat steps 9 and 10 until they do. If they never do, check your wiring with a multimeter (I had to do this at one point).

    pi@raspberrypi:~$ sudo flashrom -p linux_spi:dev=/dev/spidev0.0 -r flash01.bin
    pi@raspberrypi:~$ sudo flashrom -p linux_spi:dev=/dev/spidev0.0 -r flash02.bin
    pi@raspberrypi:~$ md5sum flash01.bin flash02.bin
  12. Download coreboot on the Pi. Compile and use ifdtool to extract all the needed bits to all the right places in the coreboot blobs directory.

    git clone ~/coreboot
    cd ~/coreboot
    git submodule update --init --recursive
    cd ~/coreboot/util/ifdtool
    sudo make install
    cd ~
    ifdtool -x ~/flash01.bin
    mkdir -p ~/coreboot/3rdparty/blobs/mainboard/lenovo/x220
    cd ~/coreboot/3rdparty/blobs/mainboard/lenovo/x220
    mv ~/flashregion_0_flashdescriptor.bin descriptor.bin
    mv ~/flashregion_2_intel_me.bin me.bin
    mv ~/flashregion_3_gbe.bin gbe.bin
  13. Build coreboot on the Pi following the wiki instructions

    • configure via (note – this is completely cargo-culted bullshit and YMMV…a lot) make nconfig
        - [*] Compress ramstage with LZMA
        - [*] Include coreboot .config file into the ROM image
        - [*] Allow use of binary-only repository
        -  Mainboard vendor (Lenovo)
        -  Mainboard model (ThinkPad X220)
        -  ROM chip size (8192 KB (8 MB))
        -  (0x100000) Size of CBFS filesystem in ROM
        - [*] Enable VMX for virtualization
        -  Include CPU microcode in CBFS (Generate from tree)
        -  Flash ROM locking on S3 resume (Don't lock ROM sections on S3 resume)
        - [*] Add Intel descriptor.bin file
          (3rdparty/blobs/mainboard/$(MAINBOARDDIR)/descriptor.bin) Path and filename of the descriptor.bin file
        - [*] Add Intel ME/TXE firmware
          (3rdparty/blobs/mainboard/$(MAINBOARDDIR)/me.bin) Path to management engine firmware
        - [*] Add gigabit ethernet firmware
          (3rdparty/blobs/mainboard/$(MAINBOARDDIR)/gbe.bin) Path to gigabit ethernet firmware
        - [*] Use native graphics initialization
        - (nothing checked)
    generic drivers
        - [*] Support Intel PCI-e WiFi adapters
        - [*] PS/2 keyboard init
        - [*] Squelch AP CPUs from early console.
          [*] Show POST codes on the debug console
    system tables
        - [*] Generate SMBIOS tables
        - Add a payload (SeaBIOS)
        - SeaBIOS version (master)
        - (3000) PS/2 keyboard controller initialization timeout (milliseconds)
        - [*] Harware init during option ROM execution
        - [*] Include generated option rom that implements legacy VGA BIOS compatibility
        - [*] Use LZMA compression for payloads
        - (nothing checked)
    • Compile coreboot!
    make crossgcc-i386 CPUS=4
    make iasl

    EDIT – 2016-11-27 Andreas Sinninger pointed out I was missing the path to the Intel ME/TXE firmware – corrected.

  14. FINALLY! Flash your new coreboot.rom to your rom chip:

    pi@raspberrypi:~$ sudo flashrom -p linux_spi:dev=/dev/spidev0.0 -r flash01.bin
    pi@raspberrypi:~$ sudo flashrom -p linux_spi:dev=/dev/spidev0.0 -r flash02.bin
    pi@raspberrypi:~$ md5sum flash01.bin flash02.bin  # if these don't match, stop, turn off the pi, fiddle with the Pomona clip, repeat this step
    pi@raspberrypi:~$ sudo flashrom -p linux_spi:dev=/dev/spidev0.0 -w ~/coreboot/build/coreboot.rom

If your laptop boots up to a SeaBIOS screen at this point: you win! If not, don’t despair, you can flash flash01.bin to go back to your old BIOS, or, better yet, keep compiling until it works.


These are some general resources without which my X220 would be a pathetic pile of smashed up silicon by now.

My Remote Desk
Tyler Cipriani Posted

Remote Culture

A rant

It doesn’t make sense to mandate that I sit in the same building as you to work on things somewhat related to the things you work on. By recognizing this fact, both employers and employees now have a great deal of freedom (for some value of the word “freedom”). Employers can hire people from across the globe, and employees can live anywhere on said globe.

When I tell people I work from home I rarely get any sympathy, but the fact is that working remotely is harder than working in an office for millions of little reasons. The in-office workplace is the default – if you’ve ever had a job chances are you went to a building some place to do that job with other folks that did a slightly different job who were (at least nominally) working towards the same goals as you. And oooh the things you took for granted in your cushy IRL job!

That meeting that was loosely scheduled for 4pm? I’ve got some time now, what if we just scrap project Foo? Work for you? Cool. {{done}}. No one updated their calendars. No one likely bothered to update the documentation for the project Foo. I can just walk down the hall and talk to Jan faster than I can update the office wiki which is always hopelessly out-of-date anyway. Nobody checks the mailing list, everyone knows if there are project Foo questions, they can just ask me. Problem. Solved.

Remote companies cannot be this lazy.

It’s not just that remote work is lonely (it is). It’s not just that it’s hard to find a good place to work when you’re remote (it is hard). It’s a million little things – documenting the little decisions so that when someone on the other side of the world wakes up, they don’t have questions (because you won’t be around to answer them), keeping the office wiki up-to-date, making sure to post big changes to the mailing list.

Being “remote friendly” is not a thing, having a remote culture is. Remote culture is something that everyone has to cultivate constantly.

Remote Desks

The Wikimedia Foundation strives for a remote culture. There are constant and seemingly innumerable challenges – both big and small, both technical and cultural.

A couple of months ago there was an email thread on the staff mailing list that attempted to assail one of the remaining bastions of privilege exclusive to the physical, IRL office-worker: seeing people’s desks!

Walking around a physical office you see people’s personalities laid out in physical space. You may discover that you have similar interests or hobbies, you may learn about a new topic, or you may discover the very key to existence simply by craning your neck slightly to take a good, long, hard look at another person’s pile of accumulated doo-dads and brick-a-brack.

Filled with this understanding, we shared our desks, and the things on them.

My Desk

This is what my desk looked like in September of 2016.

My Desk
My Desk

Some of the the things on my desk, and some of the reasons for some of the things on it (in no order):

  1. Data Science at the Command Line
  2. The Anarchist’s Design Book
  3. Phantom II Drone (with a GoPro Hero 3+)
  4. Manfrotto MTPIXI-B PIXI Mini Tripod
  5. Joby GorillaPod SLR-Zoom Tripod
  6. Some rusty pliers
  7. A 12’ Tape measure
  8. Google Fi powered Nexus 5x - I dislike this phone
  9. 2x Laptop Camera Covers
  10. USB Barcode Reader for my Library Project.
  11. SouthOrd MPXS-14 Lock Pick Set and a few MasterLocks for practice
  12. GoF Book
  13. Brother HL-L2340DW Compact Laser Printer $99 – best printer ever.
  14. 3M LX550 Notebook riser – no need for a monitor, works great.
  15. Vortex Poker II (with Cherry MX-Blues)
  16. A barcode that says “HI” to test out the barcode scanner
  17. Evoluent VerticalMouse
  18. Fair casino dice to generate diceware passphrases
  19. A desktop background from NASA (there’s a thing in my dotfiles to download a new one daily)
  20. SparkFun Cerberus USB Cable
  21. Vintage Kodak ad of a kid with a squirrel to liven-up the joint
  22. Renewal form for the American Homebrewer’s Association which is a problematic organization for many reasons