Jean-Paul Calderone

An intermediate step here might be to not *blow up* when encountering these other rrset types. Since they have different elements, they currently break `list_resource_record_sets` merely by existing. :/

Nope. I was looking for something that is more of an end-user experience rather than pieces for building my own (esp. since it sounds like perhaps the pieces are there...

Current behavior: ``` $ nixops destroy --deployment $NAME warning: are you sure you want to destroy EC2 machine ‘infra’? (y/N) n warning: are you sure you want to destroy EC2...

I wanted to ingest slipcover measurements into coverage reporting services so I wrote a converter from slipcover output to coveralls.io format - https://github.com/PrivateStorageio/ZKAPAuthorizer/blob/8a447d2584b37eecef6fef97374293f16534c952/slipcover2coveralls.py I think I might rather work with...

We now at least get tracebacks thanks to monkey-patching in a fix for http://twistedmatrix.com/trac/ticket/8860 I haven't observed the problem since deploying this... but I also haven't been reading all the...

Two reads through of the code that I _think_ is relevant here didn't yield any enlightenment for me. A mitigation strategy could be to teach Kubernetes to notice that at...

We should take a closer look at the OS X installation experience for Tahoe-LAFS and determine if there's anything we can do to make it better. This requires access to...

If the solution involves any kind of waiting on the part of the user with a non-obvious completion point, some kind of progress indicator would be nice. Chris suggested this...

It turns out they last forever (or until the originating end gives up - which ours does whenever we deploy a code update) by default.

One way to do this would be in the by customizing the "nickname" sent in the config blog via magic-wormhole. It currently says "Least Authority S4" but we could make...