The short-form week of 2–8 Mar 2015

09 Mar 2015; last modified 11 Mar 2015

The week in review, 140 characters at a time.

This document was created automatically from my archive of my Twitter stream. Due to limitations in the Twitter API and occasional glitches in my archiving system, it may not be 100% complete.

Monday at 02:31pm

In the wake of Google policy changes wrt acceptable content, microblogging service Ello announces that March is NSFW month. *chuckle*—@ndw

Tuesday at 03:13am

Them not invent yet, or us. So just treat all human same for now.—@PlioceneBloke

Tuesday at 12:48pm

OH "And if you do, god help you, because those specs were not written to be read by people who don't already know what they say."—@ndw

In a conversation that started on Tuesday at 06:10pm

I think my "Epson V600 Photo" scanner is giving up the ghost. Recommendations, #lazyweb?—@ndw

@ndw check @wirecutter very happy with their top choice for laser printer.—@kstirman

@kstirman @wirecutter Thanks, Kelly.—@ndw

Tuesday at 09:54pm

RT @xmlcalabash: Freshly sharpened: bleeding edge experimental XML Calabash 1.0.31 released. http://t.co/lUCqOL2mWF—@ndw

Wednesday at 08:27am

Wow. Google Contacts are suddenly and unexpectedly completely different this morning. Not sure I'm impressed, really.—@ndw

In a conversation that started on Wednesday at 10:31am

Disk failure has brought http://t.co/1cNyxxBH5qq, *.nwalsh.com, etc. down. And @DALDEI and I were just talking about setting it up in EC2...—@ndw

@ndw @DALDEI If your considering EC2 then http://t.co/EuZ65nyHv1 is a good alternative if your into green—@adamretter

Things are back up, but there'll be some more bobbling over the next few days.—@ndw

@ndw @DALDEI But you were saved by your backup procedure....?—@dpawson

@dpawson @DALDEI I believe so. I'm going to find out, right? Backups I can do, restores, we'll see! (But I am optimistic.)—@ndw

@ndw @DALDEI Yep. Never tempted to try... just in case. Fingers crossed.—@dpawson

@ndw I'm tempted to use @digitalocean for a pet project, read/heard good things. Can be cheaper than EC2 @DALDEI—@rdeltour

Wednesday at 04:40pm

What a wonderful document: Chuck Jones's rules for writing the Road Runner and Wile E. Coyote. ht @AmosPosner http://t.co/o5ziZymEcY—@saladinahmed

In a conversation that started on Wednesday at 06:12pm

@ndw is http://t.co/Q1FJAnoDU8 down for the time being? I'm working on some Xproc and would love to reference the site!—@taegyunKK

@ndw Didn't see the tweet about your disk failure, hope the recovery goes smoothly—@taegyunKK

@taegyunKK It's back, I believe. It'll probably be down for a short while tomorrow or the day after. Shout if you have troubles.—@ndw

Thursday at 01:05pm

You ever go to put Greek cheese on something but then realize you already did it? A fetaccompli—@hellophia

In a conversation that started on Thursday at 01:23pm

@ndw Is it possible to feed the output of a <p:xslt> step and insert it into the <c:body> of a <p:http-request>? #Xproc—@taegyunKK

@taegyunKK Certainly. Though it depends exactly what you want to do. You can use p:wrap to put a c:body around the output.—@ndw

@ndw @xquery illustration of what I'm trying to achieve.. feed the last <p:xslt> step output into the <c:body> http://t.co/s8mTYzqKqu—@taegyunKK

@taegyunKK @ndw yes use p:template step, as described here http://t.co/jwQIDk4O4f—@xquery

Thursday at 08:50pm

Speeding millionaire gets 54,000-euro fine. Let's hear it for Finland: Finland's speeding fines are linked to... http://t.co/2t1g5uSy9W—@jwz

Thursday at 10:32pm

RT @alexmilowski: Using #nodejs to run #xquery over #json in #MarkLogic is really awesome! Oh, the things I will do with this ...—@ndw

Thursday at 11:56pm

http://t.co/HSutHCEvPU—@SciencePorn

Sunday at 04:09pm

If we all club together we could raise enough money to buy Monday and have it destroyed—@SoVeryBritish