One of our favourite dishes is fish & chips. One of the perks of living in Toronto for a summer was having a cheap fish & chips place just a couple blocks away. And here, there’s a great place (Mac’s Fish & Chips) a couple miles from our apartment.

But often we make our own fish & chips. The first, key thing is the batter. After some experimentation, here’s the recipe I use:

• 1C flour (usually white, occasionally add some whole wheat)
• 2t cornstarch (helps the consistency a lot, helps it stick to the fish)
• Seasoned salt (I just sprinkle some on; usually use Harley’s)
• 1 egg
• Milk (we use coconut or rice milk, but dairy milk works as well of course. I recommend 2% or whole; skim might be a little thin)

Mix together flour, cornstarch, and salt with a fork. Mix in the egg. Then add milk a bit (~1/4C at a time), mixing with the fork, until it’s a good consistency. You want it thick, thick enough it doesn’t drip all over the place, but not so thick you can’t spread it over the fish.

I’ve been bearish on Do Not Track. Providing user control over tracking is useful, but DNT has seemed to have exactly zero utility, being the Internet-tracking equivalent of the evil bit. Trackers have little incentive to use it, short of regulatory pressure or just trying to be good people, and the particularly bad actors who I might really want to keep my data away from are never going to respect it even with regulation. So turn on RequestPolicy and forget about it.

Then this crossed my radar. Twitter is personalizing the new-user experience based on tracking data collected via tweet buttons, so your new account automatically has suggestions of people to follow that might actually be relevant. This has huge implications for improving experience for new users; a lot of the benefit of Twitter depends on the streams you follow, and connecting users to relevant streams right off the bat seems like a great way to dramatically improve the quality of the initial experience and thereby improve user retention.

Thanks in part to Do Not Track, Twitter is also building this feature in the most responsible way I can imagine:

• If you have Do Not Track set in your browser, they don’t track your data.
• They purge data after 10 days, so they don’t hang on to it indefinitely and your new-user experience is only based on the last 10 days of web visits.
• They describe the feature, and the data they collect.

I had a need this week to join lines in a shell script. Specifically, I had a file containing file names, one per line and needed them colon-separated in a single line.

I could have done something in Perl or Awk, or something. But a bit of searching turned up this solution in sed:

sed -e :a -e '$!N; s/\n/:/; ta' test.txt

sed usually operates a line at a time, so a simple s/\n/:/g won’t work; it will never find the newline characters.

There is an emerging social norm on app.net, or at least among some of its vocal members, that cross-posting content from Twitter (e.g. w/ IFTTT) is unwelcome.

As I said in that thread, I think this norm is unhelpful for encouraging adoption and building a diverse community and information flow.

Authors/publishers, both in the large and in the small, write and post where there is engagement. If there is no engagement, there is little incentive to post. But also, if there is nothing posted, there is nothing to engage with. Chicken, egg. Vicious or virtuous circle.

Content mirroring provides a way to test the waters, so to speak. It provides a zero-marginal-effort means to get your content onto ADN and see if the community there is interested in it. If there’s engagement, (A) reciprocate the engagement, and (B) consider making dedicated or channel-specific content. This does require that you read ADN, monitor the mentions, etc., but none of that is visible in the “posted with IFTTT” blurb.