Sun, 12 May 2013
Crockpots and kitchen improvements
Preeya and I cooked together at my place yesterday, and after the event, I wrote down some notes so that next time it can be even better.
The idea of the cooking was to create leftovers for us both to eat during the work-week. Preeya's angle is that she loses interest in eating something during cooking it, so we thought we could make food for each other.
We cooked:
- Crockpot Recipe for Vegetarian Black Bean and Tomatillo Soup with Lime and Cilantro (for Asheesh, by Preeya)
- Slow Cooker Coconut & Green Curry Pork (for Preeya, by Asheesh)
Notes
Here are the notes I wrote up from the event. Mostly I'm sharing these to provide some insight into the process of "Do something in the kitchen, then think about how to improve the kitchen" that I've been going through a lot lately.
Dry things we could have had but didn't
- Brown rice
- Black beans
(Fix: bought them by Google Shopping Express)
- Canned diced tomatoes... (reading http://www.cooksillustrated.com/tastetests/overview.asp?docid=25627 suggests Hunt's is good; fix is to stock a few cans. I should get that from a local store since Google Shopping Express doesn't have Hunt's. Muir Glen Organic is also good, says this. Personal note: Jersey Fresh brand is super great, but hard to get.)
Locations of things in kitchen
- Scissors were easy to use once Asheesh said where they were.
- Counter space was not cleared-off before we began.
- Oven gloves were in a weird spot. (Fix: I moved two magnetic hooks
- We didn't have a garlic press, which would have been nice. (Fix: I did some research and bought http://www.amazon.com/Zyliss-Susi-3-Garlic-Press/dp/B007D3V00Q/ . Note that this press does not need one to peel the clove, which is good news.)
- Now that the 5lb gag of basmati is open, I'm afraid it'll get infested with moths. (Fix: Buy a 1 gallon Mason jar and see if I can fit all the rice into that.)
- Some spices aren't in the "spice rack" (but there's a fix already in the works for that, awaiting delivery of more spice jars).
- Preeya didn't know where chopping boards were, though they were easy to get once found.
- We tried two different locations for Preeya's slow cooker, settling on to the right of the sink / underneath the window there.
Shopping
- The pork butt was very reasonably priced, but it meant round-tripping to Mission Street for Preeya's favorite meat market. Asheesh could have tried La Gallinita next time.
- Buying the rest of things was easy. Casa Lucas had everything, I think.
General
- Things in the slow cooker take ages to cool down.
- We don't have any tupperware large enough to fit a full 4 quart slow cooker cooking result.
- The programmable-ness is super nice in Preeya's slow cooker.
- Using our can opener on the Maesri curry paste just sucks.
- Preeya had to go back to her place to get her slow cooker, which we could have thought of.
- Preeya mentioned the Mezzaluna style of cutting board, which has a dome to rock a knife within, for dicing. (Other names for similar things: ulus, uluut.) Such a thing might be worth getting.
Recipe
- The rice in the recipe for Asheesh became mush. Should probably have stuck to brown rice.
- Asheesh thought he'd add spinach to Preeya's recipe but hasn't yet.
Logistics
- It was nice cooking together. The scheduling was somewhat messy. We could have pre-picked our recipes. Preeya didn't bring a computer so only Asheesh really looked.
[food] permanent link and comments
Mon, 06 May 2013
asheesh.org/scratch/ back in business
For a few years, I had been storing public notes to myself (that might possibly be useful to others) at http://asheesh.org/scratch/.
Then OpenHatch happened in May 2009, and I paid decreasing attention to that site.
Eventually, as a semi-unprotected MediaWiki instance, it became spammed to smithereens.
Last night and this morning, I did the following things:
Now you can more easily read my scratchy notes, like:
Honestly, it is a huge relief to see those old bits of text back on the web. It makes me feel so much more pleasantly connected to the timeline.
[sysop] permanent link and comments
Sat, 13 Apr 2013
Why are you doing all of this?
fijal just asked me, on IRC:
Briefly, here is the reason I work on OpenHatch:
For free software to take over the world, and for all users of software to be able to have control over their computing, we need a few things it seems to me.
I think that explains basically all of what we do at OpenHatch.
[free-culture] permanent link and comments
Thu, 07 Feb 2013
Notes from attempting to despam a wiki with git-remote-mediawiki
I just tried to despam a mediawiki instance with git-remote-mediawiki.
The idea is as follows:
(You can process that with either 'grep ^Author' and so on, or you can use an overwrought Python script I wrote.)
Here's where things start to go wrong.
You might try to revert them all:
That works great until the first merge conflict.
So then you write a wrapper script that does "git revert $1 || git revert --abort", and you can still only revert the first few hundred (out of ~800) spam edits because one of the commits causes a conflict when you try to revert it.
Why a conflict? I suspect it's because there are spam edits that I neglected to include in the revert stream. (Update: The conflict was actually a real conflict -- some kind soul on the web had already reverted a bunch of the spam edits!)
In our case, there are fairly few pages getting spammed, so it'd be simpler to 'git log' the pages we care about and revert back to the commit IDs that look clean. 'git revert' could still be useful in the case of tangled history, but (apparently) there is a limit to how useful it can be, anyway.
Oh, also:
It'd be useful to be able to create MediaWiki dump files from git-remote-mediawiki exports. That way, I could use 'git rebase -i' to clean up history. (That would break links *unless* the MediaWiki revision IDs somehow stayed constant for the revisions with the same content. Maybe that's feasible. Actually, the simplest way might be to write a tool that filters the dump file itself, rather than exporting straight from git-remote-mediawiki.)
Also also, I fixed a format string bug in git mergetool, one of my favorite little pieces of git.
P.S. In this corpus, of the IP address editors (i.e., not logged in), 0 (of 16) are spammers. About 80% of the logged-in editors are spammers. (Admittedly our wiki does require you to log in if you are posting new URLs to a page.)
Update: It is way faster if you run it with low latency to the MediaWiki server in question. It probably could be adjusted to make fewer API calls, and to make more of them in parallel.
[software] permanent link and comments
Sat, 02 Feb 2013
Receiving mail virtually
This is the most beautiful piece of mail I have ever received virtually:
Since a few months ago, I have been a very happy customer of Virtual Post Mail, a service where they'll receive mail on my behalf and, if I want them to, scan it. And if there is a check inside, they'll send it to my bank's "Deposit by mail" address so it gets into my bank account.
I've been using it for a number of OpenHatch inbound mail things, so that I don't have to go deposit checks at a bank branch if e.g. I'm traveling. But I've also been using it for a few personal things.
I suspect this is a wedding invitation. I've clicked the "Open and Scan" button in the website, and expect to find out shortly (in 1-24 hours).
[travel] permanent link and comments
Sat, 12 Jan 2013
A brief tribute
The news.
[people] permanent link and comments
Thu, 27 Sep 2012
Censored on Facebook
For the first time in what feels like years, I wanted to share something with my friends on Facebook.
The background was that I read a note on Slashdot that Linus Torvalds thought a presidential candidate's remarks on a topic related to airline security were "moron"ic. So I did my own research, and I disagred. I figured this was a topic of general enough interest that all my Facebook friends might be interested in knowing my position, so I wanted to share that.
Facebook didn't let me.
I tried first with a link to snopes.com, which blocked me with the rationale that http://snopes.com/images/template/snopes.gif is "spammy or unsafe":
Then I thought I'd be clever, and I linked to the .nyud.net version of the snopes page on the topic. I earned the same message that my post included a blocked link.
So then I tried again, with a link to a video on YouTube of the same clip.
That's when I first got the extremely generic message that "The message could not be posted to this Wall."
Finally, I removed all the links, and kept the first bit of text. For this, I got the same generic error: "The message could not be posted to this Wall."
Update: Patrick points out I should link to the actual video. Here it is, embedded:
(BTW: The first thing I did was to click "let us know" to indicate that I think I'm seeing this by mistake. I filled out the form to indicate there was a problem in an honest, respectful way. I got back an email autoresponse that said, "Thanks for taking the time to submit this report. While we don't currently provide individual support for this issue, this information will help us identify bugs on our site.")
[software] permanent link and comments
Mon, 13 Aug 2012
Zooming in
A mis-quote of "Can Hospital Chains Improve the Medical Industry?".
[debian] permanent link and comments
Mon, 30 Jul 2012
RHEL 7 will (probably) have GNOME 3
While chatting with Greg Price earlier this evening about the coming Linpocalypse, I said something I wanted to research. Upon further review, it seems that Red Hat Enterprise Linux 7 will ship GNOME 3.
You can see a video of Jonathan Blandford talking about it, where he says:
"CubedRoot" on fedoraforum.org did take a look, and (s)he wries:
[software] permanent link and comments
Thu, 14 Jun 2012
Reactions to a public disaster
Quoth Laila Winter:
[me] permanent link and comments