Recent changes to this wiki:

blog update
diff --git a/blog/entry/comically_bad_shipping_estimates_and_middlemen.mdwn b/blog/entry/comically_bad_shipping_estimates_and_middlemen.mdwn
new file mode 100644
index 00000000..6aa86b2a
--- /dev/null
+++ b/blog/entry/comically_bad_shipping_estimates_and_middlemen.mdwn
@@ -0,0 +1,45 @@
+My inverter has unfortunately died, and I wanted to replace it with the
+same model. Ideally before I lose the contents of the fridge. It's a 24v
+inverter, which is not at all as easy to find a replacement for as a 12v
+inverter would be.
+
+Somehow Walmart was the only retailer that 
+[had it available](https://www.walmart.com/ip/AIMS-Power-1500-Watt-48-Volt-Pure-Sine-Inverter/35887513)
+with a delivery estimate: Just 2 days.
+
+[[!img pics/shipping/walmart.png]]
+
+It's the second day now, with no indication they've shipped it. 
+I noticed the "sold and shipped by Zoro", so went and
+[found it on that website](https://www.zoro.com/aims-power-pure-sine-inverter-1500w-24v-pwri150024s/i/G4430015/).
+
+[[!img pics/shipping/zorro.png]]
+
+So, the reality is it ships direct from China via container ship. As does
+every product from Zoro, which all show as 2 day delivery on Walmart's website.
+
+I don't think this is a pandemic thing. I think it's a trying to compete
+with Amazon and failing thing.
+
+----
+
+My other comically bad shipping estimate this pandemic was from Amazon
+though. There was a run this summer on Kayaks, because social distancing is
+great on the water. I found a high quality inflatable kayak.
+
+Amazon said "only 2 left in stock" and promised delivery in 1 week.
+One week later, it had not shipped, and they updated the delivery
+estimate forward 1 week. A week after that, ditto.
+
+Eventually I bought a new model from the same manufacturer, Advanced
+Elements. Unfortunately, that kayak exploded the second time I inflated it,
+due to a manufacturing defect.
+
+So I got in touch with Advanced Elements and they offered a replacement. I
+asked if, instead, they maybe still had any of the older model of kayak
+I had tried to order. They checked their warehouse, and found
+"the last one" in a corner somewhere.
+
+No shipping estimate was provided. It arrived in 3 days.
+
+[[!img pics/kayak_webb_island.jpg]]
diff --git a/blog/pics/kayak_webb_island.jpg b/blog/pics/kayak_webb_island.jpg
new file mode 100644
index 00000000..ff8c3beb
Binary files /dev/null and b/blog/pics/kayak_webb_island.jpg differ
diff --git a/blog/pics/shipping/walmart.png b/blog/pics/shipping/walmart.png
new file mode 100644
index 00000000..127e6be1
Binary files /dev/null and b/blog/pics/shipping/walmart.png differ
diff --git a/blog/pics/shipping/zorro.png b/blog/pics/shipping/zorro.png
new file mode 100644
index 00000000..0ca5b13f
Binary files /dev/null and b/blog/pics/shipping/zorro.png differ

update
diff --git a/blog/entry/AIMS_inverter_control_via_GPIO_ports.mdwn b/blog/entry/AIMS_inverter_control_via_GPIO_ports.mdwn
index 121f9ac1..8a70a1e6 100644
--- a/blog/entry/AIMS_inverter_control_via_GPIO_ports.mdwn
+++ b/blog/entry/AIMS_inverter_control_via_GPIO_ports.mdwn
@@ -43,3 +43,9 @@ It works!
 	joey@darkstar:~>ssh house inverter status
 	on
 
+---
+
+Update fall 2020: This inverter died after 2.5 years of daily light use.
+While it's possible this control had something to do with it, it seems more
+likely that it was value engineered to not last much longer than its 2 year
+warantee period.

add news item for pdmenu 1.3.6
diff --git a/code/pdmenu/news/version_1.3.1.mdwn b/code/pdmenu/news/version_1.3.1.mdwn
deleted file mode 100644
index 3d4d3d19..00000000
--- a/code/pdmenu/news/version_1.3.1.mdwn
+++ /dev/null
@@ -1,3 +0,0 @@
-pdmenu 1.3.1 released with [[!toggle text="these changes"]]
-[[!toggleable text="""
-   * Use arch wildcards in build deps. Closes: #[634487](http://bugs.debian.org/634487)"""]]
\ No newline at end of file
diff --git a/code/pdmenu/news/version_1.3.6.mdwn b/code/pdmenu/news/version_1.3.6.mdwn
new file mode 100644
index 00000000..bdc9c1b7
--- /dev/null
+++ b/code/pdmenu/news/version_1.3.6.mdwn
@@ -0,0 +1,4 @@
+pdmenu 1.3.6 released with [[!toggle text="these changes"]]
+[[!toggleable text="""
+   * Fix build with gcc 10.
+     Thanks, Fabrice Fontaine."""]]
\ No newline at end of file

add news item for moreutils 0.64
diff --git a/code/moreutils/news/version_0.59.mdwn b/code/moreutils/news/version_0.59.mdwn
deleted file mode 100644
index 1d39e7ba..00000000
--- a/code/moreutils/news/version_0.59.mdwn
+++ /dev/null
@@ -1,10 +0,0 @@
-moreutils 0.59 released with [[!toggle text="these changes"]]
-[[!toggleable text="""
-   * Makefile: add DOCBOOKXSL setting.
-     Thanks, Kevin Bullock
-   * parallel: include signal.h to fix warning when building with clang
-     Thanks, Kevin Bullock
-   * chronic: Added -v option for more verbose output.
-     Thanks, Tomas Mudrunka
-   * chronic: Added -e option to display any stderr.
-     Thanks, Tomas Mudrunka"""]]
\ No newline at end of file
diff --git a/code/moreutils/news/version_0.64.mdwn b/code/moreutils/news/version_0.64.mdwn
new file mode 100644
index 00000000..f00f532a
--- /dev/null
+++ b/code/moreutils/news/version_0.64.mdwn
@@ -0,0 +1,8 @@
+moreutils 0.64 released with [[!toggle text="these changes"]]
+[[!toggleable text="""
+   * parallel: fix typo in usage message.
+   * Makefile: Propagate compiler and linker flags when building is\_utf8.
+   * ts: Fix parsing of ISO-8601 dates.
+     Thanks, David Laban.
+   * parallel: Allow compiling with uClibc-ng, which does not have getloadavg.
+     Thanks, Rosen Penev"""]]
\ No newline at end of file

Added a comment: it might be a variation of TOCTOU
diff --git a/blog/entry/process_wild_ride/comment_1_a18ee2d5bd831b48ce67178d8ee4591a._comment b/blog/entry/process_wild_ride/comment_1_a18ee2d5bd831b48ce67178d8ee4591a._comment
new file mode 100644
index 00000000..fc5c55df
--- /dev/null
+++ b/blog/entry/process_wild_ride/comment_1_a18ee2d5bd831b48ce67178d8ee4591a._comment
@@ -0,0 +1,16 @@
+[[!comment format=mdwn
+ username="cwk"
+ avatar="http://cdn.libravatar.org/avatar/b717a7ec6c3c6dbd10662df8db1564d1"
+ subject="it might be a variation of TOCTOU"
+ date="2020-08-15T15:50:32Z"
+ content="""
+Hi,
+
+I think what you found might be a variation of TOCTOU - time of creation, time of access.
+
+For example (although slightly different, but it's the same underlying idea):
+
+https://duo.com/decipher/docker-bug-allows-root-access-to-host-file-system
+
+
+"""]]

Request for better handling of no stdin with vipe
diff --git a/code/moreutils/discussion.mdwn b/code/moreutils/discussion.mdwn
index cc0fd4a8..1785edfc 100644
--- a/code/moreutils/discussion.mdwn
+++ b/code/moreutils/discussion.mdwn
@@ -652,3 +652,16 @@ Curiously, running bar.sh directly doesn't have this problem.  I'm not sure what
 * Please can the manpage warn of the non-preservation of order, on the collected stdout from child processes?  
   On first inspection with `pee md5sum sha256sum` vs `pee sha256sum md5sum`, and on a fast/idle machine, it looks like stdout are collected and then written. But more complex examples show that stdouts may be interleaved even when there have been no newlines yet, so `pee 'md5sum > foo.md5' 'sha256sum > foo.sha256'` is a much better solution.  Thanks -- m  
   *ps.* no bytes were harmed in our discovery of this behaviour, because we've seen interleaved data too many times before! :-]
+
+## Vipe without stdin
+
+Hi Joey, thanks for your work on moreutils. I use vipe all the time. As someone else said, this is the killer app :)
+Sometimes I would like to use vipe without receiving any input first, so that I can set up some text for piping to another program. Kind of like here-docs or echo, except you get to edit the text with vim first. A simple example could look something like this:
+
+    vipe | wc -c
+
+More often, I might want to do something like this:
+
+    vipe | datamash sum 1
+
+Now, vipe can *sort of* do this, by using either a here-string (`vipe <<< "" | wc -c`) or by pressing Ctrl-D as soon as vipe launches. I wondered if we could just skip the Ctrl-D step and have vipe detect when no stdin has been given to it; instead, jump straight into an empty vim document? - TR

blog update
diff --git a/blog/entry/process_wild_ride.mdwn b/blog/entry/process_wild_ride.mdwn
new file mode 100644
index 00000000..daa12fbb
--- /dev/null
+++ b/blog/entry/process_wild_ride.mdwn
@@ -0,0 +1,30 @@
+[[!meta title="Mr Process's wild ride"]]
+
+When a unix process is running in a directory, and that directory gets
+renamed, the process is taken on a ride to a new location in the
+filesystem. Suddenly, any "../" paths it might be using point to new, and
+unexpected locations.
+
+This can be a source of interesting behavior, and also of security holes.
+
+Suppose root is poking around in `~user/foo/bar/` and decides to 
+`vim ../../etc/conffile`
+
+If the user notices this process is running, they can `mv ~/foo/bar /tmp`
+and when vim saves the file, it will write to `/tmp/bar/../../etc/conffile`
+AKA `/etc/conffile`.
+
+(Vim does warn that the file has changed while it was being edited. Other
+editors may not. Or root may be feeling especially BoFH and decide to
+overwrite the user's changes to their file. Or the rename could perhaps be
+carefully timed to avoid vim's overwrite protection.)
+
+Or, suppose root, in the same place, decides to archive `../../etc` with tar,
+and then delete it:
+
+	tar cf etc.tar ../../etc; rm -rf ../../etc
+
+Now the user has some time to take root's shell on a ride, before the
+`rm` starts ... and make it delete all of `/etc`!
+
+Anyone know if this class of security hole has a name?

update
diff --git a/blog/entry/bracketing_and_async_exceptions_in_haskell.mdwn b/blog/entry/bracketing_and_async_exceptions_in_haskell.mdwn
index a0f70c10..65b3923d 100644
--- a/blog/entry/bracketing_and_async_exceptions_in_haskell.mdwn
+++ b/blog/entry/bracketing_and_async_exceptions_in_haskell.mdwn
@@ -76,11 +76,11 @@ What can libraries do?
   <pre>
   bracketInsulated :: IO a -> (a -> IO b) -> (a -> IO c) -> IO c
   bracketInsulated a b = bracket
-  	(async a >>= wait)
-  	(\v -> async (b v) >>= wait)
+  	(uninterruptibleMask $ \u -> async (u a) >>= u . wait)
+  	(\v -> uninterruptibleMask $ \u -> async (u (b v)) >>= u . wait)
   </pre>
-  (This implementation may not be quite right though -- does `async` 
-  use any interruptable operations?)
+  (Note use of uninterruptibleMask here in case async itself does an
+  interruptable operation. My first version got that wrong.. This is hard!)
 
 
 My impression of the state of things now is that you should be very cautious

update
diff --git a/blog/entry/bracketing_and_async_exceptions_in_haskell.mdwn b/blog/entry/bracketing_and_async_exceptions_in_haskell.mdwn
index 34f44dfb..a0f70c10 100644
--- a/blog/entry/bracketing_and_async_exceptions_in_haskell.mdwn
+++ b/blog/entry/bracketing_and_async_exceptions_in_haskell.mdwn
@@ -79,6 +79,9 @@ What can libraries do?
   	(async a >>= wait)
   	(\v -> async (b v) >>= wait)
   </pre>
+  (This implementation may not be quite right though -- does `async` 
+  use any interruptable operations?)
+
 
 My impression of the state of things now is that you should be very cautious
 using `race` or `cancel` or `withAsync` or the like, unless the thread is small

comment
diff --git a/blog/entry/bracketing_and_async_exceptions_in_haskell/comment_3_84bdc994e5569c0efa45993a3073b694._comment b/blog/entry/bracketing_and_async_exceptions_in_haskell/comment_3_84bdc994e5569c0efa45993a3073b694._comment
new file mode 100644
index 00000000..b812ca37
--- /dev/null
+++ b/blog/entry/bracketing_and_async_exceptions_in_haskell/comment_3_84bdc994e5569c0efa45993a3073b694._comment
@@ -0,0 +1,18 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 3"""
+ date="2020-06-11T16:02:44Z"
+ content="""
+@alex safe-exceptions and unliftio use uninterruptibleMask in its
+async safe bracket. Which is ok if the cleanup action is fast, but does
+risk the program not responding to ctrl-c if the cleanup takes a while for
+whatever reason.
+
+As well as SIGINT, there's also the possibility that an async exception is
+thrown for some truely exceptional circumstance, like a segfault. Most code
+would do well to exit immediately on such an exception, not mask it.
+
+I wonder if there's a way to make an uninterruptibleMask that masks only
+a specific async exception, eg the AsyncCancelled exception. 
+Probably this would need ghc support, if it's possible at all.
+"""]]

Added a comment
diff --git a/blog/entry/bracketing_and_async_exceptions_in_haskell/comment_2_1a61fb4f5168aab94775046cd8096eb3._comment b/blog/entry/bracketing_and_async_exceptions_in_haskell/comment_2_1a61fb4f5168aab94775046cd8096eb3._comment
new file mode 100644
index 00000000..219d48d4
--- /dev/null
+++ b/blog/entry/bracketing_and_async_exceptions_in_haskell/comment_2_1a61fb4f5168aab94775046cd8096eb3._comment
@@ -0,0 +1,9 @@
+[[!comment format=mdwn
+ username="gueux+joeyh@3dc86e5b17c9ce2c7edd4ce108f939239c363bc6"
+ nickname="gueux+joeyh"
+ avatar="http://cdn.libravatar.org/avatar/cb159899815e640e3bfc18c409cc7e06"
+ subject="comment 2"
+ date="2020-06-11T12:33:20Z"
+ content="""
+As alex said, safe-exceptions may help. There was a series of blog posts a few years ago about async exceptions: https://tech.fpcomplete.com/blog/2016/06/announce-safe-exceptions/ (I think that is the last post)
+"""]]

Added a comment: Consider UnliftIO
diff --git a/blog/entry/bracketing_and_async_exceptions_in_haskell/comment_1_e2cb821f69f273d9d3e2bcbb442ac0d8._comment b/blog/entry/bracketing_and_async_exceptions_in_haskell/comment_1_e2cb821f69f273d9d3e2bcbb442ac0d8._comment
new file mode 100644
index 00000000..32b7718a
--- /dev/null
+++ b/blog/entry/bracketing_and_async_exceptions_in_haskell/comment_1_e2cb821f69f273d9d3e2bcbb442ac0d8._comment
@@ -0,0 +1,9 @@
+[[!comment format=mdwn
+ username="alex@e098de4fb1118aae3f6bc5b218ee9e36d10e385c"
+ nickname="alex"
+ avatar="http://cdn.libravatar.org/avatar/c498b37d672ddd88ee07e928f287c2dd"
+ subject="Consider UnliftIO"
+ date="2020-06-11T03:15:36Z"
+ content="""
+Consider [safe-exceptions](https://hackage.haskell.org/package/safe-exceptions) or [unliftio](https://hackage.haskell.org/package/unliftio) (UnliftIO.Exception) both of which have async-safe drop-in replacements for bracket, catch, etc.
+"""]]

try
diff --git a/blog/entry/bracketing_and_async_exceptions_in_haskell.mdwn b/blog/entry/bracketing_and_async_exceptions_in_haskell.mdwn
index 8b30078b..34f44dfb 100644
--- a/blog/entry/bracketing_and_async_exceptions_in_haskell.mdwn
+++ b/blog/entry/bracketing_and_async_exceptions_in_haskell.mdwn
@@ -64,7 +64,7 @@ What can libraries do?
 * Use `finally`. Good mostly in simple situations; more complicated things
   would be hard to write this way.
   <pre>
-  hClose h `finally` removeFile name
+  hClose h \`finally\` removeFile name
   </pre>
 
 * Use `uninterruptibleMask`, but it's a big hammer and is often not the

try
diff --git a/blog/entry/bracketing_and_async_exceptions_in_haskell.mdwn b/blog/entry/bracketing_and_async_exceptions_in_haskell.mdwn
index 2c64776d..8b30078b 100644
--- a/blog/entry/bracketing_and_async_exceptions_in_haskell.mdwn
+++ b/blog/entry/bracketing_and_async_exceptions_in_haskell.mdwn
@@ -63,7 +63,9 @@ What can libraries do?
 
 * Use `finally`. Good mostly in simple situations; more complicated things
   would be hard to write this way.
-  <pre>hClose h `finally` removeFile name</pre>
+  <pre>
+  hClose h `finally` removeFile name
+  </pre>
 
 * Use `uninterruptibleMask`, but it's a big hammer and is often not the
   right tool for the job. If the operation takes a while to run,

try
diff --git a/blog/entry/bracketing_and_async_exceptions_in_haskell.mdwn b/blog/entry/bracketing_and_async_exceptions_in_haskell.mdwn
index 7fecaa43..2c64776d 100644
--- a/blog/entry/bracketing_and_async_exceptions_in_haskell.mdwn
+++ b/blog/entry/bracketing_and_async_exceptions_in_haskell.mdwn
@@ -63,10 +63,7 @@ What can libraries do?
 
 * Use `finally`. Good mostly in simple situations; more complicated things
   would be hard to write this way.
-
-[[!format haskell """
-hClose h `finally` removeFile name
-"""]]
+  <pre>hClose h `finally` removeFile name</pre>
 
 * Use `uninterruptibleMask`, but it's a big hammer and is often not the
   right tool for the job. If the operation takes a while to run,
@@ -74,13 +71,12 @@ hClose h `finally` removeFile name
 
 * May be better to run the actions in worker threads, to insulate
   them from receiving any async exceptions.
-  
-[[!format haskell """
-bracketInsulated :: IO a -> (a -> IO b) -> (a -> IO c) -> IO c
-bracketInsulated a b = bracket
-	(async a >>= wait)
-	(\v -> async (b v) >>= wait)
-"""]]
+  <pre>
+  bracketInsulated :: IO a -> (a -> IO b) -> (a -> IO c) -> IO c
+  bracketInsulated a b = bracket
+  	(async a >>= wait)
+  	(\v -> async (b v) >>= wait)
+  </pre>
 
 My impression of the state of things now is that you should be very cautious
 using `race` or `cancel` or `withAsync` or the like, unless the thread is small

oop
diff --git a/blog/entry/bracketing_and_async_exceptions_in_haskell.mdwn b/blog/entry/bracketing_and_async_exceptions_in_haskell.mdwn
index 46910113..7fecaa43 100644
--- a/blog/entry/bracketing_and_async_exceptions_in_haskell.mdwn
+++ b/blog/entry/bracketing_and_async_exceptions_in_haskell.mdwn
@@ -65,7 +65,7 @@ What can libraries do?
   would be hard to write this way.
 
 [[!format haskell """
-	hClose h `finally` removeFile name
+hClose h `finally` removeFile name
 """]]
 
 * Use `uninterruptibleMask`, but it's a big hammer and is often not the
@@ -76,10 +76,10 @@ What can libraries do?
   them from receiving any async exceptions.
   
 [[!format haskell """
-	bracketInsulated :: IO a -> (a -> IO b) -> (a -> IO c) -> IO c
-	bracketInsulated a b = bracket
-		(async a >>= wait)
-		(\v -> async (b v) >>= wait)
+bracketInsulated :: IO a -> (a -> IO b) -> (a -> IO c) -> IO c
+bracketInsulated a b = bracket
+	(async a >>= wait)
+	(\v -> async (b v) >>= wait)
 """]]
 
 My impression of the state of things now is that you should be very cautious

oop
diff --git a/blog/entry/bracketing_and_async_exceptions_in_haskell.mdwn b/blog/entry/bracketing_and_async_exceptions_in_haskell.mdwn
index 3b9d80ff..46910113 100644
--- a/blog/entry/bracketing_and_async_exceptions_in_haskell.mdwn
+++ b/blog/entry/bracketing_and_async_exceptions_in_haskell.mdwn
@@ -61,14 +61,12 @@ What can libraries do?
   there should be an expectation that "withFoo" always is, but if so the
   Haskell comminity has some work ahead of it.
 
-* Use `finally`, eg 
+* Use `finally`. Good mostly in simple situations; more complicated things
+  would be hard to write this way.
 
 [[!format haskell """
-  	hClose h `finally` removeFile name
+	hClose h `finally` removeFile name
 """]]
-  
-  Good mostly in simple situations; more complicated things would be hard
-  to write this way.
 
 * Use `uninterruptibleMask`, but it's a big hammer and is often not the
   right tool for the job. If the operation takes a while to run,
@@ -78,10 +76,10 @@ What can libraries do?
   them from receiving any async exceptions.
   
 [[!format haskell """
-  	bracketInsulated :: IO a -> (a -> IO b) -> (a -> IO c) -> IO c
-  	bracketInsulated a b = bracket
-  		(async a >>= wait)
-  		(\v -> async (b v) >>= wait)
+	bracketInsulated :: IO a -> (a -> IO b) -> (a -> IO c) -> IO c
+	bracketInsulated a b = bracket
+		(async a >>= wait)
+		(\v -> async (b v) >>= wait)
 """]]
 
 My impression of the state of things now is that you should be very cautious

oop
diff --git a/blog/entry/bracketing_and_async_exceptions_in_haskell.mdwn b/blog/entry/bracketing_and_async_exceptions_in_haskell.mdwn
index 1b95f4d3..3b9d80ff 100644
--- a/blog/entry/bracketing_and_async_exceptions_in_haskell.mdwn
+++ b/blog/entry/bracketing_and_async_exceptions_in_haskell.mdwn
@@ -63,7 +63,7 @@ What can libraries do?
 
 * Use `finally`, eg 
 
-[[!code language=haskell """
+[[!format haskell """
   	hClose h `finally` removeFile name
 """]]
   
@@ -77,7 +77,7 @@ What can libraries do?
 * May be better to run the actions in worker threads, to insulate
   them from receiving any async exceptions.
   
-[[!code language=haskell """
+[[!format haskell """
   	bracketInsulated :: IO a -> (a -> IO b) -> (a -> IO c) -> IO c
   	bracketInsulated a b = bracket
   		(async a >>= wait)

markdown!!
diff --git a/blog/entry/bracketing_and_async_exceptions_in_haskell.mdwn b/blog/entry/bracketing_and_async_exceptions_in_haskell.mdwn
index d3bd88f9..1b95f4d3 100644
--- a/blog/entry/bracketing_and_async_exceptions_in_haskell.mdwn
+++ b/blog/entry/bracketing_and_async_exceptions_in_haskell.mdwn
@@ -63,7 +63,9 @@ What can libraries do?
 
 * Use `finally`, eg 
 
+[[!code language=haskell """
   	hClose h `finally` removeFile name
+"""]]
   
   Good mostly in simple situations; more complicated things would be hard
   to write this way.
@@ -75,10 +77,12 @@ What can libraries do?
 * May be better to run the actions in worker threads, to insulate
   them from receiving any async exceptions.
   
+[[!code language=haskell """
   	bracketInsulated :: IO a -> (a -> IO b) -> (a -> IO c) -> IO c
   	bracketInsulated a b = bracket
   		(async a >>= wait)
   		(\v -> async (b v) >>= wait)
+"""]]
 
 My impression of the state of things now is that you should be very cautious
 using `race` or `cancel` or `withAsync` or the like, unless the thread is small

markdown
diff --git a/blog/entry/bracketing_and_async_exceptions_in_haskell.mdwn b/blog/entry/bracketing_and_async_exceptions_in_haskell.mdwn
index 51eb938f..d3bd88f9 100644
--- a/blog/entry/bracketing_and_async_exceptions_in_haskell.mdwn
+++ b/blog/entry/bracketing_and_async_exceptions_in_haskell.mdwn
@@ -61,8 +61,10 @@ What can libraries do?
   there should be an expectation that "withFoo" always is, but if so the
   Haskell comminity has some work ahead of it.
 
-* Use `finally`, eg `hClose h \`finally\` removeFile name`
+* Use `finally`, eg 
 
+  	hClose h `finally` removeFile name
+  
   Good mostly in simple situations; more complicated things would be hard
   to write this way.
 
@@ -72,11 +74,11 @@ What can libraries do?
 
 * May be better to run the actions in worker threads, to insulate
   them from receiving any async exceptions.
-
-	bracketInsulated :: IO a -> (a -> IO b) -> (a -> IO c) -> IO c
-	bracketInsulated a b = bracket
-		(async a >>= wait)
-		(\v -> async (b v) >>= wait)
+  
+  	bracketInsulated :: IO a -> (a -> IO b) -> (a -> IO c) -> IO c
+  	bracketInsulated a b = bracket
+  		(async a >>= wait)
+  		(\v -> async (b v) >>= wait)
 
 My impression of the state of things now is that you should be very cautious
 using `race` or `cancel` or `withAsync` or the like, unless the thread is small

markdown
diff --git a/blog/entry/bracketing_and_async_exceptions_in_haskell.mdwn b/blog/entry/bracketing_and_async_exceptions_in_haskell.mdwn
index ad0f7c0d..51eb938f 100644
--- a/blog/entry/bracketing_and_async_exceptions_in_haskell.mdwn
+++ b/blog/entry/bracketing_and_async_exceptions_in_haskell.mdwn
@@ -61,9 +61,7 @@ What can libraries do?
   there should be an expectation that "withFoo" always is, but if so the
   Haskell comminity has some work ahead of it.
 
-* Use `finally`, eg
-
-	hClose h `finally` removeFile name
+* Use `finally`, eg `hClose h \`finally\` removeFile name`
 
   Good mostly in simple situations; more complicated things would be hard
   to write this way.

blog update
diff --git a/blog/entry/bracketing_and_async_exceptions_in_haskell.mdwn b/blog/entry/bracketing_and_async_exceptions_in_haskell.mdwn
new file mode 100644
index 00000000..ad0f7c0d
--- /dev/null
+++ b/blog/entry/bracketing_and_async_exceptions_in_haskell.mdwn
@@ -0,0 +1,94 @@
+I've been digging into async exceptions in haskell, and getting more
+and more concerned. In particular, `bracket` seems to be often used in ways
+that are not async exception safe. I've found multiple libraries with problems.
+
+Here's an example:
+
+	withTempFile a = bracket setup cleanup a
+	  where
+		setup = openTempFile "/tmp" "tmpfile"
+		cleanup (name, h) = do
+			hClose h
+			removeFile name
+
+This looks reasonably good, it makes sure to clean up after itself even
+when the action throws an exception.
+
+But, in fact that code can leave stale temp files lying around.
+If the thread receives an async exception when `hClose` is
+running, it will be interrupted before the file is removed.
+
+We normally think of `bracket` as masking exceptions, but it
+doesn't prevent async exceptions in all cases.
+See [Control.Exception on "interruptible operations"](http://hackage.haskell.org/package/base-4.14.0.0/docs/Control-Exception.html#g:13),
+which can receive async exceptions even when other exceptions are masked.
+
+It's a bit surprising, but `hClose` is such an interruptable operation,
+because it flushes the write buffer. The only way to know is to
+[read the code](https://hackage.haskell.org/package/base-4.14.0.0/docs/src/GHC.IO.Handle.Internals.html#hClose_help).
+
+It can be quite hard to determine if an operation is interruptable, since
+it can come down to whether it retries a STM transaction, or uses a MVar
+that is not always full. I've been auditing libraries and I often have
+to look at code several dependencies away, and even then may not be sure
+if a library has this problem.
+
+* [process's withCreateProcess](https://github.com/haskell/process/issues/183)
+  could fail to wait on the process, leaving a zombie. Might also leak
+  file descriptors?
+
+* [http-client's withResponse](https://github.com/snoyberg/http-client/issues/436)
+  might fail to close a network connection. (If a MVar happened to be empty
+  when it's called.)
+
+  Worth noting that there are plenty of examples of using http-client
+  to eg, race downloading two urls and cancel the slower download. Which 
+  is just the kind of use of an async exception that could cause a problem.
+
+* persistent's withSqlPool and withSqlConn might fail to clean up,
+  when used with persistent-postgresql. (If another thread is using the
+  connection and so a MVar over in postgresql-simple is empty.)
+
+* concurrent-output has some locking code that is not async exception safe.
+  (My library, so I've fixed part of it, and hope to fix the rest.)
+
+So far, around half of the libraries I've looked at, that use `bracket`
+or `onException` or the like probably have this problem.
+
+What can libraries do?
+
+* Document whether these things are async exception safe. Or perhaps
+  there should be an expectation that "withFoo" always is, but if so the
+  Haskell comminity has some work ahead of it.
+
+* Use `finally`, eg
+
+	hClose h `finally` removeFile name
+
+  Good mostly in simple situations; more complicated things would be hard
+  to write this way.
+
+* Use `uninterruptibleMask`, but it's a big hammer and is often not the
+  right tool for the job. If the operation takes a while to run,
+  the program will not respond to ctrl-c during that time.
+
+* May be better to run the actions in worker threads, to insulate
+  them from receiving any async exceptions.
+
+	bracketInsulated :: IO a -> (a -> IO b) -> (a -> IO c) -> IO c
+	bracketInsulated a b = bracket
+		(async a >>= wait)
+		(\v -> async (b v) >>= wait)
+
+My impression of the state of things now is that you should be very cautious
+using `race` or `cancel` or `withAsync` or the like, unless the thread is small
+and easy to audit for these problems. Kind of a shame, since I had wanted to
+be able to cancel a thread that is big and sprawling and uses all the
+libraries mentioned above.
+
+----
+
+This work was sponsored by Jake Vosloo and Graham Spencer
+[on Patreon](https://patreon.com/joeyh).
+
+[[!tag haskell]]

diff --git a/code/moreutils/discussion.mdwn b/code/moreutils/discussion.mdwn
index 326e3e07..cc0fd4a8 100644
--- a/code/moreutils/discussion.mdwn
+++ b/code/moreutils/discussion.mdwn
@@ -5,6 +5,7 @@ comments --[[Joey]]
 Sponge gets terminated with SIGSEGV if it tries to append to an unwritable file:
 
 (make sure you dont have a file named "a")
+
     sudo touch a && sudo chown 000 a && echo 1 | sponge -a a
     sudo rm -f a
 

Formatting
diff --git a/code/moreutils/discussion.mdwn b/code/moreutils/discussion.mdwn
index 7dc15a17..326e3e07 100644
--- a/code/moreutils/discussion.mdwn
+++ b/code/moreutils/discussion.mdwn
@@ -5,8 +5,8 @@ comments --[[Joey]]
 Sponge gets terminated with SIGSEGV if it tries to append to an unwritable file:
 
 (make sure you dont have a file named "a")
-sudo touch a && sudo chown 000 a && echo 1 | sponge -a a
-sudo rm -f a
+    sudo touch a && sudo chown 000 a && echo 1 | sponge -a a
+    sudo rm -f a
 
 Arch Linux, moreutils 0.63-1
 

Sponge segmentation fault
diff --git a/code/moreutils/discussion.mdwn b/code/moreutils/discussion.mdwn
index f11410e3..7dc15a17 100644
--- a/code/moreutils/discussion.mdwn
+++ b/code/moreutils/discussion.mdwn
@@ -1,6 +1,15 @@
 Feel free to edit this page to suggest tools to add, or make any other
 comments --[[Joey]]
 
+## Sponge segmentation fault
+Sponge gets terminated with SIGSEGV if it tries to append to an unwritable file:
+
+(make sure you dont have a file named "a")
+sudo touch a && sudo chown 000 a && echo 1 | sponge -a a
+sudo rm -f a
+
+Arch Linux, moreutils 0.63-1
+
 ## tool suggestion: "re" (Reach Recent Folders)
 
 The `re` command aims to save numerous `cd` operations for reaching recently-used folders.

poll vote (watched it all, liked it\)
diff --git a/blog/entry/watch_me_code_for_half_an_hour.mdwn b/blog/entry/watch_me_code_for_half_an_hour.mdwn
index ef9dc9db..76c62951 100644
--- a/blog/entry/watch_me_code_for_half_an_hour.mdwn
+++ b/blog/entry/watch_me_code_for_half_an_hour.mdwn
@@ -14,7 +14,7 @@ Not shown is the hour I spent the next day changing the "optimize"
 subcommand implemented here into "--auto" options that can be passed to
 [[code/git-annex]]'s get and drop commands.
 
-[[!poll 66 "watched it all, liked it"" 9 "watched some, boring" 4 "too long for me" 15 "too haskell for me" 14 "not interested"]]
+[[!poll 65 "watched it all, liked it"" 9 "watched some, boring" 4 "too long for me" 15 "too haskell for me" 14 "not interested"]]
 
 [[!meta title="watch me program for half an hour"]]
 [[!tag haskell]]

poll vote (watched it all, liked it")
diff --git a/blog/entry/watch_me_code_for_half_an_hour.mdwn b/blog/entry/watch_me_code_for_half_an_hour.mdwn
index 5870344d..ef9dc9db 100644
--- a/blog/entry/watch_me_code_for_half_an_hour.mdwn
+++ b/blog/entry/watch_me_code_for_half_an_hour.mdwn
@@ -14,7 +14,7 @@ Not shown is the hour I spent the next day changing the "optimize"
 subcommand implemented here into "--auto" options that can be passed to
 [[code/git-annex]]'s get and drop commands.
 
-[[!poll 65 "watched it all, liked it" 9 "watched some, boring" 4 "too long for me" 15 "too haskell for me" 14 "not interested"]]
+[[!poll 66 "watched it all, liked it"" 9 "watched some, boring" 4 "too long for me" 15 "too haskell for me" 14 "not interested"]]
 
 [[!meta title="watch me program for half an hour"]]
 [[!tag haskell]]

poll vote (watched it all, liked it)
diff --git a/blog/entry/watch_me_code_for_half_an_hour.mdwn b/blog/entry/watch_me_code_for_half_an_hour.mdwn
index eef2f4ea..5870344d 100644
--- a/blog/entry/watch_me_code_for_half_an_hour.mdwn
+++ b/blog/entry/watch_me_code_for_half_an_hour.mdwn
@@ -14,7 +14,7 @@ Not shown is the hour I spent the next day changing the "optimize"
 subcommand implemented here into "--auto" options that can be passed to
 [[code/git-annex]]'s get and drop commands.
 
-[[!poll 64 "watched it all, liked it" 9 "watched some, boring" 4 "too long for me" 15 "too haskell for me" 14 "not interested"]]
+[[!poll 65 "watched it all, liked it" 9 "watched some, boring" 4 "too long for me" 15 "too haskell for me" 14 "not interested"]]
 
 [[!meta title="watch me program for half an hour"]]
 [[!tag haskell]]

poll vote (watched it all, liked it')
diff --git a/blog/entry/watch_me_code_for_half_an_hour.mdwn b/blog/entry/watch_me_code_for_half_an_hour.mdwn
index 5870344d..eef2f4ea 100644
--- a/blog/entry/watch_me_code_for_half_an_hour.mdwn
+++ b/blog/entry/watch_me_code_for_half_an_hour.mdwn
@@ -14,7 +14,7 @@ Not shown is the hour I spent the next day changing the "optimize"
 subcommand implemented here into "--auto" options that can be passed to
 [[code/git-annex]]'s get and drop commands.
 
-[[!poll 65 "watched it all, liked it" 9 "watched some, boring" 4 "too long for me" 15 "too haskell for me" 14 "not interested"]]
+[[!poll 64 "watched it all, liked it" 9 "watched some, boring" 4 "too long for me" 15 "too haskell for me" 14 "not interested"]]
 
 [[!meta title="watch me program for half an hour"]]
 [[!tag haskell]]

poll vote (watched it all, liked it)
diff --git a/blog/entry/watch_me_code_for_half_an_hour.mdwn b/blog/entry/watch_me_code_for_half_an_hour.mdwn
index eef2f4ea..5870344d 100644
--- a/blog/entry/watch_me_code_for_half_an_hour.mdwn
+++ b/blog/entry/watch_me_code_for_half_an_hour.mdwn
@@ -14,7 +14,7 @@ Not shown is the hour I spent the next day changing the "optimize"
 subcommand implemented here into "--auto" options that can be passed to
 [[code/git-annex]]'s get and drop commands.
 
-[[!poll 64 "watched it all, liked it" 9 "watched some, boring" 4 "too long for me" 15 "too haskell for me" 14 "not interested"]]
+[[!poll 65 "watched it all, liked it" 9 "watched some, boring" 4 "too long for me" 15 "too haskell for me" 14 "not interested"]]
 
 [[!meta title="watch me program for half an hour"]]
 [[!tag haskell]]

poll vote (watched it all, liked it)
diff --git a/blog/entry/watch_me_code_for_half_an_hour.mdwn b/blog/entry/watch_me_code_for_half_an_hour.mdwn
index 0c8af3a4..eef2f4ea 100644
--- a/blog/entry/watch_me_code_for_half_an_hour.mdwn
+++ b/blog/entry/watch_me_code_for_half_an_hour.mdwn
@@ -14,7 +14,7 @@ Not shown is the hour I spent the next day changing the "optimize"
 subcommand implemented here into "--auto" options that can be passed to
 [[code/git-annex]]'s get and drop commands.
 
-[[!poll 63 "watched it all, liked it" 9 "watched some, boring" 4 "too long for me" 15 "too haskell for me" 14 "not interested"]]
+[[!poll 64 "watched it all, liked it" 9 "watched some, boring" 4 "too long for me" 15 "too haskell for me" 14 "not interested"]]
 
 [[!meta title="watch me program for half an hour"]]
 [[!tag haskell]]

Added a comment
diff --git a/blog/entry/DIN/comment_3_f7de7c9b2bb15323f2419ca221f71d91._comment b/blog/entry/DIN/comment_3_f7de7c9b2bb15323f2419ca221f71d91._comment
new file mode 100644
index 00000000..be578415
--- /dev/null
+++ b/blog/entry/DIN/comment_3_f7de7c9b2bb15323f2419ca221f71d91._comment
@@ -0,0 +1,23 @@
+[[!comment format=mdwn
+ username="samuel.kacer@b56d07b334f1d9f89d360e15299a94e675012f6b"
+ nickname="samuel.kacer"
+ avatar="http://cdn.libravatar.org/avatar/a8626a50a086b21b8380dc7610f31e53"
+ subject="comment 3"
+ date="2020-04-13T07:57:55Z"
+ content="""
+@Joey
+
+Sectioning using \"article\" is helpful, as they provide semantics about the web page layout, but they are not considered to be a navigational landmark, so not all screen readers support navigating by \"article\" sections. From [ARIA: article role](https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Roles/Article_Role)
+
+\"Articles are not considered a navigational landmark, but many assistive technologies that support landmarks also support a means to navigate among articles. ...\"
+
+\"header\" elements are turned into navigational landmarks when they are descendants of the \"body\" element and this type of landmark is the \"banner\". They are the converse of a \"footer\" element which transform into \"content info\" landmark when it is directly child of \"body\". As navigational landmarks they are just meant for the whole page and not for individual sections of the page.
+
+In Section 4.1 of [WAI-ARIA Authoring Practices 1.1](https://www.w3.org/TR/wai-aria-practices-1.1/#bib-html-aria) is described which HTML semantic region elements get turned into aria landmarks.
+
+Finally, headings are what most screen readers go to first for navigation of a web page. So for those reasons I'd recommend making the article titles headings. If you don't want to literally make them a \"h1-6\" because it would mess with your CSS then you can just set aria attributes which will change how the page is understood by assisstive tech but not affect any visual rendering of the page.
+_a role=\"heading\" aria-level=\"2\"_Lemons_/a_
+(using _ instead of angular brackets)
+
+[More info on heading role](https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Roles/heading_role#Examples)
+"""]]

removed
diff --git a/blog/entry/DIN/comment_3_d5bbbb5d26dfbeee04d82ac443d794db._comment b/blog/entry/DIN/comment_3_d5bbbb5d26dfbeee04d82ac443d794db._comment
deleted file mode 100644
index b0d17618..00000000
--- a/blog/entry/DIN/comment_3_d5bbbb5d26dfbeee04d82ac443d794db._comment
+++ /dev/null
@@ -1,23 +0,0 @@
-[[!comment format=mdwn
- username="samuel.kacer@b56d07b334f1d9f89d360e15299a94e675012f6b"
- nickname="samuel.kacer"
- avatar="http://cdn.libravatar.org/avatar/a8626a50a086b21b8380dc7610f31e53"
- subject="comment 3"
- date="2020-04-13T07:50:09Z"
- content="""
-@Joey
-
-Sectioning using <article> is helpful, as they provide semantics about the web page layout, but they are not considered to be a navigational landmakr, so not all screen readers support navigating by <article> sections. From [ARIA: article role](https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Roles/Article_Role)
-
-\"Articles are not considered a navigational landmark, but many assistive technologies that support landmarks also support a means to navigate among articles. ...\"
-
-<header> elements are turned into navigational landmarks when they are descendants of the <body> element and this type of landmark is the \"banner\". They are the converse of a <footer> element which transform into \"content info\" landmark when it is directly child of <body>. As navigational landmarks they are just meant for the whole page and not for individual sections of the page.
-
-In Section 4.1 of [WAI-ARIA Authoring Practices 1.1](https://www.w3.org/TR/wai-aria-practices-1.1/#bib-html-aria) is described which HTML semantic region elements get turned into aria landmarks.
-
-Finally, headings are what most screen readers go to first for navigation of a web page. So for those reasons I'd recommend making the article titles headings. If you don't want to literally make them a <h1-6> because it would mess with your CSS then you can just set aria attributes which will change how the page is understood by assisstive tech but not affect any visual rendering of the page.
-_a role=\"heading\" aria-level=\"2\"_Lemons_/a_
-(using _ instead of </>)
-
-[More info on heading role](https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Roles/heading_role#Examples)
-"""]]

Added a comment
diff --git a/blog/entry/DIN/comment_3_d5bbbb5d26dfbeee04d82ac443d794db._comment b/blog/entry/DIN/comment_3_d5bbbb5d26dfbeee04d82ac443d794db._comment
new file mode 100644
index 00000000..b0d17618
--- /dev/null
+++ b/blog/entry/DIN/comment_3_d5bbbb5d26dfbeee04d82ac443d794db._comment
@@ -0,0 +1,23 @@
+[[!comment format=mdwn
+ username="samuel.kacer@b56d07b334f1d9f89d360e15299a94e675012f6b"
+ nickname="samuel.kacer"
+ avatar="http://cdn.libravatar.org/avatar/a8626a50a086b21b8380dc7610f31e53"
+ subject="comment 3"
+ date="2020-04-13T07:50:09Z"
+ content="""
+@Joey
+
+Sectioning using <article> is helpful, as they provide semantics about the web page layout, but they are not considered to be a navigational landmakr, so not all screen readers support navigating by <article> sections. From [ARIA: article role](https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Roles/Article_Role)
+
+\"Articles are not considered a navigational landmark, but many assistive technologies that support landmarks also support a means to navigate among articles. ...\"
+
+<header> elements are turned into navigational landmarks when they are descendants of the <body> element and this type of landmark is the \"banner\". They are the converse of a <footer> element which transform into \"content info\" landmark when it is directly child of <body>. As navigational landmarks they are just meant for the whole page and not for individual sections of the page.
+
+In Section 4.1 of [WAI-ARIA Authoring Practices 1.1](https://www.w3.org/TR/wai-aria-practices-1.1/#bib-html-aria) is described which HTML semantic region elements get turned into aria landmarks.
+
+Finally, headings are what most screen readers go to first for navigation of a web page. So for those reasons I'd recommend making the article titles headings. If you don't want to literally make them a <h1-6> because it would mess with your CSS then you can just set aria attributes which will change how the page is understood by assisstive tech but not affect any visual rendering of the page.
+_a role=\"heading\" aria-level=\"2\"_Lemons_/a_
+(using _ instead of </>)
+
+[More info on heading role](https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Roles/heading_role#Examples)
+"""]]

comment
diff --git a/blog/entry/DIN/comment_2_d9d0ecfea0ba53b50683d81740d75ba0._comment b/blog/entry/DIN/comment_2_d9d0ecfea0ba53b50683d81740d75ba0._comment
new file mode 100644
index 00000000..9c5a7f13
--- /dev/null
+++ b/blog/entry/DIN/comment_2_d9d0ecfea0ba53b50683d81740d75ba0._comment
@@ -0,0 +1,13 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 2"""
+ date="2020-04-12T14:31:49Z"
+ content="""
+@samuel.kacer, the sections of the blog are inside html article tags,
+and the heading of each is inside a html header tag.
+That seems like sufficient semantic information to me..
+
+I guess what I'll suggest is, if there's some reason that's not sufficient,
+you file a bug report on <https://ikiwiki.info> which is what the blog
+uses.
+"""]]

Added a comment: thanks for the alt text for graphics
diff --git a/blog/entry/DIN/comment_1_aec864b293c70d48d616d4461653aab3._comment b/blog/entry/DIN/comment_1_aec864b293c70d48d616d4461653aab3._comment
new file mode 100644
index 00000000..0a6750d8
--- /dev/null
+++ b/blog/entry/DIN/comment_1_aec864b293c70d48d616d4461653aab3._comment
@@ -0,0 +1,20 @@
+[[!comment format=mdwn
+ username="samuel.kacer@b56d07b334f1d9f89d360e15299a94e675012f6b"
+ nickname="samuel.kacer"
+ avatar="http://cdn.libravatar.org/avatar/a8626a50a086b21b8380dc7610f31e53"
+ subject="thanks for the alt text for graphics"
+ date="2020-04-12T12:18:59Z"
+ content="""
+Hi,
+
+I just stumbled onto your blog yesterday while searching for information on FRP in Haskell. Really cool stuff using Haskell for home automation in embedded systems!
+
+I just wanted to post a comment because I noticed you include nice alt text on your images, which I greatly appreciate as a blind person. One other note on accessibility is that navigating around your blog would be easier if the article headings were some sort of HTML heading like <h2>. Screen readers give shortcuts for jumping between different headings, so having sections of a webpage of intrest start with headings means as a screen reader user I could very easily switch between them instead of scrolling  through the whole article before finding the beginning of the next one.
+
+Just thought I would mention it since it seems you already care about accessibility.
+
+Oh and happy late birthday!
+
+Regards,
+Sam
+"""]]

Added a comment: Happy birthday!
diff --git a/blog/entry/lemons/comment_5_83be6177d9a79f379ded08576c3d80bf._comment b/blog/entry/lemons/comment_5_83be6177d9a79f379ded08576c3d80bf._comment
new file mode 100644
index 00000000..ac2f182c
--- /dev/null
+++ b/blog/entry/lemons/comment_5_83be6177d9a79f379ded08576c3d80bf._comment
@@ -0,0 +1,9 @@
+[[!comment format=mdwn
+ username="diogo"
+ avatar="http://cdn.libravatar.org/avatar/b829c41f02e974268e52bd6ca828b088"
+ subject="Happy birthday!"
+ date="2020-04-12T07:49:12Z"
+ content="""
+Happy birthday, Joey!
+Feliz aniversário, Joey!
+"""]]

removed
diff --git a/blog/entry/lemons/comment_4_7d0d69de1f68c74c68fc51445e9077b2._comment b/blog/entry/lemons/comment_4_7d0d69de1f68c74c68fc51445e9077b2._comment
deleted file mode 100644
index 039e356d..00000000
--- a/blog/entry/lemons/comment_4_7d0d69de1f68c74c68fc51445e9077b2._comment
+++ /dev/null
@@ -1,9 +0,0 @@
-[[!comment format=mdwn
- username="amacater@8dbb5176e3195fd87756930de08ffc5d96244756"
- nickname="amacater"
- avatar="http://cdn.libravatar.org/avatar/886d76ddcb7edd77095c829efc964ee6"
- subject="Happy birthday Joeh"
- date="2020-04-11T23:09:20Z"
- content="""
-Happy birthday and all the best. The lemon meringue pie looks good too
-"""]]

Added a comment: Happy birthday Joey
diff --git a/blog/entry/lemons/comment_5_7d701b10b2b863f0a5ac24485c6f4766._comment b/blog/entry/lemons/comment_5_7d701b10b2b863f0a5ac24485c6f4766._comment
new file mode 100644
index 00000000..037daaa2
--- /dev/null
+++ b/blog/entry/lemons/comment_5_7d701b10b2b863f0a5ac24485c6f4766._comment
@@ -0,0 +1,9 @@
+[[!comment format=mdwn
+ username="amacater@8dbb5176e3195fd87756930de08ffc5d96244756"
+ nickname="amacater"
+ avatar="http://cdn.libravatar.org/avatar/886d76ddcb7edd77095c829efc964ee6"
+ subject="Happy birthday Joey"
+ date="2020-04-11T23:11:20Z"
+ content="""
+Happy birthday / Penblwydd hapus i ti :) Lemon meringue pie looks good too.
+"""]]

Added a comment: Happy birthday Joeh
diff --git a/blog/entry/lemons/comment_4_7d0d69de1f68c74c68fc51445e9077b2._comment b/blog/entry/lemons/comment_4_7d0d69de1f68c74c68fc51445e9077b2._comment
new file mode 100644
index 00000000..039e356d
--- /dev/null
+++ b/blog/entry/lemons/comment_4_7d0d69de1f68c74c68fc51445e9077b2._comment
@@ -0,0 +1,9 @@
+[[!comment format=mdwn
+ username="amacater@8dbb5176e3195fd87756930de08ffc5d96244756"
+ nickname="amacater"
+ avatar="http://cdn.libravatar.org/avatar/886d76ddcb7edd77095c829efc964ee6"
+ subject="Happy birthday Joeh"
+ date="2020-04-11T23:09:20Z"
+ content="""
+Happy birthday and all the best. The lemon meringue pie looks good too
+"""]]

Added a comment: by the way
diff --git a/blog/entry/lemons/comment_3_a89d9517428d266bbdc12c086524c8d2._comment b/blog/entry/lemons/comment_3_a89d9517428d266bbdc12c086524c8d2._comment
new file mode 100644
index 00000000..dc9f48ed
--- /dev/null
+++ b/blog/entry/lemons/comment_3_a89d9517428d266bbdc12c086524c8d2._comment
@@ -0,0 +1,9 @@
+[[!comment format=mdwn
+ username="maggiemargarethess@78015320cd96dc052b86f45ba7a77ac2c0aaa5a7"
+ nickname="maggiemargarethess"
+ avatar="http://cdn.libravatar.org/avatar/61b9ea3a9064e12dbcc6ed88724c1640"
+ subject="by the way"
+ date="2020-04-11T20:46:42Z"
+ content="""
+It looks gourmet.  
+"""]]

Added a comment: Correction
diff --git a/blog/entry/lemons/comment_2_3e112328177a1d52faf3d8764e521022._comment b/blog/entry/lemons/comment_2_3e112328177a1d52faf3d8764e521022._comment
new file mode 100644
index 00000000..f1086ae4
--- /dev/null
+++ b/blog/entry/lemons/comment_2_3e112328177a1d52faf3d8764e521022._comment
@@ -0,0 +1,11 @@
+[[!comment format=mdwn
+ username="maggiemargarethess@78015320cd96dc052b86f45ba7a77ac2c0aaa5a7"
+ nickname="maggiemargarethess"
+ avatar="http://cdn.libravatar.org/avatar/61b9ea3a9064e12dbcc6ed88724c1640"
+ subject="Correction"
+ date="2020-04-11T20:46:16Z"
+ content="""
+Mom brings it.  I make it.  
+
+little sis
+"""]]

Added a comment: Pie
diff --git a/blog/entry/lemons/comment_1_c3eadc3c8cf4e2fe4478f90a77e3997e._comment b/blog/entry/lemons/comment_1_c3eadc3c8cf4e2fe4478f90a77e3997e._comment
new file mode 100644
index 00000000..c20c33a8
--- /dev/null
+++ b/blog/entry/lemons/comment_1_c3eadc3c8cf4e2fe4478f90a77e3997e._comment
@@ -0,0 +1,14 @@
+[[!comment format=mdwn
+ username="errol@4c351216735f25963d33c6356c048fda8ce68cb1"
+ nickname="errol"
+ avatar="http://cdn.libravatar.org/avatar/ef35c62161fcba23b7ee6636efbd1569"
+ subject="Pie"
+ date="2020-04-11T20:20:14Z"
+ content="""
+
+
+
+
+
+you could mail me a piece.
+"""]]

blog update
diff --git a/blog/entry/lemons.mdwn b/blog/entry/lemons.mdwn
new file mode 100644
index 00000000..90e3eb8a
--- /dev/null
+++ b/blog/entry/lemons.mdwn
@@ -0,0 +1,31 @@
+Lemon is one of my things. I homegrow meyer lemons and mostly eat them
+whole. My mom makes me lemon meringue pie on my birthday. I thought
+I knew how much work that must be.
+
+[[!img pics/lemonmeringuepie.jpg alt="Gorgeous whole lemon-meringue pie"
+size=900x]]
+
+Well, that was harder than anticipated, and so worth it. Glad my mom was
+there on jitsi to give moral support while I hand whisked the egg whites
+and cursed.
+
+I also got a homemade mask whose [quarantimer](https://quarantimer.app/)
+expired just in time.
+
+But all I really want want for my birthday, this April 11th 2020, is for
+the coronavirus to have peaked today. I mean, having a pandemic peak on your
+birthday is sour, but it's better than the alternative.
+
+Please give me that gift. Stay home. Even when some are saying
+it's over, watch the graphs. Don't go visit even 
+[just one person](https://statnet.org/COVID-JustOneFriend/),
+even on their birthday. I think you can do it.
+
+Yes?
+
+[[!img pics/maskie.jpg alt="Joey in a rainbow tie-die mask,
+holding a thumb up." size=900x]]
+
+[[!img pics/lemonmeringuepieslice.jpg alt="Lemon-meringue pie slice" 
+size=900x]]
+

add
diff --git a/blog/pics/lemonmeringuepie.jpg b/blog/pics/lemonmeringuepie.jpg
new file mode 100644
index 00000000..37500f1d
Binary files /dev/null and b/blog/pics/lemonmeringuepie.jpg differ
diff --git a/blog/pics/lemonmeringuepieslice.jpg b/blog/pics/lemonmeringuepieslice.jpg
new file mode 100644
index 00000000..c0061e1e
Binary files /dev/null and b/blog/pics/lemonmeringuepieslice.jpg differ

add
diff --git a/blog/pics/maskie.jpg b/blog/pics/maskie.jpg
new file mode 100644
index 00000000..515af84a
Binary files /dev/null and b/blog/pics/maskie.jpg differ

hmm
diff --git a/blog/entry/solar_powered_waterfall.mdwn b/blog/entry/solar_powered_waterfall.mdwn
index d4090468..d3aba4c4 100644
--- a/blog/entry/solar_powered_waterfall.mdwn
+++ b/blog/entry/solar_powered_waterfall.mdwn
@@ -3,7 +3,7 @@
 This waterfall is beside my yard. When it's running, I know my
 [[water tanks|hacking_water]] are full and the spring is not dry.
 
-<video controls src="https://downloads.kitenet.net/videos/solar_waterfall.mp4"></video>
+<video controls src="https://downloads.kitenet.net/videos/solar_waterfall.mp4" width=100%></video>
 
 Also it's computer controlled, for times when I don't want to hear it.
 I'll also use the computer control later on to avoid running the pump

reorg
diff --git a/blog/entry/solar_powered_waterfall.mdwn b/blog/entry/solar_powered_waterfall.mdwn
index 6fff9b2f..d4090468 100644
--- a/blog/entry/solar_powered_waterfall.mdwn
+++ b/blog/entry/solar_powered_waterfall.mdwn
@@ -1,10 +1,10 @@
 [[!meta title="solar powered waterfall controlled by a GPIO port"]]
 
-<video controls src="https://downloads.kitenet.net/videos/solar_waterfall.mp4"></video>
-
 This waterfall is beside my yard. When it's running, I know my
 [[water tanks|hacking_water]] are full and the spring is not dry.
 
+<video controls src="https://downloads.kitenet.net/videos/solar_waterfall.mp4"></video>
+
 Also it's computer controlled, for times when I don't want to hear it.
 I'll also use the computer control later on to avoid running the pump
 excessively and wearing it out, and for some safety features like not

oop
diff --git a/blog/entry/solar_powered_waterfall.mdwn b/blog/entry/solar_powered_waterfall.mdwn
index 98a30281..6fff9b2f 100644
--- a/blog/entry/solar_powered_waterfall.mdwn
+++ b/blog/entry/solar_powered_waterfall.mdwn
@@ -1,6 +1,6 @@
 [[!meta title="solar powered waterfall controlled by a GPIO port"]]
 
-<video controls src=""https://downloads.kitenet.net/videos/solar_waterfall.mp4></video>
+<video controls src="https://downloads.kitenet.net/videos/solar_waterfall.mp4"></video>
 
 This waterfall is beside my yard. When it's running, I know my
 [[water tanks|hacking_water]] are full and the spring is not dry.

blog update
diff --git a/blog/entry/solar_powered_waterfall.mdwn b/blog/entry/solar_powered_waterfall.mdwn
new file mode 100644
index 00000000..98a30281
--- /dev/null
+++ b/blog/entry/solar_powered_waterfall.mdwn
@@ -0,0 +1,26 @@
+[[!meta title="solar powered waterfall controlled by a GPIO port"]]
+
+<video controls src=""https://downloads.kitenet.net/videos/solar_waterfall.mp4></video>
+
+This waterfall is beside my yard. When it's running, I know my
+[[water tanks|hacking_water]] are full and the spring is not dry.
+
+Also it's computer controlled, for times when I don't want to hear it.
+I'll also use the computer control later on to avoid running the pump
+excessively and wearing it out, and for some safety features like not
+running when the water is frozen.
+
+This is a whole hillside of pipes, water tanks, pumps, solar panels,
+all controlled by a GPIO port. Easy enough; the pump controller has a float
+switch input and the GPIO drives a 4n35 optoisolator to open or close that
+circuit. Hard part will be burying all the cable to the pump. And then all
+the landscaping around the waterfall.
+
+There's a bit of lag to turning it on and off. It can take over an hour for
+it to start flowing, and around half an hour to stop. The water level has
+to get high enough in the water tanks to overcome some airlocks and
+complicated hydrodynamic flow stuff. Then when it stops, all that excess
+water has to drain back down.
+
+Anyway, enjoy my soothing afternoon project and/or massive rube goldberg
+machine, I certainly am.
diff --git a/offgrid/water.mdwn b/offgrid/water.mdwn
index 5516935b..c2b271d3 100644
--- a/offgrid/water.mdwn
+++ b/offgrid/water.mdwn
@@ -27,3 +27,5 @@ The system works great, I have 30 PSI now, and sufficient storage to easily
 get through the fall dry season.
 
 For more see [[blog/entry/hacking_water]].
+
+Also the overflow goes to [[blog/entry/solar_powered_waterfall]].

response
diff --git a/blog/entry/quarantimer/comment_2_020ce05418c028437818ff965ac1fe88._comment b/blog/entry/quarantimer/comment_2_020ce05418c028437818ff965ac1fe88._comment
new file mode 100644
index 00000000..4fe22ac2
--- /dev/null
+++ b/blog/entry/quarantimer/comment_2_020ce05418c028437818ff965ac1fe88._comment
@@ -0,0 +1,7 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 2"""
+ date="2020-04-03T22:17:50Z"
+ content="""
+Thanks, it's good to know.
+"""]]

response
diff --git a/blog/entry/usb_drives_with_no_phantom_load/comment_18_8bcce33cb27a9dc1cf912a31af19c202._comment b/blog/entry/usb_drives_with_no_phantom_load/comment_18_8bcce33cb27a9dc1cf912a31af19c202._comment
new file mode 100644
index 00000000..81e6659e
--- /dev/null
+++ b/blog/entry/usb_drives_with_no_phantom_load/comment_18_8bcce33cb27a9dc1cf912a31af19c202._comment
@@ -0,0 +1,10 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 18"""
+ date="2020-04-03T22:16:02Z"
+ content="""
+Startech ST4200USBM.
+
+But uhubctl's home page has a good list of all known usable hubs, many much
+cheaper.
+"""]]

Added a comment
diff --git a/blog/entry/quarantimer/comment_1_b6d902d668c3ae7e694420e35684adf9._comment b/blog/entry/quarantimer/comment_1_b6d902d668c3ae7e694420e35684adf9._comment
new file mode 100644
index 00000000..8aedae63
--- /dev/null
+++ b/blog/entry/quarantimer/comment_1_b6d902d668c3ae7e694420e35684adf9._comment
@@ -0,0 +1,9 @@
+[[!comment format=mdwn
+ username="jon+joeyh@0ca6720a1d6c4435ce5a38a0be3c151864be033a"
+ nickname="jon+joeyh"
+ avatar="http://cdn.libravatar.org/avatar/10bbf766427526558b9a09a3e77e5d14"
+ subject="comment 1"
+ date="2020-04-03T09:56:05Z"
+ content="""
+This is really useful, thank you for building it. I've been using it myself and recommending it to others.
+"""]]

Added a comment
diff --git a/blog/entry/usb_drives_with_no_phantom_load/comment_17_9896acdd60597cbd7d3927f90cebdcd9._comment b/blog/entry/usb_drives_with_no_phantom_load/comment_17_9896acdd60597cbd7d3927f90cebdcd9._comment
new file mode 100644
index 00000000..646a6e96
--- /dev/null
+++ b/blog/entry/usb_drives_with_no_phantom_load/comment_17_9896acdd60597cbd7d3927f90cebdcd9._comment
@@ -0,0 +1,9 @@
+[[!comment format=mdwn
+ username="gfa@1e86118cd41fbfea50004af221471ad97b55af18"
+ nickname="gfa"
+ avatar="http://cdn.libravatar.org/avatar/4678da4da55c67fa668e31ea0a76b201"
+ subject="comment 17"
+ date="2020-04-03T06:46:03Z"
+ content="""
+What USB hub are you using? cheers
+"""]]

post
diff --git a/blog/entry/DIN.mdwn b/blog/entry/DIN.mdwn
index 668bba28..07be0f38 100644
--- a/blog/entry/DIN.mdwn
+++ b/blog/entry/DIN.mdwn
@@ -2,7 +2,8 @@
 
 My offgrid house has an industrial automation panel.
 
-[[!img pics/DIN/dinrail.jpg alt="A row of electrical devices, mounted on a
+[[!img pics/DIN/dinrail.jpg size=800x
+alt="A row of electrical devices, mounted on a
 metal rail. Many wires neatly extend from it above and below,
 disappearing into wire gutters."]]
 
@@ -23,11 +24,11 @@ stuff, and perhaps you could use a distraction too.
 The panel has my house's computer on it, as well as both AC and DC power
 distribution, breakers, and switching. Since the house is offgrid, the panel
 is designed to let every non-essential power drain be turned off, from
-my [[offgrid_fridge|fridge]] to the 20 terabytes of
+my [[offgrid_fridge|fridge_0.1]] to the 20 terabytes of
 [[offline_storage|usb_drives_with_no_phantom_load]] to the
 [[inverter|AIMS_inverter_control_via_GPIO_ports]] and satellite dish,
 the spring pump for my [[gravity_flow_water_system|hacking_water]], and
-even the outlet by the kitchen sink.
+even the power outlet by the kitchen sink.
 
 Saving power is part of why I'm using old-school relays and stuff and not
 IOT devices, the other reason is of course: IOT devices are horrible
@@ -62,12 +63,12 @@ clipped into place and it evolves for changing needs.
 
 Also, wire gutters, where have you been all my life?
 
-[[!img pics/DIN/gearwall.jpg size=500x 
-alt="A small utility room with an entire wall
+[[!img pics/DIN/gearwall.jpg size=600x 
+alt="A cramped utility room with an entire wall
 covered with electronic gear, including the DIN rail, which is surrounded by
 wire gutters"]]
-[[!img pics/DIN/wiregutter.jpg size=500x 
-alt="A wire gutter with the cover removed.
+[[!img pics/DIN/wiregutter.jpg size=300x 
+alt="Detail of a wire gutter with the cover removed.
 Numerous large and small wires run along it and exit here and there."]]
 
 Finally, if you'd like to know what everything on the DIN rail is, from
@@ -76,6 +77,4 @@ hub switch, computer switch, +24v block, -24v block, IO daughterboard, 1tb
 SSD, arm board, modem, 3 USB hubs, 5 relays, AC hot block, AC neutral
 block, DC-DC power converters, humidity sensor.
 
-[[!img pics/DIN/dinrailleft.jpg alt="DIN rail as described above, left side."]]
-[[!img pics/DIN/dinrailright.jpg alt="DIN rail as described above, right side."]]
-
+[[!img pics/DIN/dinrailfull.jpg size=900x alt="Full width of DIN rail."]]

add
diff --git a/blog/pics/DIN/dinrailfull.jpg b/blog/pics/DIN/dinrailfull.jpg
new file mode 100644
index 00000000..7e8954b6
Binary files /dev/null and b/blog/pics/DIN/dinrailfull.jpg differ

add
diff --git a/blog/pics/DIN/gearwall.jpg b/blog/pics/DIN/gearwall.jpg
new file mode 100644
index 00000000..d7c0e0cd
Binary files /dev/null and b/blog/pics/DIN/gearwall.jpg differ

add
diff --git a/blog/pics/DIN/dinrail.jpg b/blog/pics/DIN/dinrail.jpg
new file mode 100644
index 00000000..1c459569
Binary files /dev/null and b/blog/pics/DIN/dinrail.jpg differ

add
diff --git a/blog/entry/DIN.mdwn b/blog/entry/DIN.mdwn
index 0ab512d2..668bba28 100644
--- a/blog/entry/DIN.mdwn
+++ b/blog/entry/DIN.mdwn
@@ -1,20 +1,24 @@
+[[!meta title="DIN distractions"]]
+
 My offgrid house has an industrial automation panel.
 
-[[!img DIN/dinrail.jpg alt="A row of electrical devices, mounted on a
+[[!img pics/DIN/dinrail.jpg alt="A row of electrical devices, mounted on a
 metal rail. Many wires neatly extend from it above and below,
 disappearing into wire gutters."]]
 
 I started building this in February, before covid-19 was impacting us here,
-when lots of digikey orders were no big problem, and getting an unusual
+when lots of mail orders were no big problem, and getting an unusual
 3D-printed DIN rail bracket for a SSD was just a couple clicks.
 
-I finished a month deep into social isolation and quarentine, scrounging
-around the house for scrap wire, scavenging screws from unused stuff and
-cutting them to size, and hoping I would not end up in a "need just one
-more part" situation.
+I finished a month later, deep into social isolation and quarentine,
+scrounging around the house for scrap wire, scavenging screws from unused
+stuff and cutting them to size, and hoping I would not end up in a "need
+just one more part that I can't get" situation.
 
 It got rather elaborate, and working on it was often a welcome distraction
-from the news when I couldn't concentrate on my usual work.
+from the news when I couldn't concentrate on my usual work. I'm posting
+this now because people sometimes tell me they like hearing about my offfgrid
+stuff, and perhaps you could use a distraction too.
 
 The panel has my house's computer on it, as well as both AC and DC power
 distribution, breakers, and switching. Since the house is offgrid, the panel
@@ -25,30 +29,46 @@ my [[offgrid_fridge|fridge]] to the 20 terabytes of
 the spring pump for my [[gravity_flow_water_system|hacking_water]], and
 even the outlet by the kitchen sink.
 
-(Saving power is part of why I'm using old-school relays and stuff and not
-IOT devices, the other reason is of course: IOT devices are horrible.)
+Saving power is part of why I'm using old-school relays and stuff and not
+IOT devices, the other reason is of course: IOT devices are horrible
+dystopian e-waste. I'm taking the utopian Star Trek approach, where I
+can command "full power to the vacuum cleaner!"
 
-[[!img DIN/daughterboard.jpg alt="Two circuit boards, connected by numerous
+[[!img pics/DIN/daughterboard.jpg size=300x
+alt="Two circuit boards, connected by numerous
 ribbon cables, and clearly hand-soldered. The smaller board is suspended
 above the larger."]]
-[[!img DIN/schematic.jpg alt="An electrical schematic, of moderate complexity."]]
+[[!img pics/DIN/schematic.jpg size=600x alt="An electrical schematic, of moderate complexity."]]
 
 At the core of the panel, next to the cubietruck arm board, is a custom
 IO daughterboard. Designed and built by hand to fit into a DIN mount case,
 it uses every GPIO pin on the cubietruck's main GPIO header. Making
-this board was about half the project. It got pretty tight in there.
+this board took 40+ hours, and was about half the project. It got
+pretty tight in there.
+
+This was my first foray into DIN rail mount, and it really is industrial
+lego -- a whole universe of parts that all fit together and are immensely
+flexible. Often priced more than seems reasonable for a little bit of
+plastic and metal, until you look at the spec sheets and the ratings.
+(Total cost for my panel was $400.) It's odd that it's not more used
+outside its niche -- I came of age in the Bay Area, surrounded by rack
+mount equipment, but no DIN mount equipment. Hacking the hardware in
+a rack is unusual, but DIN *invites* hacking.
 
-This was my first forway into DIN rail mount, and it really is industrial
-lego -- a whole universe of parts that all fit together. This is a second
-system kind of project, replacing some unsightly shelves full of gear
-with something kind of overdone. But should be worth it in the long run
-as new gear gets clipped into place.
+Admittedly, this is a second system kind of project, replacing some
+unsightly shelves full of gear and wires everywhere with something kind
+of overdone. But should be worth it in the long run as new gear gets
+clipped into place and it evolves for changing needs.
 
 Also, wire gutters, where have you been all my life?
 
-[[!img DIN/gearwall.jpg alt="A small utility room with an entire wall
+[[!img pics/DIN/gearwall.jpg size=500x 
+alt="A small utility room with an entire wall
 covered with electronic gear, including the DIN rail, which is surrounded by
 wire gutters"]]
+[[!img pics/DIN/wiregutter.jpg size=500x 
+alt="A wire gutter with the cover removed.
+Numerous large and small wires run along it and exit here and there."]]
 
 Finally, if you'd like to know what everything on the DIN rail is, from
 left to right: Ground block, 24v DC disconnect, fridge GFI, spare GFI, USB
@@ -56,5 +76,6 @@ hub switch, computer switch, +24v block, -24v block, IO daughterboard, 1tb
 SSD, arm board, modem, 3 USB hubs, 5 relays, AC hot block, AC neutral
 block, DC-DC power converters, humidity sensor.
 
-[[!img DIN/dinrailleft.jpg alt="DIN rail as described above, left side."]]
-[[!img DIN/dinrailright.jpg alt="DIN rail as described above, right side."]]
+[[!img pics/DIN/dinrailleft.jpg alt="DIN rail as described above, left side."]]
+[[!img pics/DIN/dinrailright.jpg alt="DIN rail as described above, right side."]]
+
diff --git a/blog/pics/DIN/wiregutter.jpg b/blog/pics/DIN/wiregutter.jpg
new file mode 100644
index 00000000..53d41005
Binary files /dev/null and b/blog/pics/DIN/wiregutter.jpg differ

add
diff --git a/blog/entry/DIN.mdwn b/blog/entry/DIN.mdwn
new file mode 100644
index 00000000..0ab512d2
--- /dev/null
+++ b/blog/entry/DIN.mdwn
@@ -0,0 +1,60 @@
+My offgrid house has an industrial automation panel.
+
+[[!img DIN/dinrail.jpg alt="A row of electrical devices, mounted on a
+metal rail. Many wires neatly extend from it above and below,
+disappearing into wire gutters."]]
+
+I started building this in February, before covid-19 was impacting us here,
+when lots of digikey orders were no big problem, and getting an unusual
+3D-printed DIN rail bracket for a SSD was just a couple clicks.
+
+I finished a month deep into social isolation and quarentine, scrounging
+around the house for scrap wire, scavenging screws from unused stuff and
+cutting them to size, and hoping I would not end up in a "need just one
+more part" situation.
+
+It got rather elaborate, and working on it was often a welcome distraction
+from the news when I couldn't concentrate on my usual work.
+
+The panel has my house's computer on it, as well as both AC and DC power
+distribution, breakers, and switching. Since the house is offgrid, the panel
+is designed to let every non-essential power drain be turned off, from
+my [[offgrid_fridge|fridge]] to the 20 terabytes of
+[[offline_storage|usb_drives_with_no_phantom_load]] to the
+[[inverter|AIMS_inverter_control_via_GPIO_ports]] and satellite dish,
+the spring pump for my [[gravity_flow_water_system|hacking_water]], and
+even the outlet by the kitchen sink.
+
+(Saving power is part of why I'm using old-school relays and stuff and not
+IOT devices, the other reason is of course: IOT devices are horrible.)
+
+[[!img DIN/daughterboard.jpg alt="Two circuit boards, connected by numerous
+ribbon cables, and clearly hand-soldered. The smaller board is suspended
+above the larger."]]
+[[!img DIN/schematic.jpg alt="An electrical schematic, of moderate complexity."]]
+
+At the core of the panel, next to the cubietruck arm board, is a custom
+IO daughterboard. Designed and built by hand to fit into a DIN mount case,
+it uses every GPIO pin on the cubietruck's main GPIO header. Making
+this board was about half the project. It got pretty tight in there.
+
+This was my first forway into DIN rail mount, and it really is industrial
+lego -- a whole universe of parts that all fit together. This is a second
+system kind of project, replacing some unsightly shelves full of gear
+with something kind of overdone. But should be worth it in the long run
+as new gear gets clipped into place.
+
+Also, wire gutters, where have you been all my life?
+
+[[!img DIN/gearwall.jpg alt="A small utility room with an entire wall
+covered with electronic gear, including the DIN rail, which is surrounded by
+wire gutters"]]
+
+Finally, if you'd like to know what everything on the DIN rail is, from
+left to right: Ground block, 24v DC disconnect, fridge GFI, spare GFI, USB
+hub switch, computer switch, +24v block, -24v block, IO daughterboard, 1tb
+SSD, arm board, modem, 3 USB hubs, 5 relays, AC hot block, AC neutral
+block, DC-DC power converters, humidity sensor.
+
+[[!img DIN/dinrailleft.jpg alt="DIN rail as described above, left side."]]
+[[!img DIN/dinrailright.jpg alt="DIN rail as described above, right side."]]
diff --git a/blog/pics/DIN/daughterboard.jpg b/blog/pics/DIN/daughterboard.jpg
new file mode 100644
index 00000000..2444bfb1
Binary files /dev/null and b/blog/pics/DIN/daughterboard.jpg differ
diff --git a/blog/pics/DIN/schematic.jpg b/blog/pics/DIN/schematic.jpg
new file mode 100644
index 00000000..b9573d73
Binary files /dev/null and b/blog/pics/DIN/schematic.jpg differ

Request to add a --editor flag to vidir and make it understand file URIs
diff --git a/code/moreutils/discussion.mdwn b/code/moreutils/discussion.mdwn
index f6e621d6..f11410e3 100644
--- a/code/moreutils/discussion.mdwn
+++ b/code/moreutils/discussion.mdwn
@@ -274,6 +274,19 @@ It computes the number of days between two dates and can check whether a date ex
 
 ## vidir
 
+I hope this is the right place to make any propositions.
+Vidir is the, by far, most powerfull mass renaming tool I am aware of, but unfortunately it is limited to terminal use only.
+However, sometimes I want to do mass renaming from a graphical file browser, atm this is possible by opening the current folder in terminal and typing vidir.
+Many file browsers (e.g. nemo, nautilus, thunar) allow you to specify a command for mass renaming purposes which brings me to the following two limitations:
+
+* In most of these file-browsers the file names are given as URIs which vidir doesn't seem to understand
+
+* My EDITOR variable is, of course, set to vim therefore, it doesn't work from a graphical context.
+  It would be nice if vidir would understand a command line flag like --editor where one could set an editor (e.g. gvim) only for the current session
+
+-- Mani
+
+
 A suggestion regarding vidir:
 I would find it quite useful if vidir could work with version control system commands like:
 

Added a comment: Excited to try git-annex
diff --git a/blog/entry/how_I_maybe_didnt_burn_out/comment_6_cd08526d09c26cd14d984c06b9d0e21a._comment b/blog/entry/how_I_maybe_didnt_burn_out/comment_6_cd08526d09c26cd14d984c06b9d0e21a._comment
new file mode 100644
index 00000000..220a2245
--- /dev/null
+++ b/blog/entry/how_I_maybe_didnt_burn_out/comment_6_cd08526d09c26cd14d984c06b9d0e21a._comment
@@ -0,0 +1,10 @@
+[[!comment format=mdwn
+ username="pannekoek"
+ avatar="http://cdn.libravatar.org/avatar/676a7c403af0627c9bde84ee1ab3975c"
+ subject="Excited to try git-annex"
+ date="2020-03-27T18:19:11Z"
+ content="""
+git-annex seems really cool! I'm one of those users who has large repository of source files I want to track with \"vanilla git\" and one subdirectory of very large files I want to manage with git-annex. Pardon me if this is mention elsewhere, but how can I set up git annex v7 to only annex files I explicitly \"git annex add\" and otherwise leave \"git add\" unchanged?
+
+Thanks for all of your hard work. Your many projects and experiments in off-grid living are an inspiration.
+"""]]

add
diff --git a/blog/entry/quarantimer.mdwn b/blog/entry/quarantimer.mdwn
new file mode 100644
index 00000000..8c15cac3
--- /dev/null
+++ b/blog/entry/quarantimer.mdwn
@@ -0,0 +1,34 @@
+[[!meta title="quarantimer: a coronovirus quarantine timer for your things"]]
+
+I am trying to avoid bringing coronovirus into my house on anything,
+and I also don't want to sterilize a lot of stuff. (Tedious and easy to
+make a mistake.) Currently it seems that the best approach is to leave
+stuff to sit undisturbed someplace safe for long enough for the virus to
+degrade away.
+
+Following that policy, I've quickly ended up with a porch full of stuff
+in different stages of quarantine, and I am quickly losing track of how
+long things have been in quarantine. If you have the same problem,
+here is a solution:
+
+<https://quarantimer.app/>
+
+Open it on your mobile device, and you can take photos of each thing,
+select the kind of surfaces it has, and it will track the quarantine time
+for you. You can share the link to other devices or other people to
+collaborate.
+
+[[!img code/quarantimer/screenshot.png]]
+
+I anticipate the javascript and css will improve, but it's good enough for
+now. I will provide this website until the crisis is over. Of course,
+it's free software and you can also host your own.
+
+If this seems useful, please tell your friends and family about it.
+
+Be well!
+
+----
+
+This is made possible by my supporters on
+[Patreon](https://patreon.com/joeyh/), particularly Jake Vosloo.

add
diff --git a/code.mdwn b/code.mdwn
index 9f54f1a2..ab93e7c5 100644
--- a/code.mdwn
+++ b/code.mdwn
@@ -22,6 +22,7 @@ The stuff that's swapped into my local cache at the moment.
 [[haskell-filepath-bytestring]]
 [[arduino-copilot]]
 [[virtual-hallway-track]]
+[[quarantimer]]
 
 ## Less active projects
 

add
diff --git a/code/quarantimer.mdwn b/code/quarantimer.mdwn
new file mode 100644
index 00000000..a0b9cdd8
--- /dev/null
+++ b/code/quarantimer.mdwn
@@ -0,0 +1,5 @@
+Coronavirus quarantine timer
+
+<https://quarantimer.app/>
+
+[[!img code/quarantimer/screenshot.png]]
diff --git a/code/quarantimer/screenshot.png b/code/quarantimer/screenshot.png
new file mode 100644
index 00000000..16b34d63
Binary files /dev/null and b/code/quarantimer/screenshot.png differ

screenshot
diff --git a/code/virtual-hallway-track.mdwn b/code/virtual-hallway-track.mdwn
index 80a17b16..4d82e05b 100644
--- a/code/virtual-hallway-track.mdwn
+++ b/code/virtual-hallway-track.mdwn
@@ -9,5 +9,6 @@ and has only been used in conjunction with one conference so far.
 
 [[!img screenshot.png size=640x]]
 
-
 [[!img screenshot2.png size=640x]]
+
+[[!img screenshot3.png size=640x]]
diff --git a/code/virtual-hallway-track/screenshot3.png b/code/virtual-hallway-track/screenshot3.png
new file mode 100644
index 00000000..3022e186
Binary files /dev/null and b/code/virtual-hallway-track/screenshot3.png differ

screenshot
diff --git a/code/virtual-hallway-track.mdwn b/code/virtual-hallway-track.mdwn
index bf4019f6..80a17b16 100644
--- a/code/virtual-hallway-track.mdwn
+++ b/code/virtual-hallway-track.mdwn
@@ -8,3 +8,6 @@ and has only been used in conjunction with one conference so far.
 <https://git.joeyh.name/index.cgi/virtual-hallway-track.git/>
 
 [[!img screenshot.png size=640x]]
+
+
+[[!img screenshot2.png size=640x]]
diff --git a/code/virtual-hallway-track/screenshot2.png b/code/virtual-hallway-track/screenshot2.png
new file mode 100644
index 00000000..82b5e4cc
Binary files /dev/null and b/code/virtual-hallway-track/screenshot2.png differ

scale
diff --git a/code/virtual-hallway-track.mdwn b/code/virtual-hallway-track.mdwn
index ea5c909e..bf4019f6 100644
--- a/code/virtual-hallway-track.mdwn
+++ b/code/virtual-hallway-track.mdwn
@@ -7,4 +7,4 @@ and has only been used in conjunction with one conference so far.
 
 <https://git.joeyh.name/index.cgi/virtual-hallway-track.git/>
 
-[[!img screenshot.png]]
+[[!img screenshot.png size=640x]]

Revert "scale"
This reverts commit 48d2182e6316a24dd7c57822d064070445f0ada3.
diff --git a/code/virtual-hallway-track/screenshot.png b/code/virtual-hallway-track/screenshot.png
index 5f663fda..751629bf 100644
Binary files a/code/virtual-hallway-track/screenshot.png and b/code/virtual-hallway-track/screenshot.png differ

scale
diff --git a/code/virtual-hallway-track/screenshot.png b/code/virtual-hallway-track/screenshot.png
index 751629bf..5f663fda 100644
Binary files a/code/virtual-hallway-track/screenshot.png and b/code/virtual-hallway-track/screenshot.png differ

update
diff --git a/offgrid/water.mdwn b/offgrid/water.mdwn
index 88c203a4..5516935b 100644
--- a/offgrid/water.mdwn
+++ b/offgrid/water.mdwn
@@ -8,8 +8,8 @@ the only way to get water pressure was a pump with a pressure tank. I did
 not like this system, which barely worked, was noisy every time the water
 ran, and once leaked all over the living room.
 
-I found a flat spot around 50 feet higher than the house, and have added a
-water tank there (currently a 50 gallon temporary drum). 
+I found a flat spot around 50 feet higher than the house, and installed
+two 550 gallon water tanks.
 
 Repurposing an old, small set of solar panels, and a Shurflow pump with a
 linear voltage regulator, I found it was able to pump water up there from
@@ -17,11 +17,13 @@ the cistern.
 
 The cistern was cleaned out, re-sealed and water level sensors installed,
 so it will slowly fill up from the spring and then the pump will periodically
-pump 100 gallons of water out of it.
+pump out of it.
 
 I hand buried around 300 feet of PEX pipe, 12 inches deep, to connect the
 water tank to the house, using a tool called a "whomper" which was easier
 than digging a trench by hand and refilling.
 
-The system works great, I have 30 PSI now and only need more water storage
-on the hill to complete it.
+The system works great, I have 30 PSI now, and sufficient storage to easily
+get through the fall dry season.
+
+For more see [[blog/entry/hacking_water]].

update
diff --git a/code/virtual-hallway-track.mdwn b/code/virtual-hallway-track.mdwn
index c313c3a4..ea5c909e 100644
--- a/code/virtual-hallway-track.mdwn
+++ b/code/virtual-hallway-track.mdwn
@@ -1,9 +1,10 @@
 The best part of a good conference is its hallway track,
-with conversations in small, shifting groups.
+with conversations in small groups that grow and split, and the chance to
+look around, find your friends and see what they're enthused about.
 
 This program tries to emulate that in a virtual space. It's experimental
 and has only been used in conjunction with one conference so far.
 
-[[!img screenshot.png]]
-
 <https://git.joeyh.name/index.cgi/virtual-hallway-track.git/>
+
+[[!img screenshot.png]]

vht
diff --git a/code.mdwn b/code.mdwn
index 38766cb0..9f54f1a2 100644
--- a/code.mdwn
+++ b/code.mdwn
@@ -21,6 +21,7 @@ The stuff that's swapped into my local cache at the moment.
 [[fridge0]]
 [[haskell-filepath-bytestring]]
 [[arduino-copilot]]
+[[virtual-hallway-track]]
 
 ## Less active projects
 
diff --git a/code/virtual-hallway-track.mdwn b/code/virtual-hallway-track.mdwn
new file mode 100644
index 00000000..c313c3a4
--- /dev/null
+++ b/code/virtual-hallway-track.mdwn
@@ -0,0 +1,9 @@
+The best part of a good conference is its hallway track,
+with conversations in small, shifting groups.
+
+This program tries to emulate that in a virtual space. It's experimental
+and has only been used in conjunction with one conference so far.
+
+[[!img screenshot.png]]
+
+<https://git.joeyh.name/index.cgi/virtual-hallway-track.git/>
diff --git a/code/virtual-hallway-track/screenshot.png b/code/virtual-hallway-track/screenshot.png
new file mode 100644
index 00000000..751629bf
Binary files /dev/null and b/code/virtual-hallway-track/screenshot.png differ

poll vote (watched it all, liked it)
diff --git a/blog/entry/watch_me_code_for_half_an_hour.mdwn b/blog/entry/watch_me_code_for_half_an_hour.mdwn
index 61d1ad12..0c8af3a4 100644
--- a/blog/entry/watch_me_code_for_half_an_hour.mdwn
+++ b/blog/entry/watch_me_code_for_half_an_hour.mdwn
@@ -14,7 +14,7 @@ Not shown is the hour I spent the next day changing the "optimize"
 subcommand implemented here into "--auto" options that can be passed to
 [[code/git-annex]]'s get and drop commands.
 
-[[!poll 62 "watched it all, liked it" 9 "watched some, boring" 4 "too long for me" 15 "too haskell for me" 14 "not interested"]]
+[[!poll 63 "watched it all, liked it" 9 "watched some, boring" 4 "too long for me" 15 "too haskell for me" 14 "not interested"]]
 
 [[!meta title="watch me program for half an hour"]]
 [[!tag haskell]]

poll vote (watched it all, liked it)
diff --git a/blog/entry/watch_me_code_for_half_an_hour.mdwn b/blog/entry/watch_me_code_for_half_an_hour.mdwn
index 0d0b7766..61d1ad12 100644
--- a/blog/entry/watch_me_code_for_half_an_hour.mdwn
+++ b/blog/entry/watch_me_code_for_half_an_hour.mdwn
@@ -14,7 +14,7 @@ Not shown is the hour I spent the next day changing the "optimize"
 subcommand implemented here into "--auto" options that can be passed to
 [[code/git-annex]]'s get and drop commands.
 
-[[!poll 61 "watched it all, liked it" 9 "watched some, boring" 4 "too long for me" 15 "too haskell for me" 14 "not interested"]]
+[[!poll 62 "watched it all, liked it" 9 "watched some, boring" 4 "too long for me" 15 "too haskell for me" 14 "not interested"]]
 
 [[!meta title="watch me program for half an hour"]]
 [[!tag haskell]]

poll vote (not interested)
diff --git a/blog/entry/watch_me_code_for_half_an_hour.mdwn b/blog/entry/watch_me_code_for_half_an_hour.mdwn
index 4d025ef3..0d0b7766 100644
--- a/blog/entry/watch_me_code_for_half_an_hour.mdwn
+++ b/blog/entry/watch_me_code_for_half_an_hour.mdwn
@@ -14,7 +14,7 @@ Not shown is the hour I spent the next day changing the "optimize"
 subcommand implemented here into "--auto" options that can be passed to
 [[code/git-annex]]'s get and drop commands.
 
-[[!poll 61 "watched it all, liked it" 9 "watched some, boring" 4 "too long for me" 16 "too haskell for me" 13 "not interested"]]
+[[!poll 61 "watched it all, liked it" 9 "watched some, boring" 4 "too long for me" 15 "too haskell for me" 14 "not interested"]]
 
 [[!meta title="watch me program for half an hour"]]
 [[!tag haskell]]

poll vote (too haskell for me)
diff --git a/blog/entry/watch_me_code_for_half_an_hour.mdwn b/blog/entry/watch_me_code_for_half_an_hour.mdwn
index e0ac7e02..4d025ef3 100644
--- a/blog/entry/watch_me_code_for_half_an_hour.mdwn
+++ b/blog/entry/watch_me_code_for_half_an_hour.mdwn
@@ -14,7 +14,7 @@ Not shown is the hour I spent the next day changing the "optimize"
 subcommand implemented here into "--auto" options that can be passed to
 [[code/git-annex]]'s get and drop commands.
 
-[[!poll 61 "watched it all, liked it" 9 "watched some, boring" 5 "too long for me" 15 "too haskell for me" 13 "not interested"]]
+[[!poll 61 "watched it all, liked it" 9 "watched some, boring" 4 "too long for me" 16 "too haskell for me" 13 "not interested"]]
 
 [[!meta title="watch me program for half an hour"]]
 [[!tag haskell]]

poll vote (too long for me)
diff --git a/blog/entry/watch_me_code_for_half_an_hour.mdwn b/blog/entry/watch_me_code_for_half_an_hour.mdwn
index 9d4b2460..e0ac7e02 100644
--- a/blog/entry/watch_me_code_for_half_an_hour.mdwn
+++ b/blog/entry/watch_me_code_for_half_an_hour.mdwn
@@ -14,7 +14,7 @@ Not shown is the hour I spent the next day changing the "optimize"
 subcommand implemented here into "--auto" options that can be passed to
 [[code/git-annex]]'s get and drop commands.
 
-[[!poll 61 "watched it all, liked it" 10 "watched some, boring" 4 "too long for me" 15 "too haskell for me" 13 "not interested"]]
+[[!poll 61 "watched it all, liked it" 9 "watched some, boring" 5 "too long for me" 15 "too haskell for me" 13 "not interested"]]
 
 [[!meta title="watch me program for half an hour"]]
 [[!tag haskell]]

poll vote (watched some, boring)
diff --git a/blog/entry/watch_me_code_for_half_an_hour.mdwn b/blog/entry/watch_me_code_for_half_an_hour.mdwn
index 873a99f0..9d4b2460 100644
--- a/blog/entry/watch_me_code_for_half_an_hour.mdwn
+++ b/blog/entry/watch_me_code_for_half_an_hour.mdwn
@@ -14,7 +14,7 @@ Not shown is the hour I spent the next day changing the "optimize"
 subcommand implemented here into "--auto" options that can be passed to
 [[code/git-annex]]'s get and drop commands.
 
-[[!poll 62 "watched it all, liked it" 9 "watched some, boring" 4 "too long for me" 15 "too haskell for me" 13 "not interested"]]
+[[!poll 61 "watched it all, liked it" 10 "watched some, boring" 4 "too long for me" 15 "too haskell for me" 13 "not interested"]]
 
 [[!meta title="watch me program for half an hour"]]
 [[!tag haskell]]

poll vote (watched it all, liked it)
diff --git a/blog/entry/watch_me_code_for_half_an_hour.mdwn b/blog/entry/watch_me_code_for_half_an_hour.mdwn
index a897950c..873a99f0 100644
--- a/blog/entry/watch_me_code_for_half_an_hour.mdwn
+++ b/blog/entry/watch_me_code_for_half_an_hour.mdwn
@@ -14,7 +14,7 @@ Not shown is the hour I spent the next day changing the "optimize"
 subcommand implemented here into "--auto" options that can be passed to
 [[code/git-annex]]'s get and drop commands.
 
-[[!poll 61 "watched it all, liked it" 9 "watched some, boring" 4 "too long for me" 15 "too haskell for me" 13 "not interested"]]
+[[!poll 62 "watched it all, liked it" 9 "watched some, boring" 4 "too long for me" 15 "too haskell for me" 13 "not interested"]]
 
 [[!meta title="watch me program for half an hour"]]
 [[!tag haskell]]

poll vote (I don't plan to try it)
diff --git a/code/kaxxt/feedback.mdwn b/code/kaxxt/feedback.mdwn
index 8f326b76..855ebca3 100644
--- a/code/kaxxt/feedback.mdwn
+++ b/code/kaxxt/feedback.mdwn
@@ -1,4 +1,4 @@
 Whatdayathink? Please vote in the poll, or post your
 experiences/questions to [[/code/Kaxxt/Discussion]].
 
-[[!poll 4 "I tried it, liked it." 0 "I tried it, needs work." 13 "I haven't tried it, but want to" 2 "I don't plan to try it"]]
+[[!poll 4 "I tried it, liked it." 0 "I tried it, needs work." 12 "I haven't tried it, but want to" 3 "I don't plan to try it"]]

poll vote (I haven't tried it, but want to)
diff --git a/code/kaxxt/feedback.mdwn b/code/kaxxt/feedback.mdwn
index 4c80decf..8f326b76 100644
--- a/code/kaxxt/feedback.mdwn
+++ b/code/kaxxt/feedback.mdwn
@@ -1,4 +1,4 @@
 Whatdayathink? Please vote in the poll, or post your
 experiences/questions to [[/code/Kaxxt/Discussion]].
 
-[[!poll 4 "I tried it, liked it." 1 "I tried it, needs work." 12 "I haven't tried it, but want to" 2 "I don't plan to try it"]]
+[[!poll 4 "I tried it, liked it." 0 "I tried it, needs work." 13 "I haven't tried it, but want to" 2 "I don't plan to try it"]]

poll vote (I tried it, needs work.)
diff --git a/code/kaxxt/feedback.mdwn b/code/kaxxt/feedback.mdwn
index 38745036..4c80decf 100644
--- a/code/kaxxt/feedback.mdwn
+++ b/code/kaxxt/feedback.mdwn
@@ -1,4 +1,4 @@
 Whatdayathink? Please vote in the poll, or post your
 experiences/questions to [[/code/Kaxxt/Discussion]].
 
-[[!poll 5 "I tried it, liked it." 0 "I tried it, needs work." 12 "I haven't tried it, but want to" 2 "I don't plan to try it"]]
+[[!poll 4 "I tried it, liked it." 1 "I tried it, needs work." 12 "I haven't tried it, but want to" 2 "I don't plan to try it"]]

poll vote (I tried it, liked it.)
diff --git a/code/kaxxt/feedback.mdwn b/code/kaxxt/feedback.mdwn
index 20b95675..38745036 100644
--- a/code/kaxxt/feedback.mdwn
+++ b/code/kaxxt/feedback.mdwn
@@ -1,4 +1,4 @@
 Whatdayathink? Please vote in the poll, or post your
 experiences/questions to [[/code/Kaxxt/Discussion]].
 
-[[!poll 4 "I tried it, liked it." 0 "I tried it, needs work." 12 "I haven't tried it, but want to" 2 "I don't plan to try it"]]
+[[!poll 5 "I tried it, liked it." 0 "I tried it, needs work." 12 "I haven't tried it, but want to" 2 "I don't plan to try it"]]

diff --git a/code/moreutils/discussion.mdwn b/code/moreutils/discussion.mdwn
index fc93bb8a..f6e621d6 100644
--- a/code/moreutils/discussion.mdwn
+++ b/code/moreutils/discussion.mdwn
@@ -1,6 +1,16 @@
 Feel free to edit this page to suggest tools to add, or make any other
 comments --[[Joey]]
 
+## tool suggestion: "re" (Reach Recent Folders)
+
+The `re` command aims to save numerous `cd` operations for reaching recently-used folders.
+This command orders folders by date of last modification, and enables specifying a substring
+of the name of the folder targeted. The `re` command saves me a lot of time, every single day.
+
+It is currently implemented as a shell script.
+https://github.com/charguer/re
+
+
 ## tool suggestion: "even" and "wol"
 
 Written these two tiny tools, but figure they're useful to others:

update for readfrom rename to input
diff --git a/blog/entry/announcing_arduino-copilot.mdwn b/blog/entry/announcing_arduino-copilot.mdwn
index 1ab90ba9..a80f8ad9 100644
--- a/blog/entry/announcing_arduino-copilot.mdwn
+++ b/blog/entry/announcing_arduino-copilot.mdwn
@@ -57,7 +57,7 @@ time, and then back to fast flashing.
 
 	main :: IO ()
 	main = arduino $ do
-	        buttonpressed <- readfrom pin12
+	        buttonpressed <- input pin12
 	        led =: buttonpressed || blinking
 	        delay =: MilliSeconds (longer_and_longer * 2)
 
@@ -93,7 +93,7 @@ without ever generating C code, right at the console!
 But first, one line of code needs to be changed, to provide some button states
 for the simulation:
 
-	        buttonpressed <- readfrom' pin12 [False, False, False, True, True]
+	        buttonpressed <- input' pin12 [False, False, False, True, True]
 
 Now let's see what it does:
 

die spammer skum
diff --git a/blog/entry/DIY_professional_grade_solar_panel_installation/comment_1_36e55b0ee1442202b0de0141bb6af683._comment b/blog/entry/DIY_professional_grade_solar_panel_installation/comment_1_36e55b0ee1442202b0de0141bb6af683._comment
deleted file mode 100644
index 2ab2f157..00000000
--- a/blog/entry/DIY_professional_grade_solar_panel_installation/comment_1_36e55b0ee1442202b0de0141bb6af683._comment
+++ /dev/null
@@ -1,9 +0,0 @@
-[[!comment format=mdwn
- username="kratikawc12@9c0de3354a5df080ca18590d1a95dc5a37ab3174"
- nickname="kratikawc12"
- avatar="http://cdn.libravatar.org/avatar/c6ca6872611820518ecc2de387fadadc"
- subject="solar panel installation Austin"
- date="2020-02-26T07:20:30Z"
- content="""
-I really appreciate this piece of useful information. For more information, you can visit our website: <a href=\"https://austinsolarpanelinstallation.com/\">solar panel installation Austin</a>
-"""]]

Added a comment: solar panel installation Austin
diff --git a/blog/entry/DIY_professional_grade_solar_panel_installation/comment_1_36e55b0ee1442202b0de0141bb6af683._comment b/blog/entry/DIY_professional_grade_solar_panel_installation/comment_1_36e55b0ee1442202b0de0141bb6af683._comment
new file mode 100644
index 00000000..2ab2f157
--- /dev/null
+++ b/blog/entry/DIY_professional_grade_solar_panel_installation/comment_1_36e55b0ee1442202b0de0141bb6af683._comment
@@ -0,0 +1,9 @@
+[[!comment format=mdwn
+ username="kratikawc12@9c0de3354a5df080ca18590d1a95dc5a37ab3174"
+ nickname="kratikawc12"
+ avatar="http://cdn.libravatar.org/avatar/c6ca6872611820518ecc2de387fadadc"
+ subject="solar panel installation Austin"
+ date="2020-02-26T07:20:30Z"
+ content="""
+I really appreciate this piece of useful information. For more information, you can visit our website: <a href=\"https://austinsolarpanelinstallation.com/\">solar panel installation Austin</a>
+"""]]

poll vote (I haven't tried it, but want to)
diff --git a/code/kaxxt/feedback.mdwn b/code/kaxxt/feedback.mdwn
index 1195c7ed..20b95675 100644
--- a/code/kaxxt/feedback.mdwn
+++ b/code/kaxxt/feedback.mdwn
@@ -1,4 +1,4 @@
 Whatdayathink? Please vote in the poll, or post your
 experiences/questions to [[/code/Kaxxt/Discussion]].
 
-[[!poll 4 "I tried it, liked it." 0 "I tried it, needs work." 11 "I haven't tried it, but want to" 2 "I don't plan to try it"]]
+[[!poll 4 "I tried it, liked it." 0 "I tried it, needs work." 12 "I haven't tried it, but want to" 2 "I don't plan to try it"]]

poll vote (watched it all, liked it)
diff --git a/blog/entry/watch_me_code_for_half_an_hour.mdwn b/blog/entry/watch_me_code_for_half_an_hour.mdwn
index 270458c9..a897950c 100644
--- a/blog/entry/watch_me_code_for_half_an_hour.mdwn
+++ b/blog/entry/watch_me_code_for_half_an_hour.mdwn
@@ -14,7 +14,7 @@ Not shown is the hour I spent the next day changing the "optimize"
 subcommand implemented here into "--auto" options that can be passed to
 [[code/git-annex]]'s get and drop commands.
 
-[[!poll 60 "watched it all, liked it" 9 "watched some, boring" 4 "too long for me" 15 "too haskell for me" 13 "not interested"]]
+[[!poll 61 "watched it all, liked it" 9 "watched some, boring" 4 "too long for me" 15 "too haskell for me" 13 "not interested"]]
 
 [[!meta title="watch me program for half an hour"]]
 [[!tag haskell]]

blog update
diff --git a/blog/entry/arduino-copilot_combinators.mdwn b/blog/entry/arduino-copilot_combinators.mdwn
new file mode 100644
index 00000000..27668ed6
--- /dev/null
+++ b/blog/entry/arduino-copilot_combinators.mdwn
@@ -0,0 +1,118 @@
+My framework for programming Arduinos in Haskell has two major
+improvements this week. It's feeling like I'm laying the
+keystone on this project. It's all about the combinators now.
+
+## Sketch combinators
+
+Consider this arduino-copilot program, that does something unless
+a pause button is pushed:
+
+	paused <- input pin3
+	pin4 =: foo @: not paused
+	v <- input a1
+	pin5 =: bar v @: sometimes && not paused
+
+The pause button has to be checked everywhere, and there's a risk
+of forgetting to check it, resulting in unexpected behavior. It would
+be nice to be able to factor that out somehow. Also, notice that it inputs
+from a1 all the time, but won't use that input when pause is pushed.
+It would be nice to be able to avoid that unnecessary work.
+
+The new `whenB` combinator solves all of that:
+
+	paused <- input pin3
+	whenB (not paused) $ do
+		pin4 =: foo
+		v <- input a1
+		pin5 =: bar v @: sometimes
+
+All `whenB` does is takes a `Behavior Bool` and uses it to control
+whether a Sketch runs.  It was not easy to implement, given
+the constraints of Copilot DSL, but it's working. And once I had
+`whenB`, I was able to leverage RebindableSyntax to allow 
+`if then else` expressions to choose between Sketches, as well as between
+Streams.
+
+Now it's easy to start by writing a Sketch that describes a simple behavior,
+like `turnRight` or `goForward`, and glue those together in a straightforward
+way to make a more complex Sketch, like a line-following robot:
+
+	ll <- leftLineSensed
+	rl <- rightLineSensed
+	if ll && rl
+		then stop
+		else if ll
+			then turnLeft
+			else if rl
+				then turnRight
+				else goForward
+
+([Full line following robot example here](https://git.joeyh.name/index.cgi/arduino-copilot.git/plain/examples/robot/demo.hs))
+
+## TypedBehavior combinators
+
+I've complained before that the Copilot DSL limits `Stream` to basic C data
+types, and so progamming with it felt like I was not able to leverage
+the type checker as much as I'd hope to when writing Haskell, to eg
+keep different units of measurement separated.
+
+Well, I found a way around that problem. All it needed was phantom types,
+and some combinators to lift Copilot DSL expressions.
+
+For example, a Sketch that controls a hot water heater certainly
+wants to indicate clearly that temperatures are in C not F, and
+PSI is another important unit. So define some empty types for those units:
+
+	data PSI
+	data Celsius
+
+Using those as the phantom type parameters for TypedBehavior, some
+important values can be defined:
+
+	maxSafePSI :: TypedBehavior PSI Float
+	maxSafePSI = TypedBehavior (constant 45)
+
+	maxWaterTemp :: TypedBehavior Celsius Float
+	maxWaterTemp = TypedBehavior (constant 35)
+
+And functions like this to convert raw ADC readings into our units:
+
+	adcToCelsius :: Behavior Float -> TypedBehavior Celsius Float
+	adcToCelsius v = TypedBehavior $ v * (constant 200 / constant 1024)
+
+And then we can make functions that take these TypedBehaviors and run
+Copilot DSL expressions on the Stream contained within them,
+producing Behaviors suitable for being connected up to pins:
+
+	isSafePSI :: TypedBehavior PSI Float -> Behavior Bool
+	isSafePSI p = liftB2 (<) p maxSafePSI
+	
+	isSafeTemp :: TypedBehavior Celsius Float -> Behavior Bool
+	isSafeTemp t = liftB2 (<) t maxSafePSI
+
+([Full water heater example here](https://git.joeyh.name/index.cgi/arduino-copilot.git/plain/examples/waterheater/demo.hs))
+
+BTW, did you notice the mistake on the last line of code above? No worries;
+the type checker will, so it will blow up at compile time, and not at runtime.
+
+	    • Couldn't match type ‘PSI’ with ‘Celsius’
+	      Expected type: TypedBehavior Celsius Float
+	        Actual type: TypedBehavior PSI Float
+
+The `liftB2` combinator was all I needed to add to support that.
+There's also a `liftB`, and there could be `liftB3` etc. (Could it
+be generalized to a single lift function that supports multiple arities?
+I don't know yet.) It would be good to have more types than just phantom
+types; I particularly miss Maybe; but this does go a long way.
+
+So you can have a good amount of type safety while using Copilot
+to program your Arduino, and you can mix both FRP style and imperative
+style as you like. Enjoy!
+
+----
+
+This work was sponsored by Trenton Cronholm and Jake Vosloo
+on [Patreon](https://patreon.com/joeyh).
+
+[[!tag code/arduino-copilot]]
+[[!tag haskell]]

renam
diff --git a/blog/entry/announcing_arduino-copilot.mdwn b/blog/entry/announcing_arduino-copilot.mdwn
index 34698c19..1ab90ba9 100644
--- a/blog/entry/announcing_arduino-copilot.mdwn
+++ b/blog/entry/announcing_arduino-copilot.mdwn
@@ -142,4 +142,4 @@ Development of arduino-copilot was sponsored by Trenton Cronholm and
 Jake Vosloo [on Patreon](https://patreon.com/joeyh).
 
 [[!tag haskell]]
-[[!tag code/haskell-arduino-copilot]]
+[[!tag code/arduino-copilot]]
diff --git a/blog/entry/arduino-copilot_one_week_along.mdwn b/blog/entry/arduino-copilot_one_week_along.mdwn
index d27c2ab6..d18ae001 100644
--- a/blog/entry/arduino-copilot_one_week_along.mdwn
+++ b/blog/entry/arduino-copilot_one_week_along.mdwn
@@ -72,4 +72,4 @@ Development of arduino-copilot was sponsored by Trenton Cronholm and
 Jake Vosloo [on Patreon](https://patreon.com/joeyh).
 
 [[!tag haskell]]
-[[!tag code/haskell-arduino-copilot]]
+[[!tag code/arduino-copilot]]
diff --git a/code.mdwn b/code.mdwn
index ecab83aa..38766cb0 100644
--- a/code.mdwn
+++ b/code.mdwn
@@ -20,7 +20,7 @@ The stuff that's swapped into my local cache at the moment.
 [[easy-peasy-devicetree-squeezy]]
 [[fridge0]]
 [[haskell-filepath-bytestring]]
-[[haskell-arduino-copilot]]
+[[arduino-copilot]]
 
 ## Less active projects
 
diff --git a/code/haskell-arduino-copilot.mdwn b/code/arduino-copilot.mdwn
similarity index 100%
rename from code/haskell-arduino-copilot.mdwn
rename to code/arduino-copilot.mdwn

blog update
diff --git a/blog/entry/arduino-copilot_one_week_along.mdwn b/blog/entry/arduino-copilot_one_week_along.mdwn
new file mode 100644
index 00000000..d27c2ab6
--- /dev/null
+++ b/blog/entry/arduino-copilot_one_week_along.mdwn
@@ -0,0 +1,75 @@
+My framework for programming Arduinos in Haskell in FRP-style is 
+[[a week old|announcing_arduino-copilot]], and it's grown up a lot.
+
+It can do much more than flash a light now. The `=:` operator can now connect
+all kinds of FRP Events to all kinds of outputs. There's some type level
+progamming going on to only allow connections that make sense. For example,
+[[code/arduino-copilot]] knows what pins of an Adruino support DigitalIO and
+which support PWM. There are even nice custom type error messages:
+
+	demo.hs:7:9: error:
+	    • This Pin does not support digital IO
+	    • In a stmt of a 'do' block: a6 =: blinking
+
+I wanted it to be easy to add support to [[code/arduino-copilot]] for using
+Arduino C libraries from Haskell, and that's proven to be the case. I added
+serial support last weekend, which is probably one of the harder libraries. It
+all fell into place once I realized it should not be about individual printfs,
+but about a single FRP behavior that describes all output to the serial port.
+This interface was the result:
+
+	n <- input a1 :: Sketch (Behavior ADC)
+	Serial.device =: [Serial.str "a1:", Serial.show n, Serial.char '\n']
+	Serial.baud 9600
+
+This weekend I've been adding support for the EEPROMex library, and the
+Functional Reactive Programming approach really shines in stuff like this
+example, which gathers data from a sensor, logs it to the serial port, and
+also stores every 3rd value into the EEPROM for later retrival, using the
+whole EEPROM as a rolling buffer.
+
+	v <- input a1 ([10, 20..] :: [ADC])
+	range <- EEPROM.allocRange sizeOfEEPROM :: Sketch (EEPROM.Range ADC)
+	range =: EEPROM.sweepRange 0 v @: frequency 3
+	led =: frequency 3
+	Serial.device =: [ Serial.show v, Serial.char '\n']
+	Serial.baud 9600
+	delay =: MilliSeconds (constant 10000)
+
+There's a fair bit of abstraction in that... Try doing that in 7 lines of C
+code with that level of readability. (It compiles into 120 lines of C.)
+
+Copilot's ability to interpret the program and show what it would do, without
+running it on the Adruino, seems more valuable the more complicated the
+programs become. Here's the interpretation of the program above.
+
+	delay:     digitalWrite_13:      eeprom_range_write1:  output_Serial:       
+	(10000)    (13,false)            --                    (10)                 
+	(10000)    (13,true)             (0,20)                (20)                 
+	(10000)    (13,false)            --                    (30)                 
+	(10000)    (13,false)            --                    (40)                 
+	(10000)    (13,true)             (1,50)                (50)                 
+	(10000)    (13,false)            --                    (60)          
+
+Last night I was writing a program that amoung other things, had an event that
+only happened once every 70 minutes (when the Arduino's `micros` clock
+overflows). I didn't have to wait hours staring at the Arduino to test
+and debug my program, instead I interpreted it with a clock input that
+overflowed on demand.
+
+(Hmm, I've not actually powered my Arduino on in nearly a week despite writing
+new Arduino programs every day.)
+
+So [[code/arduino-copilot]] is feeling like it's something that I'll be using
+soon to write real world Arduino programs. It's certianly is not usable for all
+Arduino programming, but it will support all the kinds of programs I want to
+write, and being able to use Functional Reactive Programming will make me want
+to write them.
+
+----
+
+Development of arduino-copilot was sponsored by Trenton Cronholm and
+Jake Vosloo [on Patreon](https://patreon.com/joeyh).
+
+[[!tag haskell]]
+[[!tag code/haskell-arduino-copilot]]

format + ps
diff --git a/code/moreutils/discussion.mdwn b/code/moreutils/discussion.mdwn
index 7ea8b25d..fc93bb8a 100644
--- a/code/moreutils/discussion.mdwn
+++ b/code/moreutils/discussion.mdwn
@@ -616,4 +616,6 @@ Curiously, running bar.sh directly doesn't have this problem.  I'm not sure what
 
 ## pee
 
-* Please can the manpage warn of the non-preservation of order, on the collected stdout from child processes?  On first inspection with `pee md5sum sha256sum` vs `pee sha256sum md5sum`, and on a fast/idle machine, it looks like stdout are collected and then written. But more complex examples show that stdouts may be interleaved even when there have been no newlines yet, so `pee 'md5sum > foo.md5' 'sha256sum > foo.sha256'` is a much better solution.  Thanks -- m
+* Please can the manpage warn of the non-preservation of order, on the collected stdout from child processes?  
+  On first inspection with `pee md5sum sha256sum` vs `pee sha256sum md5sum`, and on a fast/idle machine, it looks like stdout are collected and then written. But more complex examples show that stdouts may be interleaved even when there have been no newlines yet, so `pee 'md5sum > foo.md5' 'sha256sum > foo.sha256'` is a much better solution.  Thanks -- m  
+  *ps.* no bytes were harmed in our discovery of this behaviour, because we've seen interleaved data too many times before! :-]

request for specific clarification on pee(1) manpage
diff --git a/code/moreutils/discussion.mdwn b/code/moreutils/discussion.mdwn
index 2a9a6571..7ea8b25d 100644
--- a/code/moreutils/discussion.mdwn
+++ b/code/moreutils/discussion.mdwn
@@ -613,3 +613,7 @@ Curiously, running bar.sh directly doesn't have this problem.  I'm not sure what
 
 * [overwrite](https://unix.stackexchange.com/a/11074/176171)
 * [ftrunctate](https://unix.stackexchange.com/a/280277/176171)
+
+## pee
+
+* Please can the manpage warn of the non-preservation of order, on the collected stdout from child processes?  On first inspection with `pee md5sum sha256sum` vs `pee sha256sum md5sum`, and on a fast/idle machine, it looks like stdout are collected and then written. But more complex examples show that stdouts may be interleaved even when there have been no newlines yet, so `pee 'md5sum > foo.md5' 'sha256sum > foo.sha256'` is a much better solution.  Thanks -- m

update for arduino-copilot-1.2.0
diff --git a/blog/entry/announcing_arduino-copilot.mdwn b/blog/entry/announcing_arduino-copilot.mdwn
index 0219923a..34698c19 100644
--- a/blog/entry/announcing_arduino-copilot.mdwn
+++ b/blog/entry/announcing_arduino-copilot.mdwn
@@ -10,7 +10,7 @@ To make your arduino blink its LED, you only need 4 lines of Haskell:
 	import Copilot.Arduino
 	main = arduino $ do
 		led =: blinking
-		delay =: constant 100
+		delay =: constant (MilliSeconds 100)
 
 Running that Haskell program generates an Arduino sketch in an `.ino` file,
 which can be loaded into the Arduino IDE and uploaded to the Arduino the
@@ -59,7 +59,7 @@ time, and then back to fast flashing.
 	main = arduino $ do
 	        buttonpressed <- readfrom pin12
 	        led =: buttonpressed || blinking
-	        delay =: longer_and_longer * 2
+	        delay =: MilliSeconds (longer_and_longer * 2)
 
 This is starting to use features of the Copilot DSL; 
 "`buttonpressed || blinking`" combines two FRP streams together,
@@ -98,7 +98,7 @@ for the simulation:
 Now let's see what it does:
 
 	# runghc demo.hs -i 5
-	delay:         digitalWrite: 
+	delay:         digitalWrite_13: 
 	(2)            (13,false)    
 	(4)            (13,true)     
 	(8)            (13,false)    
diff --git a/blog/entry/announcing_arduino-copilot/comment_2_958ed75df653692e8d54e6c38c2858ab._comment b/blog/entry/announcing_arduino-copilot/comment_2_958ed75df653692e8d54e6c38c2858ab._comment
new file mode 100644
index 00000000..6ed5cde9
--- /dev/null
+++ b/blog/entry/announcing_arduino-copilot/comment_2_958ed75df653692e8d54e6c38c2858ab._comment
@@ -0,0 +1,12 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 2"""
+ date="2020-01-28T23:32:53Z"
+ content="""
+There's a more general library that could be factored out of
+arduino-copilot, perhaps, to support other micros that don't use arduino
+sketches being programmed FRP style.
+
+I don't know if bSpokeLight's image processing could be done
+in the Copilot DSL. Maybe.
+"""]]