Jeff Kaufman  ::  Blog Posts  ::  RSS Feed  ::  Contact

Backup Strategy

After reading a post from someone who nearly lost all their data to a joint NAS and external hard drive failure I decided to think through my data durability.

Most of my stuff lives in the cloud: email on Gmail, docs in Google Docs, photos in Google Photos, data in Google Drive. I trust Google a lot for this sort of thing, both given their public reputation and as an employee. I think Google is extremely unlikely to lose or corrupt my data.

The next biggest place where I have things is on the server that runs I back this up to my laptop with a cronjob that looks like:

Nomic Report II

This second week has been a pretty slow one for the game. Pavel and I were both sick, some players have silently stopped participating, and the code is basically where it was a week ago. The biggest change is that we now have a dashboard:

This shows what PRs need review by which people. Figuring this out efficiently from GitHub's interface was one of the biggest things slowing the game down. GitHub isn't designed around the idea that all repo collaborators are interested in reviewing every PR.

Bathroom Construction Update

I've now started working on the new bathroom (plans), so here's where we are while things are still fresh.

Last look at the old bathroom:

I was planning to start demolition on Saturday 1/5, so earlier in the week the plumber came by to remove fixtures and cap pipes. I broke the vanity down, and here's the empty room:

Here's a map of what I was planning:


  • Blue lines: plastic to contain dust
  • Red lines: walls to gut
  • Red rectangle: door opening to cut
  • Pink region: floor to gut

I left the ceiling alone, except in the tub alcove where there was a lower ceiling (boxed-in dead space).

Nomic Report

After proposing automated nomic last week I coded something up and started a game. After playing for a week, here are some thoughts.

The general idea is, people submit and review PRs, and whether a PR can be merged is up to what (on master) says should be merged. You win by getting the build to fail with a message saying that you win. We started playing with a that just implemented the rule "allow merging if you have unanimous approval from all users listed in players.txt".

The first problem we ran into was merge conflicts. While the first two PRs where someone asked to join (#6, #7) went fine, things bogged down as we got more requests (#11, #12, #15, #20, #22). The problem was, all players would need to approve each new PR, but then once that one was merged all the other PRs would need to have merge conflicts manually resolved, and then they'd need to be approved again.

Splitting Things

I had a good conversation in person with Quill today about the splitting things portion of my outcomes of a safety report post. I had written:

I think organizers should have a pretty low threshold for splitting things. You don't need to determine whether the harm counts as abuse, be sure of what happened, or be sure how blame should fall. That someone feels strongly enough about avoiding someone that they're willing to give up half the dance time/space to do so tells you a lot.

Automated Nomic

Nomic is a game where you start with an initial rule set, and gameplay is all about modifying the rules. I've only played in person, with human rules interpreters, but I think an automated version built around GitHub pull requests and Continuous Integration could be interesting:
More Posts

Jeff Kaufman  ::  Blog Posts  ::  RSS Feed  ::  Contact