This feed does not validate.

In addition, interoperability with the widest range of feed readers could be improved by implementing the following recommendation.


  1. <?xml version="1.0"?>
  2. <!-- name="generator" content="blosxom/2.1.2" -->
  3. <!DOCTYPE rss PUBLIC "-//Netscape Communications//DTD RSS 0.91//EN" "">
  5. <rss version="0.91">
  6.  <channel>
  7.    <title>Diary of a geek</title>
  8.    <link></link>
  9.    <description>Andrew Pollock's blog.</description>
  10.    <language>en</language>
  12.  <item>
  13.    <title>[debian] Fixing some issues with</title>
  14.    <description>
  15.     &lt;p&gt;
  16. I got an email last year pointing out a cosmetic issue with
  17. I think at the time of the email, the only problem was
  18. some bitrot in PHP&apos;s built-in server variables making some text appear
  19. incorrectly.
  20. &lt;/p&gt;
  21. &lt;p&gt;
  22. I duly added something to my TODO list to fix it, and it subsequently sat there
  23. for like 13 months. In the ensuing time, Debian changed some stuff, and my code
  24. started incorrectly handling a 302 as well, which actually broke it good and
  25. proper.
  26. &lt;/p&gt;
  27. &lt;p&gt;
  28. I finally got around to fixing it.
  29. &lt;/p&gt;
  30. &lt;p&gt;
  31. I also fixed a problem where sometimes there can be multiple entries in the
  32. &lt;tt&gt;Sources&lt;/tt&gt; file for a package (switching to using
  33. &lt;tt&gt;;/tt&gt; would also address this), which caused
  34. sometimes caused an incorrect version of the changelog to be returned.
  35. &lt;/p&gt;
  36. &lt;p&gt;
  37. In the resulting tinkering, I learned about &lt;a
  38. href=&quot;;&gt;&lt;tt&gt;;/tt&gt;&lt;/a&gt;,
  39. which is totally awesome. I could stop maintaining and parsing a local copy of
  40. sid&apos;s &lt;tt&gt;Sources&lt;/tt&gt; file, and just make a call to this instead.
  41. &lt;/p&gt;
  42. &lt;p&gt;
  43. Finally, I added linking to CVEs, because it was a quick thing to do, and adds
  44. value.
  45. &lt;/p&gt;
  46. &lt;p&gt;
  47. In light of &lt;tt&gt;;/tt&gt;, I&apos;m very tempted to rewrite the
  48. redirector. The code is very old and hard for present-day Andrew to maintain,
  49. and I despise PHP. I&apos;d rather write it in Python today, with some proper test
  50. coverage. I could also potentially host it on AppEngine instead of locally,
  51. just so I get some experience with AppEngine
  52. &lt;/p&gt;
  53. &lt;p&gt;
  54. It&apos;s also been suggested that I fold the changes into the changelog hosting on
  55. &lt;tt&gt;;/tt&gt;. I&apos;m hesitant to do this, as it would require
  56. changing the output from plain text to HTML, which would mess up consumers of
  57. the plain text (like the current implementation of
  58. &lt;/p&gt;
  59.    </description>
  60.    <link></link>
  61.    <pubDate>Sun, 17 May 2015 14:42:00 </pubDate>
  62.  </item>
  63.  <item>
  64.    <title>[tech] LWN Chrome extension published</title>
  65.    <description>
  66.     &lt;p&gt;
  67. I finally got around to finishing off and &lt;a
  68. href=&quot;;&gt;publishing&lt;/a&gt;
  69. the LWN Chrome extension that I &lt;a
  70. href=&quot;;&gt;wrote a couple of months
  71. ago&lt;/a&gt;.
  72. &lt;/p&gt;
  73. &lt;p&gt;
  74. I received one piece of feedback from someone who read my blog via Planet
  75. Debian, but didn&apos;t appear to email me from a usable email address, so I&apos;ll
  76. respond to the criticisms here.
  77. &lt;/p&gt;
  78. &lt;p&gt;
  79. I wrote a Chrome extension because I use Google Chrome. To the best of my
  80. knowledge, it will work with Chromium as well, but as I&apos;ve never used it, I
  81. can&apos;t really say for sure. I&apos;ve chosen to licence the source under the Apache
  82. Licence, and make it &lt;a
  83. href=&quot;;a=summary&quot;&gt;freely
  84. available&lt;/a&gt;. So the extension is available to anyone who cares to download
  85. the source and &quot;side load&quot; it, if they don&apos;t want to use the Chrome Web Store.
  86. &lt;/p&gt;
  87. &lt;p&gt;
  88. As for whether a &lt;a
  89. href=&quot;;&gt;userscript&lt;/a&gt; would have
  90. done the job, maybe, but I have no experience with them.
  91. &lt;/p&gt;
  92. &lt;p&gt;
  93. Basically, I had an itch, and I scratched it, for the browser I choose to
  94. use, and I also chose to share it freely.
  95. &lt;/p&gt;
  96.    </description>
  97.    <link></link>
  98.    <pubDate>Wed, 13 May 2015 22:03:00 </pubDate>
  99.  </item>
  100.  <item>
  101.    <title>[life] Zoe at 5</title>
  102.    <description>
  103.     &lt;p&gt;
  104. Zoe celebrated her 5th birthday a day early with a lovely party at Sarah&apos;s
  105. house, with a bunch of her friends from Kindergarten, Prep and beyond. This
  106. birthday also means she&apos;s been living in two homes for as much of her life as
  107. she&apos;s lived in one. On that front, mercifully, she seems to be doing as well as
  108. one could possibly hope for. This is her normal, as much as it breaks my heart.
  109. &lt;/p&gt;
  110. &lt;p&gt;
  111. She&apos;s doing fabulously well on all fronts, really. She&apos;s grown into a lovely
  112. little girl that I always enjoy spending time with. She&apos;s finally figured out
  113. how to ride a bike, so I&apos;ve bought her a bigger bike for her birthday. I
  114. believe her swimming is going really well (I haven&apos;t seen her in action for a
  115. while because she does her swim classes via after-school care, but I&apos;m
  116. fortunate to have one of my Thermomix consultant team members be her swim
  117. teacher, so I get some feedback from time to time).
  118. &lt;/p&gt;
  119. &lt;p&gt;
  120. We had parent-teacher interviews at the end of last term, and from all reports
  121. there, Zoe seemed to be doing well in Prep. Her sight-words are going pretty
  122. well. She&apos;s got the hang of phonics. She can write her name. She seems to have
  123. made friends with lots of the kids in her class. We&apos;ve had a few of them over
  124. for dinner. I feel very connected with the school community.
  125. &lt;/p&gt;
  126. &lt;p&gt;
  127. I&apos;m really grateful that I got about 5 weeks at the start of Prep before I
  128. returned to work. I got to be really involved with school for a little bit. I
  129. helped out with her school swim classes. I helped out with a literacy group. I
  130. did Tuckshop a couple of times. It was lovely. I wish I could be a stay at home
  131. parent so I could do that sort of thing all the time, but that&apos;s just not
  132. possible (at the moment, anyway). The school clearly relies quite heavily on
  133. parent helpers.
  134. &lt;/p&gt;
  135. &lt;p&gt;
  136. Five (and the lead up to it) seems to be a pretty fantastic age. I&apos;m loving
  137. being her Dad now just as much as any other time.
  138. &lt;/p&gt;
  139.    </description>
  140.    <link></link>
  141.    <pubDate>Mon, 04 May 2015 13:36:00 </pubDate>
  142.  </item>
  143.  <item>
  144.    <title>[tech] Honey, I wrote my first Chrome extension!</title>
  145.    <description>
  146.     &lt;p&gt;
  147. I love reading &lt;a href=&quot;;&gt;Linux Weekly News&lt;/a&gt;. It&apos;s a
  148. great source of high quality Linux and FOSS journalism, and I&apos;ve been a
  149. subscriber for years.
  150. &lt;/p&gt;
  151. &lt;p&gt;
  152. One mild annoyance I have with the site is the way articles are cross-linked.
  153. All the article URIs are in the format &lt;tt&gt;/Article/531114/&lt;/tt&gt;, which isn&apos;t
  154. particularly descriptive about that article&apos;s content.
  155. &lt;/p&gt;
  156. &lt;p&gt;
  157. When faced with an article that links to another article, with perhaps a word
  158. of anchor text, it&apos;s hard to tell if the new article is worth opening in a tab,
  159. is indeed already open in a tab, or has been previously read. (Yes, the
  160. &quot;visited link&quot; colour can help to a small degree, but even then, it doesn&apos;t
  161. tell you &lt;em&gt;which&lt;/em&gt; previously read article it is).
  162. &lt;/p&gt;
  163. &lt;p&gt;
  164. This is what &lt;strike&gt;God&lt;/strike&gt; the W3C invented &lt;a
  165. href=&quot;;&gt;the title
  166. attribute&lt;/a&gt; for.
  167. &lt;/p&gt;
  168. &lt;p&gt;
  169. Back in April 2011, I emailed Jonathan Corbet and asked if his content
  170. management system could just do this, but it was apparently a bit tricky, and
  171. it got filed in the &quot;feature request&quot; bucket.
  172. &lt;/p&gt;
  173. &lt;p&gt;
  174. I was sufficiently irritated by this deficiency last Monday, when doing some
  175. heavy reading on a topic, and so I decided to take matters into my own hands,
  176. and also learn how to write a &lt;a
  177. href=&quot;;&gt;Chrome Extension&lt;/a&gt; into the
  178. bargain.
  179. &lt;/p&gt;
  180. &lt;p&gt;
  181. I was delighted to have scratched the itch under 24 hours later and &lt;a
  182. href=&quot;;a=summary&quot;&gt;developed something
  183. that solved my particular problem&lt;/a&gt; - &lt;tt&gt;lwn4chrome&lt;/tt&gt; I&apos;m calling it.
  184. &lt;/p&gt;
  185. &lt;p&gt;
  186. I&apos;m just finalising an icon for it, and then I&apos;ll have a stab at putting it in
  187. the &lt;a href=&quot;;&gt;Chrome Web Store&lt;/a&gt; as a
  188. freebie.
  189. &lt;/p&gt;
  190. &lt;p&gt;
  191. I might even have a crack at writing a Firefox extension as well for
  192. completeness, but I suspect the bulk of LWN&apos;s readership is using Chrome or
  193. Chromium.
  194. &lt;/p&gt;
  195.    </description>
  196.    <link></link>
  197.    <pubDate>Sat, 07 Mar 2015 22:03:00 </pubDate>
  198.  </item>
  199.  <item>
  200.    <title>[work] Everything old is new again</title>
  201.    <description>
  202.     &lt;p&gt;
  203. In 2005, when I was working for Cybertrust, my job title was Security Engineer.
  204. Then I left that job, and Australia, to &lt;a
  205. href=&quot;;&gt;go work for
  206. Google&lt;/a&gt; as a Linux Systems Administrator.
  207. &lt;/p&gt;
  208. &lt;p&gt;
  209. 10 years later, after a &lt;a
  210. href=&quot;;&gt;fabulous 13 month
  211. break&lt;/a&gt;, I return to Google as a Security Engineer once more.
  212. &lt;/p&gt;
  213. &lt;p&gt;
  214. I honestly didn&apos;t expect it would be possible to return to Google under the
  215. same conditions that I had before I left, so I had very low expectations. I
  216. have to say that I am extremely humbled by the level of support I have
  217. received, both from my peers and my management, to come back.
  218. &lt;/p&gt;
  219. &lt;p&gt;
  220. I also had to make a difficult decision (aided by a coin toss) over whether to
  221. return to Google or accept an offer from a local company that would have been a
  222. good opportunity to make a broad impact.
  223. &lt;/p&gt;
  224.    </description>
  225.    <link></link>
  226.    <pubDate>Fri, 06 Mar 2015 23:04:00 </pubDate>
  227.  </item>
  228.  </channel>
  229. </rss>
Copyright © 2002-9 Sam Ruby, Mark Pilgrim, Joseph Walton, and Phil Ringnalda