FEED Validator

Congratulations!

This is a valid RSS feed.

Recommendations

This feed is valid, but interoperability with the widest range of feed readers could be improved by implementing the following recommendations.

• line 893, column 0: description should not contain role attribute (5 occurrences) [help]

  kernel<sup id="fnref:1"><a href="#fn:1" class=" ...
  

• line 893, column 345: description should not contain relative URL references: #fn:1 (6 occurrences) [help]

  ... 4;&gt;2&lt;/a&gt;&lt;/sup&gt;.&lt;/p&gt;</description>
                                               ^

Source: http://jens.mooseyard.com/index.xml

1. <?xml version="1.0" encoding="utf-8" standalone="yes"?>
2. <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
3.  <channel>
4.    <title>Thought Palace</title>
5.    <link>https://jens.mooseyard.com/</link>
6.    <description>Recent content on Thought Palace</description>
7.    <generator>Hugo -- gohugo.io</generator>
8.    <language>en-us</language>
9.    <lastBuildDate>Thu, 04 Nov 2021 20:09:32 -0700</lastBuildDate><atom:link href="https://jens.mooseyard.com/index.xml" rel="self" type="application/rss+xml" />
10.    <item>
11.      <title>Beautiful Plumage</title>
12.      <link>https://jens.mooseyard.com/2021/11/04/beautiful-plumage/</link>
13.      <pubDate>Thu, 04 Nov 2021 20:09:32 -0700</pubDate>
14.      
15.      <guid>https://jens.mooseyard.com/2021/11/04/beautiful-plumage/</guid>
16.      <description>After quite a hiatus, again, I&amp;rsquo;ve produced a new mixtape: Beautiful Plumage. This one compiles new rock music from the past five years, in an attempt to disprove the eternal &amp;ldquo;rock is dead&amp;rdquo; meme.</description>
17.    </item>
18.    
19.    <item>
20.      <title>Easy Type-Safe Integer Types In C&#43;&#43;</title>
21.      <link>https://jens.mooseyard.com/2021/09/16/easy-type-safe-integer-types-in-c-/</link>
22.      <pubDate>Thu, 16 Sep 2021 12:12:46 -0700</pubDate>
23.      
24.      <guid>https://jens.mooseyard.com/2021/09/16/easy-type-safe-integer-types-in-c-/</guid>
25.      <description>I&amp;rsquo;m working on a somewhat intricate C++ project (a persistent storage manager) that internally uses a lot of different integral types: page numbers, page offsets, page-cache indexes, bucket indexes, hash codes, transaction sequence numbers&amp;hellip; It&amp;rsquo;s very easy to get these mixed up, especially by passing parameters in the wrong order when a function takes more than one of these types; the results of that would be pretty bad.
26. It would be great if I could declare each of these as a different type, and the compiler would stop me from assigning a value of one type to a different one.</description>
27.    </item>
28.    
29.    <item>
30.      <title>If You Can See This, Netlify Works</title>
31.      <link>https://jens.mooseyard.com/2021/09/12/if-you-can-see-this-netlify-works/</link>
32.      <pubDate>Sun, 12 Sep 2021 22:39:14 +0000</pubDate>
33.      
34.      <guid>https://jens.mooseyard.com/2021/09/12/if-you-can-see-this-netlify-works/</guid>
35.      <description>I&amp;rsquo;ve completed the necessary surgery to attach the Netlify CMS to my blog, and I&amp;rsquo;m writing this post in the web-based admin UI. Exciting!
36. Now maybe I&amp;rsquo;ll actually post here&amp;hellip;</description>
37.    </item>
38.    
39.    <item>
40.      <title>The Pig Truck</title>
41.      <link>https://jens.mooseyard.com/2017/05/05/the-pig-truck/</link>
42.      <pubDate>Fri, 05 May 2017 23:47:57 -0700</pubDate>
43.      
44.      <guid>https://jens.mooseyard.com/2017/05/05/the-pig-truck/</guid>
45.      <description>At dawn came the pig truck, driving itself in from over the hills.
46. By the time it reached the jail, the prisoners were lined up, resigned, watched by the armed guards in their towers.
47. Cleaned and shaved, naked and divested of names, they were human no longer.
48. Dust rose and fell as the long blank truck pulled up, the back springing open by itself, the ramp dropping to the ground.</description>
49.    </item>
50.    
51.    <item>
52.      <title>The Dream Of Climbing</title>
53.      <link>https://jens.mooseyard.com/2017/04/17/the-dream-of-climbing/</link>
54.      <pubDate>Mon, 17 Apr 2017 21:01:46 -0700</pubDate>
55.      
56.      <guid>https://jens.mooseyard.com/2017/04/17/the-dream-of-climbing/</guid>
57.      <description>She was a worker, that’s all. A courier. Pick it up here, carry it a long way, drop it off there. It was a dull job, but it meant she didn’t have to think much, which suited her. And everyone she knew worked the same job, so it was easy to share in-jokes and gossip and complain about the conditions.
58. Her people had no vehicles, no roads, no pack animals. But they knew all the trails throughout the valley and the forest, kept them clear and well-marked.</description>
59.    </item>
60.    
61.    <item>
62.      <title>Reinventing Journaling</title>
63.      <link>https://jens.mooseyard.com/2015/05/15/reinventing-journaling/</link>
64.      <pubDate>Fri, 15 May 2015 11:55:01 -0700</pubDate>
65.      
66.      <guid>https://jens.mooseyard.com/2015/05/15/reinventing-journaling/</guid>
67.      <description>Journaling is a style of blogging that&amp;rsquo;s gone out of style lately, for some reason, but it&amp;rsquo;s dear to my heart, and to many of my friends&#39;.
68. Journaling is exemplified by LiveJournal, which has a long proud history as the first social network and possibly the first turnkey blogging system (begun in 1999, it slightly predates Blogger.) LiveJournal still exists, but it&amp;rsquo;s a shadow of its former self. The UI and functionality are stuck in an early-2000s timewarp, and worse, most of the users are gone, having decamped to Twitter and Facebook.</description>
69.    </item>
70.    
71.    <item>
72.      <title>Fears</title>
73.      <link>https://jens.mooseyard.com/2015/05/12/fears/</link>
74.      <pubDate>Tue, 12 May 2015 20:49:58 -0700</pubDate>
75.      
76.      <guid>https://jens.mooseyard.com/2015/05/12/fears/</guid>
77.      <description>I&amp;rsquo;m afraid of a lot of things. Or, I&amp;rsquo;m often afraid of things. I have some issues with anxiety. The anxieties aren&amp;rsquo;t constantly in my way; they&amp;rsquo;re more like electric fences that keep me in line. I can go through my everyday life without thinking of them, but when I venture outside what I&amp;rsquo;m comfortable with I start to get crackles of sparks down my spine and in the pit of my stomach, and then usually I back away.</description>
78.    </item>
79.    
80.    <item>
81.      <title>Baaaa</title>
82.      <link>https://jens.mooseyard.com/2015/02/10/baaaa/</link>
83.      <pubDate>Tue, 10 Feb 2015 22:27:23 -0800</pubDate>
84.      
85.      <guid>https://jens.mooseyard.com/2015/02/10/baaaa/</guid>
86.      <description>They were easy enough to mistake for sheep at a distance — white, fluffy, contentedly grazing — especially in the pre-storm dimness. It was when he got closer to them and saw their body shapes and the way they were eating that Laurence began to regret coming to the farm. As he watched, the nearest animal sheared off a half-dozen dandelions with its mandibles, squirted some sort of digestive ichor on them, and began rhythmic movements of its mouthparts.</description>
87.    </item>
88.    
89.    <item>
90.      <title>Another new blog...</title>
91.      <link>https://jens.mooseyard.com/2015/01/11/another-new-blog.../</link>
92.      <pubDate>Sun, 11 Jan 2015 21:25:58 -0800</pubDate>
93.      
94.      <guid>https://jens.mooseyard.com/2015/01/11/another-new-blog.../</guid>
95.      <description>Well, it&amp;rsquo;s the same blog, I&amp;rsquo;ve just replaced Jekyll with Hugo. If I&amp;rsquo;ve succeeded, you won&amp;rsquo;t be able to tell anything&amp;rsquo;s changed.
96. Every couple of years I go through this ritual of porting to a different blogging engine. This blog started out as handwritten HTML, then it went through Movable Type, Drupal, WordPress, Jekyll, and now Hugo.
97. Each iteration is usually an improvement, but to be honest, the main reason is to have a chance to mess with Web Stuff for a while.</description>
98.    </item>
99.    
100.    <item>
101.      <title>About</title>
102.      <link>https://jens.mooseyard.com/about/</link>
103.      <pubDate>Sun, 11 Jan 2015 20:26:58 -0800</pubDate>
104.      
105.      <guid>https://jens.mooseyard.com/about/</guid>
106.      <description>Introverted, intuitive, thinking, perceiving. I live to make things: most often software, sometimes designs or mix-CDs or stories or photos. (I wish I could make music.)
107. Father. Single dad, raising (at the moment) two teenagers.
108. Worker, dreamer. I’m driven by visions of things that could be. I built things at Apple (AppleScript, Stickies, iChat…) and at Google (Chrome) and I&amp;rsquo;m now at Couchbase building tools to let devices share information with each other.</description>
109.    </item>
110.    
111.    <item>
112.      <title>App Dream</title>
113.      <link>https://jens.mooseyard.com/2014/02/06/app-dream/</link>
114.      <pubDate>Thu, 06 Feb 2014 12:00:00 -0800</pubDate>
115.      
116.      <guid>https://jens.mooseyard.com/2014/02/06/app-dream/</guid>
117.      <description>I&amp;rsquo;m at a computer lab [probably the one from college] and have written an entire email client app in a day. I&amp;rsquo;m excitedly showing it off to everyone. It&amp;rsquo;s kind of glitchy but I can pull up my real emails, including spam.
118. The app is also, simultaneously, made out of a 2-liter soda bottle. It starts out crushed, and expands and fills with water as it launches. Unfortunately there are some cracks that water squirts out of.</description>
119.    </item>
120.    
121.    <item>
122.      <title>Notes Toward A Social-Network Schema</title>
123.      <link>https://jens.mooseyard.com/2014/02/04/notes-toward-a-social-network-schema/</link>
124.      <pubDate>Tue, 04 Feb 2014 12:00:00 -0800</pubDate>
125.      
126.      <guid>https://jens.mooseyard.com/2014/02/04/notes-toward-a-social-network-schema/</guid>
127.      <description>&lt;p&gt;Modeling a social networking system like LiveJournal or Facebook in a JSON-document-oriented database like &lt;a href=&#34;http://couchbase.com&#34;&gt;Couchbase&lt;/a&gt; [&lt;a href=&#34;http://www.couchbase.com/mobile#lite&#34;&gt;Lite&lt;/a&gt;] or &lt;a href=&#34;http://couchdb.apache.org&#34;&gt;CouchDB&lt;/a&gt; isn&amp;rsquo;t hard. Here&amp;rsquo;s a basic schema that I&amp;rsquo;ve been playing with for a while.&lt;/p&gt;</description>
128.    </item>
129.    
130.    <item>
131.      <title>&#34;Forest Wire&#34; Mix</title>
132.      <link>https://jens.mooseyard.com/2014/02/01/forest-wire-mix/</link>
133.      <pubDate>Sat, 01 Feb 2014 12:00:00 -0800</pubDate>
134.      
135.      <guid>https://jens.mooseyard.com/2014/02/01/forest-wire-mix/</guid>
136.      <description>&lt;p&gt;&lt;!-- raw HTML omitted --&gt;&lt;!-- raw HTML omitted --&gt;&lt;!-- raw HTML omitted --&gt;&lt;/p&gt;
137. &lt;p&gt;Here&amp;rsquo;s my most recent music mix, &lt;strong&gt;&lt;a href=&#34;http://recordings.mooseyard.com/mub79/&#34;&gt;&amp;ldquo;Forest Wire&amp;rdquo;&lt;/a&gt;&lt;/strong&gt;, all music from 2013. This mix is dedicated to my brother-in-law who builds guitars but nonetheless appreciates electronic music. It starts and ends ambient, but builds up into dub and K-pop and jungle and other styles.&lt;/p&gt;</description>
138.    </item>
139.    
140.    <item>
141.      <title>What I&#39;m Up To In 2014</title>
142.      <link>https://jens.mooseyard.com/2014/01/31/what-im-up-to-in-2014/</link>
143.      <pubDate>Fri, 31 Jan 2014 12:00:00 -0800</pubDate>
144.      
145.      <guid>https://jens.mooseyard.com/2014/01/31/what-im-up-to-in-2014/</guid>
146.      <description>Couchbase Lite (Née TouchDB, née Couchbase Mobile) Mobile syncable NoSQL database for iOS. My work project in one way or another since I started at Couchbase in mid-2011. I&amp;rsquo;m still having fun working on it.
147. Couchbase Sync Gateway The companion piece &amp;ndash; the glue that lets Couchbase Lite sync with Couchbase Server. It&amp;rsquo;s been challenging and educational and boundary-stretching, and part of me is sick of working on it because the secret is I&amp;rsquo;m not a big-data guy.</description>
148.    </item>
149.    
150.    <item>
151.      <title>New app in testing: Jackdaw</title>
152.      <link>https://jens.mooseyard.com/2014/01/29/new-app-in-testing-jackdaw/</link>
153.      <pubDate>Wed, 29 Jan 2014 12:00:00 -0800</pubDate>
154.      
155.      <guid>https://jens.mooseyard.com/2014/01/29/new-app-in-testing-jackdaw/</guid>
156.      <description>I’m looking for some more beta testers for a font preview/management utility I’m working on. I&amp;rsquo;ve been frustrated by not having a good visual way to browse my font library, so I wrote my own. It’s called Jackdaw.
157. If you have a sizable font collection, choose (or just ogle) fonts on a regular basis, are willing and able to send bug reports/crash logs/suggestions, and are running OS X 10.8 or 10.</description>
158.    </item>
159.    
160.    <item>
161.      <title>New Blog For 2014</title>
162.      <link>https://jens.mooseyard.com/2014/01/27/new-blog-for-2014/</link>
163.      <pubDate>Mon, 27 Jan 2014 12:00:00 -0800</pubDate>
164.      
165.      <guid>https://jens.mooseyard.com/2014/01/27/new-blog-for-2014/</guid>
166.      <description>This blog kind of ground to a halt in 2011. I think the final straw was having my WordPress hacked and many of the posts defaced with spam links. After that I swore a mighty oath not to have any further trafficking with the wickedness of PHP.
167. But I still miss blogging (proper blogging not tumblr). Sometimes I have things to say! And apparently back in the day a few people even used to read things I wrote here, which is nice to think about.</description>
168.    </item>
169.    
170.    <item>
171.      <title>Announcing TouchDB</title>
172.      <link>https://jens.mooseyard.com/2011/12/19/announcing-touchdb/</link>
173.      <pubDate>Mon, 19 Dec 2011 12:00:00 -0800</pubDate>
174.      
175.      <guid>https://jens.mooseyard.com/2011/12/19/announcing-touchdb/</guid>
176.      <description>&lt;p&gt;[I just posted this to the Couchbase Mobile community mailing list.]&lt;/p&gt;
177. <p><a href="https://github.com/couchbaselabs/TouchDB-iOS/"><strong>TouchDB</strong></a> is a
178. project I’ve been feverishly working on for a few weeks. It’s an
179. investigation into the feasibility of a CouchDB-compatible database
180. rewritten from the ground up for mobile apps. The comparison I like to
181. make is that “if CouchDB is MySQL, then TouchDB is SQLite”. In fact, it
182. uses SQLite as its underlying storage engine. You can read a <a href="https://github.com/couchbaselabs/TouchDB-iOS/wiki/Why-TouchDB%3F">longer
183. justification for
184. it</a> on
185. its wiki, as well as an
186. <a href="https://github.com/couchbaselabs/TouchDB-iOS/wiki/FAQ">FAQ</a> and <a href="https://github.com/couchbaselabs/TouchDB-iOS/wiki/Object-Design-And-Schema">design
187. document</a>.</p>
188. <p>— It speaks CouchDB’s replication protocol. I’m pretty serious about
189. that; I’m even <a href="https://github.com/couchbaselabs/TouchDB-iOS/wiki/Replication-Algorithm">documenting the
190. protocol</a>.<br>
191. — It also understands a large subset of the REST API, enough so that it
192. works with CouchCocoa. I’ve got a clone of Grocery Sync working as one
193. of the demo apps in the project.<br>
194. — The current implementation is for iOS. If the investigation pans out
195. we’ll port it to Android, and possibly other platforms.</p>
196. <p>TouchDB is certainly not ready for prime-time yet, but here are some
197. current statistics to whet your appetite:&lt;/p&gt;</description>
198.    </item>
199.    
200.    <item>
201.      <title>My presentation from Keeping It Realtime</title>
202.      <link>https://jens.mooseyard.com/2011/11/10/my-presentation-from-keeping-it-realtime/</link>
203.      <pubDate>Thu, 10 Nov 2011 12:00:00 -0800</pubDate>
204.      
205.      <guid>https://jens.mooseyard.com/2011/11/10/my-presentation-from-keeping-it-realtime/</guid>
206.      <description>I gave another talk about Couchbase/CouchDB at the Keeping It Realtime conference this week in Portland. This one is titled “_ch_ch_changes: CouchDB/Couchbase Notifications And Replications”, and the slides are now up on slideshare.
207. I had a great time. The conference itself was pretty exciting, even if some of the content was over my head (I’m not primarily a web developer, server-side isn’t how I roll, and I’ve only just started learning about node.</description>
208.    </item>
209.    
210.    <item>
211.      <title>Couchbase news (and my preso)</title>
212.      <link>https://jens.mooseyard.com/2011/08/10/couchbase-news-and-my-preso/</link>
213.      <pubDate>Wed, 10 Aug 2011 12:00:00 -0800</pubDate>
214.      
215.      <guid>https://jens.mooseyard.com/2011/08/10/couchbase-news-and-my-preso/</guid>
216.      <description>My new employer is doing well:
217. MOUNTAIN VIEW, Calif. – August 10, 2011 – Couchbase, the leading NoSQL database company, today announced it has secured $14 million in a Series C round of financing led by venture capital firm Ignition Partners with participation from the company’s existing investors Accel Partners, Mayfield Fund, and North Bridge Venture Partners. The company has also reserved an additional $1 million for investment from strategic customers and partners.</description>
218.    </item>
219.    
220.    <item>
221.      <title>At The Ice Bar</title>
222.      <link>https://jens.mooseyard.com/2011/08/08/at-the-ice-bar/</link>
223.      <pubDate>Mon, 08 Aug 2011 12:00:00 -0800</pubDate>
224.      
225.      <guid>https://jens.mooseyard.com/2011/08/08/at-the-ice-bar/</guid>
226.      <description>&lt;p&gt;August in Los Angeles was bone-dry and dusty, but he left it behind in
227. the parking lot as he made his way through the series of three doors,
228. heavy and white, and into the frozen refuge of the ice bar. He was
229. known, there, and the hostess greeted him with a sealskin robe, slipped
230. over his shoulders before he had time to start shivering. The tip of her
231. elegant nose felt icy against his own.</p>
232. <p>There was room for one more at the bar, and at a nod from the chef he
233. took the seat gratefully. One often had to wait, stamping feet to ward
234. off the cold. The chef slid the <em>amuse-bouche</em> before him as he unfolded
235. his napkin, and it was exquisite in appearance: a translucent
236. <em>carpaccio</em> of walrus blubber sprinkled with snowflakes. The snowflakes
237. were not unique, in fact they came in precisely two shapes, one
238. sprinkled on the left side of the dish, the other on the right. They
239. made not-quite-imperceptibly different crunches as he ate them. It was
240. touches like this that had made the chef’s name when he was but a young
241. man just arrived from Nunavut.&lt;/p&gt;</description>
242.    </item>
243.    
244.    <item>
245.      <title>Fudge</title>
246.      <link>https://jens.mooseyard.com/2011/05/16/fudge/</link>
247.      <pubDate>Mon, 16 May 2011 12:00:00 -0800</pubDate>
248.      
249.      <guid>https://jens.mooseyard.com/2011/05/16/fudge/</guid>
250.      <description>I’ve just released a new open-source project, a small one — Fudge-Cpp, a fast C++ library for reading and writing Fudge messages.
251. I hadn’t heard of Fudge either, till a few weeks ago, but it’s a type of thing that’s always interested me: a generic structured binary data format. A quick elevator pitch would be “it’s sorta like JSON, except more compact and faster to parse”. (It’s also sorta like Mac property-lists, YAML, etc.</description>
252.    </item>
253.    
254.    <item>
255.      <title>Glitch City</title>
256.      <link>https://jens.mooseyard.com/2011/01/09/glitch-city/</link>
257.      <pubDate>Sun, 09 Jan 2011 12:00:00 -0800</pubDate>
258.      
259.      <guid>https://jens.mooseyard.com/2011/01/09/glitch-city/</guid>
260.      <description>No again, I will not show you what’s under the bandage on my arm. I won’t even look myself, anymore; it’s gotten too disturbing. I mean, the wound hasn’t changed, but every time I look at it it bothers me more, takes me longer to stop shivering. I keep wanting to touch it.
261. Listen: Did you ever play Shock City? I’m not trying to change the subject; hear me out. I played the hell out of that game when I was twelve, and I always wondered what was inside all those buildings you couldn’t get into.</description>
262.    </item>
263.    
264.    <item>
265.      <title>py2rb: A Python-to-Ruby Porting Assistant</title>
266.      <link>https://jens.mooseyard.com/2010/05/01/py2rb-a-python-to-ruby-porting-assistant/</link>
267.      <pubDate>Sat, 01 May 2010 12:00:00 -0800</pubDate>
268.      
269.      <guid>https://jens.mooseyard.com/2010/05/01/py2rb-a-python-to-ruby-porting-assistant/</guid>
270.      <description>I’ve never figured out whether I prefer Python or Ruby, so I’ve written things in both languages. Sometimes I start in one, then change my mind and decide I’d rather use the other. Unfortunately, changing over is painful, even though both have fairly similar syntax. For instance, converting to Ruby means inserting zillions of “end” statements!
271. Having a need to do this recently, I lazily looked around for a script that would do the grunt-work of Python-to-Ruby translation.</description>
272.    </item>
273.    
274.    <item>
275.      <title>Re: Idea for alternative RSS syncing system</title>
276.      <link>https://jens.mooseyard.com/2010/02/09/re-idea-for-alternative-rss-syncing-system/</link>
277.      <pubDate>Tue, 09 Feb 2010 12:00:00 -0800</pubDate>
278.      
279.      <guid>https://jens.mooseyard.com/2010/02/09/re-idea-for-alternative-rss-syncing-system/</guid>
280.      <description>Brent “NetNewsWire” Simmons raises the idea of an open protocol for syncing RSS/Atom subscriptions, that is, a way of keeping multiple local newsreader apps (like on a Mac and an iPhone) in sync with each other, so that they share the same set of subscribed feeds, and remember which articles have already been read. You can think of it as “IMAP for RSS”.
281. NetNewsWire already does this using Google Reader as an intermediary, and Apple’s PubSub framework (which is what Safari and Mail use) shares the read/unread state using MobileMe.</description>
282.    </item>
283.    
284.    <item>
285.      <title>The Music I Liked Of 2009</title>
286.      <link>https://jens.mooseyard.com/2009/12/13/the-music-i-liked-of-2009/</link>
287.      <pubDate>Sun, 13 Dec 2009 12:00:00 -0800</pubDate>
288.      
289.      <guid>https://jens.mooseyard.com/2009/12/13/the-music-i-liked-of-2009/</guid>
290.      <description>Every year the Albums Of The Year lists seem more and more removed from my experience. (Most of the time I haven’t heard a single album on the list.) Worse, we’re now getting into the Of The Decade lists, making me realize how long this has been going on*. If you ask me the top albums of the ’80s or ’90s, I don’t have too much trouble rattling off a bunch of names.</description>
291.    </item>
292.    
293.    <item>
294.      <title>The Dungeon Master</title>
295.      <link>https://jens.mooseyard.com/2009/10/16/the-dungeon-master/</link>
296.      <pubDate>Fri, 16 Oct 2009 12:00:00 -0800</pubDate>
297.      
298.      <guid>https://jens.mooseyard.com/2009/10/16/the-dungeon-master/</guid>
299.      <description>Call the roller of big dice,
300. The long-haired one, and bid him whip
301. On kitchen tables consecutive 18’s.
302. Let the fighters dawdle in such armor
303. As they are used to wear, and let the mages swap
304. Delicious spells from last month’s Dragon.
305. Let a fumble be finale of its caster:
306. The only emperor is the dungeon master.
307. Take from the manual of monsters
308. Painted with three crude beasts, that sheet</description>
309.    </item>
310.    
311.    <item>
312.      <title>The Lost Lesson Of Instant Typing</title>
313.      <link>https://jens.mooseyard.com/2009/10/14/the-lost-lesson-of-instant-typing/</link>
314.      <pubDate>Wed, 14 Oct 2009 12:00:00 -0800</pubDate>
315.      
316.      <guid>https://jens.mooseyard.com/2009/10/14/the-lost-lesson-of-instant-typing/</guid>
317.      <description>Farhad Manjoo writing in Slate about Google Wave:
318. The trouble is, everything you type into Wave is transmitted live, in real time — every keystroke was getting sent to Zach just as I hit it. This made me too self-conscious to get my thoughts across.
319.  … Maybe I should just delete what I’d written and say, “Twitter works because it’s simple.” But I couldn’t do that, because Zach was watching me.</description>
320.    </item>
321.    
322.    <item>
323.      <title>The Top 131 Elephant Jokes</title>
324.      <link>https://jens.mooseyard.com/2009/09/07/the-top-131-elephant-jokes/</link>
325.      <pubDate>Mon, 07 Sep 2009 12:00:00 -0800</pubDate>
326.      
327.      <guid>https://jens.mooseyard.com/2009/09/07/the-top-131-elephant-jokes/</guid>
328.      <description>So far, this blog’s main claim to fame has been as the #2-ranked Google hit for [apricot jam recipe]. But that’s no longer enough to sustain my extravagant lifestyle, so I’m following the next most obvious business opportunity: Elephant jokes! These were huge (the jokes) when I was a kid, but they seem to have been largely forgotten, which is a shame. I tested them out on my kids today, and they still work fine.</description>
329.    </item>
330.    
331.    <item>
332.      <title>I Has A Hash Table</title>
333.      <link>https://jens.mooseyard.com/2009/09/05/i-has-a-hash-table/</link>
334.      <pubDate>Sat, 05 Sep 2009 12:00:00 -0800</pubDate>
335.      
336.      <guid>https://jens.mooseyard.com/2009/09/05/i-has-a-hash-table/</guid>
337.      <description>I know, three weeks ago I said I was building me a B-Tree. I did build it, even the parts I listed under “What’s next?” in that post, and it works. But it became apparent there was a more urgent need for a hash table, for work-related reasons, so I switched gears to build one of those on the same principles.
338. The biggest principle is Append-Only Storage, as described in the prior post.</description>
339.    </item>
340.    
341.    <item>
342.      <title>Gossip For Lakitu</title>
343.      <link>https://jens.mooseyard.com/2009/08/16/gossip-for-lakitu/</link>
344.      <pubDate>Sun, 16 Aug 2009 12:00:00 -0800</pubDate>
345.      
346.      <guid>https://jens.mooseyard.com/2009/08/16/gossip-for-lakitu/</guid>
347.      <description>Last year I wrote a series of blog posts about a peer-to-peer system called Cloudy that I was developing. I was going up the stack, from messaging to identity, but didn’t finish documenting all the layers I’d built. I mostly stopped working on Cloudy after I went back to gainful employment, but I keep thinking about this stuff.
348. “Lakitu”? I’ve since heard about another unrelated project nicknamed Cloudy; and the whole term “cloud” has gotten so debased in the past year that it now stands for outsourcing to giant hidden server farms, which is the antithesis of what I stand for.</description>
349.    </item>
350.    
351.    <item>
352.      <title>I’m Building Me A B-Tree</title>
353.      <link>https://jens.mooseyard.com/2009/08/14/im-building-me-a-b-tree/</link>
354.      <pubDate>Fri, 14 Aug 2009 12:00:00 -0800</pubDate>
355.      
356.      <guid>https://jens.mooseyard.com/2009/08/14/im-building-me-a-b-tree/</guid>
357.      <description>The other day I took it into my head to implement a B+tree. Why? Because they sound neat, and I’ve done hardly any serious programming with trees in my career. (Someone, I think Buzz Andersen, once noted that there are two kinds of programmers: those who do think in terms of trees, and those who do everything with hash tables. I’m in the latter camp.)
358. And also because I’m a big fan of CouchDB, and really admire its elegant storage model.</description>
359.    </item>
360.    
361.    <item>
362.      <title>Security: Not Quite Getting It</title>
363.      <link>https://jens.mooseyard.com/2009/07/13/security-not-quite-getting-it/</link>
364.      <pubDate>Mon, 13 Jul 2009 12:00:00 -0800</pubDate>
365.      
366.      <guid>https://jens.mooseyard.com/2009/07/13/security-not-quite-getting-it/</guid>
367.      <description>I got an iPhone 3GS yesterday (yes, it totally rules.) While setting up online account access for billing, AT&amp;amp;T had me enter a password.
368. There was one of those colored password-strength meters next to the text field, and it said the password I entered was “weak”. Alright, I changed it to add some commas and dashes.
369. Then I hit Submit, and was told that passwords can only contain letters and digits.</description>
370.    </item>
371.    
372.    <item>
373.      <title>320, 160, 192, GO!</title>
374.      <link>https://jens.mooseyard.com/2009/07/07/320-160-192-go/</link>
375.      <pubDate>Tue, 07 Jul 2009 12:00:00 -0800</pubDate>
376.      
377.      <guid>https://jens.mooseyard.com/2009/07/07/320-160-192-go/</guid>
378.      <description>New happy fun summer mix!</description>
379.    </item>
380.    
381.    <item>
382.      <title>The Subtle Dangers Of Distributed Objects</title>
383.      <link>https://jens.mooseyard.com/2009/07/05/the-subtle-dangers-of-distributed-objects/</link>
384.      <pubDate>Sun, 05 Jul 2009 12:00:00 -0800</pubDate>
385.      
386.      <guid>https://jens.mooseyard.com/2009/07/05/the-subtle-dangers-of-distributed-objects/</guid>
387.      <description>Introduction: I wrote this as part of a reply on Apple’s bonjour-dev mailing list, then decided it might be worth publishing more visibly. I’ve found that Cocoa’s Distributed Objects technology is immediately attractive to many developers, while those who’ve used it end up finding that it’s much more complex than it looks. But I haven’t seen much written about the caveats of using it.
388.  I am not saying “don’t use DO” or “DO is broken”!</description>
389.    </item>
390.    
391.    <item>
392.      <title>Career Update, Part &#43;&#43;n</title>
393.      <link>https://jens.mooseyard.com/2009/07/03/career-update-part-n/</link>
394.      <pubDate>Fri, 03 Jul 2009 12:00:00 -0800</pubDate>
395.      
396.      <guid>https://jens.mooseyard.com/2009/07/03/career-update-part-n/</guid>
397.      <description>I’ve been working at Google since last August. The Big G’s hiring process is rather weird — when you interview, it’s not for any specific team. It’s only after you get an offer that you decide which team to join, of the ones with open positions.
398. I decided on Google Sites, which I knew and liked from its days as JotSpot, a hosted wiki with some powerful features. It ended up not being the right place for me, for a couple of reasons:</description>
399.    </item>
400.    
401.    <item>
402.      <title>Is There Any Point To Using The Keychain API On iPhone?</title>
403.      <link>https://jens.mooseyard.com/2009/06/14/is-there-any-point-to-using-the-keychain-api-on-iphone/</link>
404.      <pubDate>Sun, 14 Jun 2009 12:00:00 -0800</pubDate>
405.      
406.      <guid>https://jens.mooseyard.com/2009/06/14/is-there-any-point-to-using-the-keychain-api-on-iphone/</guid>
407.      <description>I’ve always liked the Keychain technology in Mac OS X. Sure, the API is notoriously confusing and awkward, but the end-user benefits are compelling:
408. Secure, encrypted storage for all passwords and keys. Items can be shared between applications — so in principle you don’t have to enter a given password more than once, since other apps will find the existing item in the keychain. Items have access control lists, so they can be restricted to certain apps.</description>
409.    </item>
410.    
411.    <item>
412.      <title>A Bonjour / Chat Tutorial For iPhone Developers</title>
413.      <link>https://jens.mooseyard.com/2009/05/20/a-bonjour-/-chat-tutorial-for-iphone-developers/</link>
414.      <pubDate>Wed, 20 May 2009 12:00:00 -0800</pubDate>
415.      
416.      <guid>https://jens.mooseyard.com/2009/05/20/a-bonjour-/-chat-tutorial-for-iphone-developers/</guid>
417.      <description>MobileOrchard just published a tutorial article by Peter Bakhyryev, describing a sample iPhone app called “Chatty” that acts as a simple peer-to-peer chat-room.
418. “In this tutorial, we are going to explore a simple chat application for the iPhone. It allows you to host your own chat room and advertise it on your local Wi-Fi network (in which case your app acts as a chat “server”) or find and join chat rooms hosted by other people on your network (acting as a chat “client”).</description>
419.    </item>
420.    
421.    <item>
422.      <title>The Assassination of J.G. Ballard Considered As A Metafictional Homage</title>
423.      <link>https://jens.mooseyard.com/2009/04/21/the-assassination-of-j.g.-ballard-considered-as-a-metafictional-homage/</link>
424.      <pubDate>Tue, 21 Apr 2009 12:00:00 -0800</pubDate>
425.      
426.      <guid>https://jens.mooseyard.com/2009/04/21/the-assassination-of-j.g.-ballard-considered-as-a-metafictional-homage/</guid>
427.      <description>“Some people have suggested that mental illness is a kind of adaptation to the sort of circumstances that will arise in the future. As we move towards a more and more psychotic landscape, the psychotic traits are signs of a kind of Darwinian adaptation.”—1998
428. Abstract. Numerous studies have been conducted upon patients in terminal paresis (GPI), placing the author J.G. Ballard in a series of simulated auto crashes, e.g. multiple pileups, head-on collisions, motorcade attacks (fantasies of Presidential assassinations remained a continuing preoccupation, subjects showing a marked polymorphic fixation on windshields and rear trunk assemblies).</description>
429.    </item>
430.    
431.    <item>
432.      <title>Music, Alone</title>
433.      <link>https://jens.mooseyard.com/2009/02/24/music-alone/</link>
434.      <pubDate>Tue, 24 Feb 2009 12:00:00 -0800</pubDate>
435.      
436.      <guid>https://jens.mooseyard.com/2009/02/24/music-alone/</guid>
437.      <description>The feelings created by music are so strong, for me, but so ineffable. The problem of perception is usually described using color — how can we know if the visual sensation I call “red” is anything like the one you call “red”? — but only gets worse as you ascend to higher order perceptions, where even names become harder to apply. What do you call the feeling incited by “Guernica”, and even if you find the same words I would, is it the same feeling?</description>
438.    </item>
439.    
440.    <item>
441.      <title>What will Web 3.0 be?</title>
442.      <link>https://jens.mooseyard.com/2009/02/15/what-will-web-3.0-be/</link>
443.      <pubDate>Sun, 15 Feb 2009 12:00:00 -0800</pubDate>
444.      
445.      <guid>https://jens.mooseyard.com/2009/02/15/what-will-web-3.0-be/</guid>
446.      <description>So, Web 2.0’s heyday is over, and somewhere out there, Web 3.0 is slouching toward us waiting to be born. What will it be?
447. There’s really no such single thing as “Web x”, of course. And all predictions are really just wishes. That being said, my wish is that Web 3.0 will be about distributed systems. To oversimplify:
448. Web 1.0 built up big brand-name websites with their own content — things written by them, or repurposed from the media companies that owned them, or stuff to buy.</description>
449.    </item>
450.    
451.    <item>
452.      <title>sneJ’s Law of Toolbars</title>
453.      <link>https://jens.mooseyard.com/2009/02/13/snejs-law-of-toolbars/</link>
454.      <pubDate>Fri, 13 Feb 2009 12:00:00 -0800</pubDate>
455.      
456.      <guid>https://jens.mooseyard.com/2009/02/13/snejs-law-of-toolbars/</guid>
457.      <description>The Pessimistic Form
458. The set of commands available in a toolbar (even via customization) is restricted to those that are either:
459. (a) painfully obvious (New, Save, etc.), or
460. (b) useless to you (Save As EBCDIC, Post To CompuServe, Bilinear Zeta-Regression, etc.)
461. The Optimistic Form
462. Combine this with the well-known principle that, while everyone uses only a subset of an application’s features, everyone uses a different subset. Conclusion:
463. To be useful, a toolbar’s customization UI should allow every single command in the application.</description>
464.    </item>
465.    
466.    <item>
467.      <title>Couch</title>
468.      <link>https://jens.mooseyard.com/2009/02/03/couch/</link>
469.      <pubDate>Tue, 03 Feb 2009 12:00:00 -0800</pubDate>
470.      
471.      <guid>https://jens.mooseyard.com/2009/02/03/couch/</guid>
472.      <description>&lt;p&gt;I really don’t know how long I’ve been lying on the couch, watching the
473. men on the TV. I don’t remember things so well anymore, since the
474. accident. I don’t remember the accident either, but my friends tell me
475. it was pretty bad. I have healed about as well as I’m going to, and
476. though I don’t get around well, I can still think. In small doses.</p>
477. <p>The men on the TV gesticulate about some crisis or other; I can’t tell
478. what, because the sound is off. They look angry — at me, at all of us,
479. at themselves. Small text crawls across the screen above and below them.
480. The TV men look very tired, too, as tired as I feel, and perhaps lost
481. and afraid. I feel such sympathy; I would like to turn up the volume and
482. learn more of their situation. Maybe I could ask one of my friends to.&lt;/p&gt;</description>
483.    </item>
484.    
485.    <item>
486.      <title>“Interview With An Adware Developer”</title>
487.      <link>https://jens.mooseyard.com/2009/01/30/interview-with-an-adware-developer/</link>
488.      <pubDate>Fri, 30 Jan 2009 12:00:00 -0800</pubDate>
489.      
490.      <guid>https://jens.mooseyard.com/2009/01/30/interview-with-an-adware-developer/</guid>
491.      <description>Matt Knox, a Ruby developer and repentant former coder for an adware company, explains how adware works. Really fascinating stuff, and quite scary from a security point of view.
492. “At the same time, we also made a virtual process executable. I’ve never heard of anybody else doing this before. Windows has this thing called Create Remote Thread. Basically, the semantics of Create Remote Thread are: You’re a process, I’m a different process.</description>
493.    </item>
494.    
495.    <item>
496.      <title>Career update</title>
497.      <link>https://jens.mooseyard.com/2008/08/17/career-update/</link>
498.      <pubDate>Sun, 17 Aug 2008 12:00:00 -0800</pubDate>
499.      
500.      <guid>https://jens.mooseyard.com/2008/08/17/career-update/</guid>
501.      <description>FYI, I ended up taking the position at Google. I started two weeks ago, and it’s been quite exciting, despite (or because of) the “drinking from a fire-hose” aspect of learning my way around the big G.
502. I’m on the Google Sites team. I’ve been interested in wikis for years, and now I get to actually work on one. (Although Sites, née JotSpot, is not a typical wiki.)
503. I could write a lot about my experience of Google so far.</description>
504.    </item>
505.    
506.    <item>
507.      <title>That New-Cards Smell</title>
508.      <link>https://jens.mooseyard.com/2008/08/03/that-new-cards-smell/</link>
509.      <pubDate>Sun, 03 Aug 2008 12:00:00 -0800</pubDate>
510.      
511.      <guid>https://jens.mooseyard.com/2008/08/03/that-new-cards-smell/</guid>
512.      <description>My Decktet is a thing of beauty. I even printed &amp;amp; assembled the box (an activity that took me back to my happy childhood days of making paper polyhedra models.)
513. The only problem is that the cards still have a faint sickly-sweet stink of toluene and acetone (from the plastic coating) even after I left them spread out on the floor for a few days. It’s quite unpleasant, not like the nice smell of new books, cars or boardgames.</description>
514.    </item>
515.    
516.    <item>
517.      <title>I Made A Decktet</title>
518.      <link>https://jens.mooseyard.com/2008/08/01/i-made-a-decktet/</link>
519.      <pubDate>Fri, 01 Aug 2008 12:00:00 -0800</pubDate>
520.      
521.      <guid>https://jens.mooseyard.com/2008/08/01/i-made-a-decktet/</guid>
522.      <description>Sometimes it’s nice to make physical objects. It’s usually messier and more time-consuming than doing it on the computer, but in the end you have something you can actually touch.
523. Ever since I saw P. D. Magnus’s Decktet — a whimsical yet mysterious deck of cards for games or divination — I wanted one of my own. However, the Decktet is currently only available as a PDF, so any physical manifestation has to be of a DIY nature.</description>
524.    </item>
525.    
526.    <item>
527.      <title>BLIP news (Python! Detailed spec!)</title>
528.      <link>https://jens.mooseyard.com/2008/06/04/blip-news-python-detailed-spec/</link>
529.      <pubDate>Wed, 04 Jun 2008 12:00:00 -0800</pubDate>
530.      
531.      <guid>https://jens.mooseyard.com/2008/06/04/blip-news-python-detailed-spec/</guid>
532.      <description> I’ve now implemented BLIP in Python. That officially makes it cross-platform! If we get a third implementation, can we call it an “industry standard”? There’s some detailed protocol documentation, too. Also, on Steven Frank’s recommendation, I set up the Redmine project tracker on my website. It’s pretty slick! Kind of “Trac On Rails”.  </description>
533.    </item>
534.    
535.    <item>
536.      <title>BLIP-Protocol mailing list</title>
537.      <link>https://jens.mooseyard.com/2008/05/28/blip-protocol-mailing-list/</link>
538.      <pubDate>Wed, 28 May 2008 12:00:00 -0800</pubDate>
539.      
540.      <guid>https://jens.mooseyard.com/2008/05/28/blip-protocol-mailing-list/</guid>
541.      <description>I’ve created a BLIP-Protocol mailing list on Google Groups:
542. Please join up if you’re interested in learning, using, re-implementing, improving, extending…</description>
543.    </item>
544.    
545.    <item>
546.      <title>BLIP: Come ‘n’ get it!</title>
547.      <link>https://jens.mooseyard.com/2008/05/25/blip-come-n-get-it/</link>
548.      <pubDate>Sun, 25 May 2008 12:00:00 -0800</pubDate>
549.      
550.      <guid>https://jens.mooseyard.com/2008/05/25/blip-come-n-get-it/</guid>
551.      <description>I’ve released the source code to my “BLIP” protocol implementation, as part of a project I call “MYNetwork”, for “Mooseyard Networking Libraries”. API documentation is available online, and you can check out or browse the source code from its Mercurial repository. For the really curious, there’s even a sketchy overview of the protocol’s wire format.
552. It’s working quite well for me in Cloudy; it’s been a while since I’ve found any outright bugs, although I know there’s more work to do on performance and features.</description>
553.    </item>
554.    
555.    <item>
556.      <title>BLIP update</title>
557.      <link>https://jens.mooseyard.com/2008/05/16/blip-update/</link>
558.      <pubDate>Fri, 16 May 2008 12:00:00 -0800</pubDate>
559.      
560.      <guid>https://jens.mooseyard.com/2008/05/16/blip-update/</guid>
561.      <description>I’ve got my new BLIP protocol all implemented now. After my previous post on Monday:
562. On Tuesday I implemented message metadata. On Wednesday I got SSL working (configuring the “server” side to verify the “client’s” cert was difficult.) On Thursday I put Cloudy up on blocks, pried out Vortex and my Obj-C wrapper library, and replaced them with BLIP. And on Friday (today) I debugged.  Cloudy’s back up and running, and all its features work.</description>
563.    </item>
564.    
565.    <item>
566.      <title>The Fine Line Between Clever And Stupid</title>
567.      <link>https://jens.mooseyard.com/2008/05/12/the-fine-line-between-clever-and-stupid/</link>
568.      <pubDate>Mon, 12 May 2008 12:00:00 -0800</pubDate>
569.      
570.      <guid>https://jens.mooseyard.com/2008/05/12/the-fine-line-between-clever-and-stupid/</guid>
571.      <description>…and which side of that line am I on? Not in general; just in respect to my latest decision in Cloudy. It’s the old “make vs. buy” trade-off, or “write vs. reuse” in this case: do you go with an existing library, even if it’s problematic, or do you write your own implementation from scratch?
572. What am I talking about? The networking code in Cloudy. From the very beginning I wanted to use BEEP, a generic and flexible protocol for sending request/response messages over a socket.</description>
573.    </item>
574.    
575.    <item>
576.      <title>Stickies makes its music-video debut!</title>
577.      <link>https://jens.mooseyard.com/2008/05/11/stickies-makes-its-music-video-debut/</link>
578.      <pubDate>Sun, 11 May 2008 12:00:00 -0800</pubDate>
579.      
580.      <guid>https://jens.mooseyard.com/2008/05/11/stickies-makes-its-music-video-debut/</guid>
581.      <description>Stickies and I hadn’t spoken in a while, but it called me this morning to announce it’s made its acting debut in a music video! That was unexpected, to say the least, but it’s an exciting career move, and I had to congratulate it; it does a great job:
582. Stickies makes its entrance at 0:53, if you want to skip directly to it, but really the entire video (and song) are excellent.</description>
583.    </item>
584.    
585.    <item>
586.      <title>Cloudy Verification</title>
587.      <link>https://jens.mooseyard.com/2008/04/26/cloudy-verification/</link>
588.      <pubDate>Sat, 26 Apr 2008 12:00:00 -0800</pubDate>
589.      
590.      <guid>https://jens.mooseyard.com/2008/04/26/cloudy-verification/</guid>
591.      <description>Continuing from the previous Cloudy post … The first time you connect to someone, how do you establish that digital identifier you’re communicating with is the human being you think it is? This is surprisingly difficult to do, because it’s prone to what cryptographers call the “man-in-the-middle attack”.
592. (Those of you already wearing tinfoil hats can skip past the general explanation, down to “What Cloudy Does”.)
593. 1. A Quick Overview Of Verification Attacks.</description>
594.    </item>
595.    
596.    <item>
597.      <title>Cloudy Networking</title>
598.      <link>https://jens.mooseyard.com/2008/04/17/cloudy-networking/</link>
599.      <pubDate>Thu, 17 Apr 2008 12:00:00 -0800</pubDate>
600.      
601.      <guid>https://jens.mooseyard.com/2008/04/17/cloudy-networking/</guid>
602.      <description>Next I need to talk about networking; having an identity and minting certificates isn’t very interesting until you can connect to someone else.
603. Point-to-Point Communications. When one Cloudy peer wants to communicate with another one, it opens a TCP socket to its IP address —
604. [Hang on, there are two issues I suddenly glossed over in that last phrase. First, how did this peer find out the others’ IP address? These are just random computers, not servers, so they don’t have their own domain names or even stable addresses.</description>
605.    </item>
606.    
607.    <item>
608.      <title>Cloudy Identity</title>
609.      <link>https://jens.mooseyard.com/2008/04/15/cloudy-identity/</link>
610.      <pubDate>Tue, 15 Apr 2008 12:00:00 -0800</pubDate>
611.      
612.      <guid>https://jens.mooseyard.com/2008/04/15/cloudy-identity/</guid>
613.      <description>Continuing from the previous Cloudy post … At the root of Cloudy is the means for creating and establishing identity. A lot of peer-to-peer systems treat the peers mostly as interchangeable anonymous nodes, often deliberately so, but Cloudy is a social system.
614. Quick Crypto Recap. The identity and security layers of Cloudy are tightly intertwined, because identity without security is useless. And security is accomplished entirely through cryptography, because the centralized alternatives like locking all of your servers up in a closet don’t apply.</description>
615.    </item>
616.    
617.    <item>
618.      <title>Cloudy As Buzzwords</title>
619.      <link>https://jens.mooseyard.com/2008/04/13/cloudy-as-buzzwords/</link>
620.      <pubDate>Sun, 13 Apr 2008 12:00:00 -0800</pubDate>
621.      
622.      <guid>https://jens.mooseyard.com/2008/04/13/cloudy-as-buzzwords/</guid>
623.      <description>Continuing from Unstealthing, Incrementally. I have many ideas for applications, but most of them seem to rely on similar kinds of infrastructure, in particular a distributed, secure application-level messaging system. Unfortunately, this doesn’t really exist yet, at least not in any form that meets my needs.
624. What am I talking about here? More colloquially, it’s a mechanism for letting applications all over the network send messages to each other, without requiring a central server, and without allowing messages to be eavesdropped upon or faked.</description>
625.    </item>
626.    
627.    <item>
628.      <title>Unstealthing, Incrementally</title>
629.      <link>https://jens.mooseyard.com/2008/04/12/unstealthing-incrementally/</link>
630.      <pubDate>Sat, 12 Apr 2008 12:00:00 -0800</pubDate>
631.      
632.      <guid>https://jens.mooseyard.com/2008/04/12/unstealthing-incrementally/</guid>
633.      <description>I got about 14 minutes of fame back in January with a blog post, wherein I grumbled about (among other things) how I disliked Apple’s culture of secrecy, and announced that I’d left Apple to work on my own, unspecified, project. In the intervening three months, I haven’t said anything about what that project is, almost as though it were … secret.
634. The irony of this is not lost on me.</description>
635.    </item>
636.    
637.    <item>
638.      <title>Japanese Advertisers Discover Zooko’s Triangle</title>
639.      <link>https://jens.mooseyard.com/2008/03/26/japanese-advertisers-discover-zookos-triangle/</link>
640.      <pubDate>Wed, 26 Mar 2008 12:00:00 -0800</pubDate>
641.      
642.      <guid>https://jens.mooseyard.com/2008/03/26/japanese-advertisers-discover-zookos-triangle/</guid>
643.      <description>Cabel Sasser, of indie developer Panic, reports from Japan:
644. “Within minutes of riding on the first trains in Japan, I notice a significant change in advertising, from train to television. The trend? No more printed URLs. The replacement? Search boxes! With recommended search terms![]("“[*]":http://www.cabel.name/2008/03/japan-urls-are-totally-out.html )http://www.cabel.name/images-post/2008/03/search-2.jpg!
645. He goes on to note how common it is for people to type URLs or domain names into their browser’s search box instead of the address field.</description>
646.    </item>
647.    
648.    <item>
649.      <title>My Debt To Arthur C. Clarke</title>
650.      <link>https://jens.mooseyard.com/2008/03/23/my-debt-to-arthur-c.-clarke/</link>
651.      <pubDate>Sun, 23 Mar 2008 12:00:00 -0800</pubDate>
652.      
653.      <guid>https://jens.mooseyard.com/2008/03/23/my-debt-to-arthur-c.-clarke/</guid>
654.      <description>Arthur C. Clarke’s death hit me harder than other recent obituaries, even though it’s been decades since I read much by him. His were some of the first science fiction stories I read, at the age of ten or eleven; and for several years after that he was my favorite author.
655. I remember, during one of our long summer trips visiting the extended family in Germany, finding one of his story collections in the small English-language section of a public library.</description>
656.    </item>
657.    
658.    <item>
659.      <title>The Origin Of The iChat UI</title>
660.      <link>https://jens.mooseyard.com/2008/03/18/the-origin-of-the-ichat-ui/</link>
661.      <pubDate>Tue, 18 Mar 2008 12:00:00 -0800</pubDate>
662.      
663.      <guid>https://jens.mooseyard.com/2008/03/18/the-origin-of-the-ichat-ui/</guid>
664.      <description>&lt;p&gt;I had lost this historical document for a long time, but finally found
665. it the other day on an old backup CD. It’s the original 1997 sketch I
666. made of a chat user interface based on speech balloons.&lt;/p&gt;</description>
667.    </item>
668.    
669.    <item>
670.      <title>The Beauty Of 99¢ iPhone Apps</title>
671.      <link>https://jens.mooseyard.com/2008/03/07/the-beauty-of-99-iphone-apps/</link>
672.      <pubDate>Fri, 07 Mar 2008 12:00:00 -0800</pubDate>
673.      
674.      <guid>https://jens.mooseyard.com/2008/03/07/the-beauty-of-99-iphone-apps/</guid>
675.      <description>&lt;p&gt;After digesting yesterday’s iPhone announcements [with fava beans and a
676. nice Chianti] I started thinking about the pricing models made possible
677. by the “Application Store”. In particular,</p>
678. <h2 id="how-cheap-can-an-iphone-app-be">How cheap can an iPhone app be?</h2>
679. <p>I think the answer’s clear. The Application Store will obviously be
680. based on the iTunes store, whose bread-and-butter is a product, the AAC
681. audio file, that sells for … 99¢. Apple’s clearly able to make a profit
682. at that price point, despite credit-card processing fees, bandwidth
683. costs, and comparable payments <em>[Updated. Thanks, Dru!]</em> to the record
684. labels. So I see no reason they wouldn’t allow a developer to price an
685. application that low.</p>
686. <p>But why would a developer <em>want</em> to sell an application for a net 70¢?</p>
687. <h2 id="micropayments">Micropayments</h2>
688. <p>Because at such a low price, with a one-click store a couple of taps
689. away, it becomes an impulse purchase. It’s a form of
690. <a href="http://en.wikipedia.org/wiki/Micropayment">micropayment</a>, an idea
691. that’s been talked about for years but hasn’t widely taken off due to
692. the practical difficulties of collecting very small payments. The few
693. areas where micropayments (albeit larger than the canonical 1/10¢
694. originally proposed) have worked include the iTunes store, and the
695. downloadable-game stores for the Xbox and Wii.</p>
696. <p>And let’s not forget the most amazing example of what people will pay
697. for if you make it convenient enough: <em>ringtones</em>. The practice of
698. charging suckers $2 for a 30-second snippet of a song they already
699. have, is a multi-billion-dollar industry.&lt;/p&gt;</description>
700.    </item>
701.    
702.    <item>
703.      <title>Systems</title>
704.      <link>https://jens.mooseyard.com/2008/03/02/systems/</link>
705.      <pubDate>Sun, 02 Mar 2008 12:00:00 -0800</pubDate>
706.      
707.      <guid>https://jens.mooseyard.com/2008/03/02/systems/</guid>
708.      <description>The last paragraph of the poem “Systems” by Kristy Bowen:
709. “… I try to write a poem I wouldn’t want to sleep with. Would kick to the curb, wrap my thumbs around her slender neck and snap. This one’s still babied, blinking, wondering if it wants to be a skirt or a tire iron. Licking the perimeter of opened envelopes for a tiny bit of sweet. My nouns go awry every time I stop paying attention.</description>
710.    </item>
711.    
712.    <item>
713.      <title>hash musings</title>
714.      <link>https://jens.mooseyard.com/2008/02/19/hash-musings/</link>
715.      <pubDate>Tue, 19 Feb 2008 12:00:00 -0800</pubDate>
716.      
717.      <guid>https://jens.mooseyard.com/2008/02/19/hash-musings/</guid>
718.      <description>I’ve been thinking about writing an essay about the beauty &amp;amp; weirdness of cryptographic hash functions. The way any digitized data, however huge, can be named by a short fixed-size binary string. The way there are in theory an infinite number of hash collisions, but in practice zero. I was talking to myself about it, this morning, and two quotes appeared, which I write down here to remember:
719. “Hashing is my favorite computer-science concept.</description>
720.    </item>
721.    
722.    <item>
723.      <title>Black Button, Black Box</title>
724.      <link>https://jens.mooseyard.com/2008/02/06/black-button-black-box/</link>
725.      <pubDate>Wed, 06 Feb 2008 12:00:00 -0800</pubDate>
726.      
727.      <guid>https://jens.mooseyard.com/2008/02/06/black-button-black-box/</guid>
728.      <description>I just ran across Invisible Games, a website of short and enigmatic fictions. One of them, The Loneliness Engine, reminds me of my own short-n-enigmatic We [Had Black Boxes]. No spooky synchronicity or anything, but they seem to belong together somehow … which itself fits in with the themes of both stories. Neat.</description>
729.    </item>
730.    
731.    <item>
732.      <title>Network Barbie Says “Asynchrony Is Hard!”</title>
733.      <link>https://jens.mooseyard.com/2008/02/06/network-barbie-says-asynchrony-is-hard/</link>
734.      <pubDate>Wed, 06 Feb 2008 12:00:00 -0800</pubDate>
735.      
736.      <guid>https://jens.mooseyard.com/2008/02/06/network-barbie-says-asynchrony-is-hard/</guid>
737.      <description>You can’t avoid asynchrony when writing network code, since operations can take an arbitrary amount of time, and often do. To keep the app responsive it has to be able to get other things done while a slow operation is in progress.
738. My first exposure to network programming was in Java, whose approach to asynchrony is to use threads. Lots of ’em. The API calls are [almost] all blocking, so you run them on background threads.</description>
739.    </item>
740.    
741.    <item>
742.      <title>3 Weeks</title>
743.      <link>https://jens.mooseyard.com/2008/01/24/3-weeks/</link>
744.      <pubDate>Thu, 24 Jan 2008 12:00:00 -0800</pubDate>
745.      
746.      <guid>https://jens.mooseyard.com/2008/01/24/3-weeks/</guid>
747.      <description>I’ve been on my own for three weeks now, and I’m definitely enjoying it. I know that one of the general issues with self-employment is whether one can stay motivated without the external structure imposed by The Man. Fortunately I seem to have no problem with this — I’ve been coding at top speed. Mostly I work in the detached office, which is now clean and cozy, but sometimes I hang out on the couch in the living room.</description>
748.    </item>
749.    
750.    <item>
751.      <title>FakeSteved!</title>
752.      <link>https://jens.mooseyard.com/2008/01/24/fakesteved/</link>
753.      <pubDate>Thu, 24 Jan 2008 12:00:00 -0800</pubDate>
754.      
755.      <guid>https://jens.mooseyard.com/2008/01/24/fakesteved/</guid>
756.      <description>I used to think it was the Big Time if I got a link from Daring Fireball, but now someone just pointed out to me that the Fake Steve Jobs has taken note of my post.
757. So … what does it mean for my post to be criticized by a fictional construct that embodies a parody of the CEO of the very same ex-employer my post criticizes? Especially when, more specifically, that fictional construct’s humor is largely based on an exaggerated inversion of Apple’s carefully-groomed non-blogging public image, and he calls out a quote of mine that decries exactly the situation that his (fictional) presence repudiates?</description>
758.    </item>
759.    
760.    <item>
761.      <title>Gone Indie</title>
762.      <link>https://jens.mooseyard.com/2008/01/10/gone-indie/</link>
763.      <pubDate>Thu, 10 Jan 2008 12:00:00 -0800</pubDate>
764.      
765.      <guid>https://jens.mooseyard.com/2008/01/10/gone-indie/</guid>
766.      <description>&lt;p&gt;Here’s a career update, for those of you who care: I’ve left Apple, and
767. I’m now working on my own, from home, as an indie software developer. I
768. have plans for at least two kick-ass Mac apps, I’ll probably contribute
769. to a few open source projects, and I may dabble in some web stuff.</p>
770. <p>(At least, that’s the plan for now! Everything is subject to change
771. without prior notice. This document contains forward-looking statements.
772. These statements involve risks and uncertainties, and actual results may
773. differ.)</p>
774. <p>This is kind of a big change for me. I’ve been continuously employed for
775. 19 years, 16 of those at Apple. I clearly like being part of a team,
776. part of a company, and specifically part of Apple. But there comes a
777. time when a man’s gotta do what a man’s gotta do.&lt;/p&gt;</description>
778.    </item>
779.    
780.    <item>
781.      <title>GeekGameBoard</title>
782.      <link>https://jens.mooseyard.com/2007/12/20/geekgameboard/</link>
783.      <pubDate>Thu, 20 Dec 2007 12:00:00 -0800</pubDate>
784.      
785.      <guid>https://jens.mooseyard.com/2007/12/20/geekgameboard/</guid>
786.      <description>Santa has an early Xmas present for all you good Leopard programmers: GeekGameBoard, a new piece of sample code by the anonymous engineer elves at Apple.
787. [Update: GeekGameBoard is now an open-source project hosted at bitbucket.org
788. GeekGameBoard is an example of using Core Animation to present the user interface of a board or card game. It implements a small framework for implementing such games, with domain-specific classes like “Grid” and “Piece”, and examples of several game definitions built on top of the framework.</description>
789.    </item>
790.    
791.    <item>
792.      <title>The Gnostic argument for agnosticism</title>
793.      <link>https://jens.mooseyard.com/2007/12/10/the-gnostic-argument-for-agnosticism/</link>
794.      <pubDate>Mon, 10 Dec 2007 12:00:00 -0800</pubDate>
795.      
796.      <guid>https://jens.mooseyard.com/2007/12/10/the-gnostic-argument-for-agnosticism/</guid>
797.      <description>In some online forums I list as interests both gnosticism and agnosticism, which is a bit of a joke since the two words are literally contradictory, but is true in that both are interesting and important to me. Agnosticism as my attitude toward religion: that the existence of a God or gods is fundamentally unknowable, undecidable, unprovable. Gnosticism as a mystic tradition, a suppressed early fork of Christianity, whose beliefs have more recently had a large impact on the literature of the fantastic and on postmodern philosophy (notably Philip K.</description>
798.    </item>
799.    
800.    <item>
801.      <title>AppleScript team photo, 1993</title>
802.      <link>https://jens.mooseyard.com/2007/12/03/applescript-team-photo-1993/</link>
803.      <pubDate>Mon, 03 Dec 2007 12:00:00 -0800</pubDate>
804.      
805.      <guid>https://jens.mooseyard.com/2007/12/03/applescript-team-photo-1993/</guid>
806.      <description>&lt;p&gt;Warren just emailed me this photo, commemorating the release of the
807. first Apple product I worked on. That’s me on the second row, second
808. from the right, with the dopey expression (but no gray hairs.)&lt;/p&gt;</description>
809.    </item>
810.    
811.    <item>
812.      <title>Facebook and Decentralized Identifiers</title>
813.      <link>https://jens.mooseyard.com/2007/12/02/facebook-and-decentralized-identifiers/</link>
814.      <pubDate>Sun, 02 Dec 2007 12:00:00 -0800</pubDate>
815.      
816.      <guid>https://jens.mooseyard.com/2007/12/02/facebook-and-decentralized-identifiers/</guid>
817.      <description>I finally made myself a Facebook account, mostly to see what it’s like. Overall, I’m pretty impressed: the UI is nicer than most such sites, particularly the still-antiquated LiveJournal and the disaster that is MySpace. The biggest issue there seems to be that the main profile page absolutely doesn’t scale up to handle the exploding number of apps/widgets people are stuffing into it, so you end up with mile-long profiles containing box after box of junk.</description>
818.    </item>
819.    
820.    <item>
821.      <title>Holding a Program in One’s Head</title>
822.      <link>https://jens.mooseyard.com/2007/08/27/holding-a-program-in-ones-head/</link>
823.      <pubDate>Mon, 27 Aug 2007 12:00:00 -0800</pubDate>
824.      
825.      <guid>https://jens.mooseyard.com/2007/08/27/holding-a-program-in-ones-head/</guid>
826.      <description>&lt;p&gt;Paul Graham [who is obnoxiously elitist, but frequently insightful] has
827. a new essay, “<!-- raw HTML omitted -->Holding a
828. Program in One’s Head<!-- raw HTML omitted -->”, that is making me feel sad this morning.</p>
829. &lt;!-- raw HTML omitted --&gt;</description>
830.    </item>
831.    
832.    <item>
833.      <title>The Hero Passes</title>
834.      <link>https://jens.mooseyard.com/2007/08/06/the-hero-passes/</link>
835.      <pubDate>Mon, 06 Aug 2007 12:00:00 -0800</pubDate>
836.      
837.      <guid>https://jens.mooseyard.com/2007/08/06/the-hero-passes/</guid>
838.      <description>&lt;blockquote&gt;
839. <p>We love to play the Hero — exploring dungeons, grabbing treasure,
840. saving the world from evil. But I started wondering about the reasons
841. behind some of the actions in such games, and especially about what my
842. Heroic deeds looked like to the ordinary people of the lands I passed
843. through. (As my wife once put it: “Why isn’t there a Hug button?”) The
844. result is this story.<br>
845. I don’t normally write this sort of antiquated prose, but the genre
846. does require it. It was actually a fun exercise, and I’ve tried to
847. affect more of a <a href="http://en.wikipedia.org/wiki/James_Branch_Cabell">James Branch
848. Cabell</a> or <a href="http://en.wikipedia.org/wiki/Lord_Dunsany">Lord
849. Dunsany</a> voice, rather than
850. the tiresome faux-Tolkien of most current heroic fantasy.</p>
851. &lt;/blockquote&gt;</description>
852.    </item>
853.    
854.    <item>
855.      <title>Hang on, I gotta take a call from the Archdemon Azazael</title>
856.      <link>https://jens.mooseyard.com/2007/07/18/hang-on-i-gotta-take-a-call-from-the-archdemon-azazael/</link>
857.      <pubDate>Wed, 18 Jul 2007 12:00:00 -0800</pubDate>
858.      
859.      <guid>https://jens.mooseyard.com/2007/07/18/hang-on-i-gotta-take-a-call-from-the-archdemon-azazael/</guid>
860.      <description>37signals gripes about those annoying Bluetooth cellphone headsets with even-more-annoying blinky LEDs on them.
861. I once had the idea of a charity that would collect discarded headsets from yuppies and distribute them to mentally ill homeless people. Just by wearing the headsets, they would eliminate the social stigma attached to talking to themselves on the street; this would help re-integrate them into society.</description>
862.    </item>
863.    
864.    <item>
865.      <title>How not to fix buffer overflows</title>
866.      <link>https://jens.mooseyard.com/2007/07/16/how-not-to-fix-buffer-overflows/</link>
867.      <pubDate>Mon, 16 Jul 2007 12:00:00 -0800</pubDate>
868.      
869.      <guid>https://jens.mooseyard.com/2007/07/16/how-not-to-fix-buffer-overflows/</guid>
870.      <description>This tale of woe is making me rethink whether I want to be running any PHP-based software on my website.
871. Yes, integer overflows happen to the best of us (even those of us who write popular algorithm textbooks), but I would hope that once one is pointed out, the people maintaining the code would have a clue about how to fix it.
872. Stuff like “if (size&amp;gt;INT_MAX)…” is funny, but I find it even scarier that someone would think the solution to integer overflow is to store potentially-huge byte counts in variables of type “float”.</description>
873.    </item>
874.    
875.    <item>
876.      <title>Apricot Jam Recipe</title>
877.      <link>https://jens.mooseyard.com/2007/07/07/apricot-jam-recipe/</link>
878.      <pubDate>Sat, 07 Jul 2007 12:00:00 -0800</pubDate>
879.      
880.      <guid>https://jens.mooseyard.com/2007/07/07/apricot-jam-recipe/</guid>
881.      <description>&lt;p&gt;Here’s my family recipe for apricot jam, handed down through
882. generations. One generation, really — my mom got it from a pamphlet put
883. out by some local womens’ group, after we moved to an old ramshackle
884. house in the middle of a huge but disused apricot orchard. The trees
885. were old, but a lot of them still produced fruit, and it was no trouble
886. to walk around and collect bucketsful. So we needed some way to make use
887. of all that fruit…</p>
888. <p>This recipe is different from the usual one you find packed in a box of
889. pectin, because, well, it doesn’t use pectin. Instead, you thicken the
890. jam by cooking it a lot longer. This means it tastes less like fresh
891. fruit; but it has a wonderful taste of its own, a bit like dried
892. apricots, and a nice gloopy texture. As a bonus, putting an apricot
893. kernel&lt;sup id=&#34;fnref:1&#34;&gt;&lt;a href=&#34;#fn:1&#34; class=&#34;footnote-ref&#34; role=&#34;doc-noteref&#34;&gt;1&lt;/a&gt;&lt;/sup&gt; in every jar gradually adds an almond-y aroma&lt;sup id=&#34;fnref:2&#34;&gt;&lt;a href=&#34;#fn:2&#34; class=&#34;footnote-ref&#34; role=&#34;doc-noteref&#34;&gt;2&lt;/a&gt;&lt;/sup&gt;.&lt;/p&gt;</description>
894.    </item>
895.    
896.    <item>
897.      <title>“Cut The Lights”</title>
898.      <link>https://jens.mooseyard.com/2007/05/26/cut-the-lights/</link>
899.      <pubDate>Sat, 26 May 2007 12:00:00 -0800</pubDate>
900.      
901.      <guid>https://jens.mooseyard.com/2007/05/26/cut-the-lights/</guid>
902.      <description>This is a mix of post-punk (old and new). I made it about a month and a half ago, but hadn’t put together a cover until today. Now it’s ready…
903. [web page] [MP3] [more mixes]</description>
904.    </item>
905.    
906.    <item>
907.      <title>Uncle Jens’s Coding Tips</title>
908.      <link>https://jens.mooseyard.com/2007/05/06/uncle-jenss-coding-tips/</link>
909.      <pubDate>Sun, 06 May 2007 12:00:00 -0800</pubDate>
910.      
911.      <guid>https://jens.mooseyard.com/2007/05/06/uncle-jenss-coding-tips/</guid>
912.      <description>&lt;p&gt;Ever since Brent “NetNewsWire” Simmons posted his &lt;a href=&#34;http://inessential.com/2007/04/25.php&#34;&gt;Thoughts On Large
913. Cocoa Projects</a> the other week,
914. I’ve wanted to add some of my own tips. I’ve worked on some big projects
915. (iChat, Apple’s Java runtime, OpenDoc) and have sometimes had to find my
916. way around in others (Safari, Mail), so I know what Brent means when he
917. says:</p>
918. <blockquote>
919. <p>There’s no way I can remember, with any level of detail, how every
920. part of [my app] works. I call it the Research Barrier, when an app is
921. big enough that the developer sometimes has to do research to figure
922. things out…</p>
923. </blockquote>
924. <p>It’s been said many times that “the main person you’re writing comments
925. for is yourself, six months in the future.” It’s always a good idea to
926. keep that shadowy figure in mind while you code. Here are some other
927. techniques I’ve found invaluable:&lt;/p&gt;</description>
928.    </item>
929.    
930.    <item>
931.      <title>Computer Science’s Image Problem</title>
932.      <link>https://jens.mooseyard.com/2007/04/16/computer-sciences-image-problem/</link>
933.      <pubDate>Mon, 16 Apr 2007 12:00:00 -0800</pubDate>
934.      
935.      <guid>https://jens.mooseyard.com/2007/04/16/computer-sciences-image-problem/</guid>
936.      <description>NYT: Computer Science Takes Steps to Bring Women to the FoldI find this article baffling and the comments on itaggravating.
937. “The nerd factor is huge,” Dr. Cuny said. … This image discourages members of both sexes, but the problem seems to be more prevalent among women. ‘They think of it as programming,’ Dr. Cuny said. ‘They don’t think of it as revolutionizing the way we are going to do medicine or create synthetic molecules or study our impact on the climate of the earth.</description>
938.    </item>
939.    
940.    <item>
941.      <title>Masculine And Feminine In Operating Systems</title>
942.      <link>https://jens.mooseyard.com/2007/03/18/masculine-and-feminine-in-operating-systems/</link>
943.      <pubDate>Sun, 18 Mar 2007 12:00:00 -0800</pubDate>
944.      
945.      <guid>https://jens.mooseyard.com/2007/03/18/masculine-and-feminine-in-operating-systems/</guid>
946.      <description>My friend Tanya is a gateway to the strange and exotic worlds of fan- and slash-fiction. Today she pointed out a whole LiveJournal community, mac_hearts_pc, devoted to mostly-smutty extrapolations of Apple’s anthropomorphized Mac-vs-PC ads. Wow.
947. In her post about this, she says
948. “I tend to think of Macs as so feminine as to be, well, female”which is really making me think…
949. How do we map computer behaviors onto ‘male’ and ‘female’?</description>
950.    </item>
951.    
952.    <item>
953.      <title>Haiku Archives</title>
954.      <link>https://jens.mooseyard.com/2007/03/04/haiku-archives/</link>
955.      <pubDate>Sun, 04 Mar 2007 12:00:00 -0800</pubDate>
956.      
957.      <guid>https://jens.mooseyard.com/2007/03/04/haiku-archives/</guid>
958.      <description>2001 Figs cover the ground
959. The children step over them
960. Or sometimes they don’t
961. A hug and a kiss
962. A heart outlined with fingers
963. And a wave goodbye
964. To the very end
965. of the quivering green branch
966. clings a black squirrel
967. So much depends on
968. a red Mario beanie
969. left out on the lawn.
970. Yellow leaves dancing
971. in the air, two stories up
972. against green windows.
973. I cannot get up.</description>
974.    </item>
975.    
976.    <item>
977.      <title>Music (Prologue)</title>
978.      <link>https://jens.mooseyard.com/2007/02/18/music-prologue/</link>
979.      <pubDate>Sun, 18 Feb 2007 12:00:00 -0800</pubDate>
980.      
981.      <guid>https://jens.mooseyard.com/2007/02/18/music-prologue/</guid>
982.      <description>&lt;p&gt;The problem with &lt;a href=&#34;https://jens.mooseyard.com/Jens/2007/01/in-which-i-think-about-java-again-but-only-for-a-moment/&#34;&gt;writing about something I
983. dislike</a>
984. is that, after the momentary pleasure of getting it off your chest,
985. there’s not a lot of motivation to read people’s responses (especially
986. the argumentative ones.) Better to pick as a topic something that I <em>do</em>
987. like very much … such as music.</p>
988. <p>I can’t claim to be an expert on music: I can only barely play an
989. instrument, my dj skills are wack, the theory hurts my brain, and my
990. knowledge is encyclopedic only in a few micro-genres. But I’m rabidly
991. enthusiastic about it; and fortunately, music nowadays is tightly
992. entangled with computer technology, which (like any engineer) I <em>can</em>
993. easily sound like an expert on.&lt;/p&gt;</description>
994.    </item>
995.    
996.    <item>
997.      <title>Computer Psychosis</title>
998.      <link>https://jens.mooseyard.com/2007/02/02/computer-psychosis/</link>
999.      <pubDate>Fri, 02 Feb 2007 12:00:00 -0800</pubDate>
1000.      
1001.      <guid>https://jens.mooseyard.com/2007/02/02/computer-psychosis/</guid>
1002.      <description>“I have verified that I can create a sound file that can wake Vista speech recognition, open Windows Explorer, delete the documents folder, and then empty the trash.”
1003. — George Ou, ZDNet
1004. Sounds like computer psychosis to me. “I’m sorry, Dave, but I can’t open that. The voices told me to delete all of your files.”</description>
1005.    </item>
1006.    
1007.    <item>
1008.      <title>So Many Fonts, So Little Print</title>
1009.      <link>https://jens.mooseyard.com/2007/01/23/so-many-fonts-so-little-print/</link>
1010.      <pubDate>Tue, 23 Jan 2007 12:00:00 -0800</pubDate>
1011.      
1012.      <guid>https://jens.mooseyard.com/2007/01/23/so-many-fonts-so-little-print/</guid>
1013.      <description>I went on a free-font-downloading bender last weekend. I still love typography, and I’m glad to see the arcane art of type design isn’t dying out. Back in the old days of Desktop Publishing, you had a choice between high-quality but expensive fonts from reputable foundries, or a bunch of cheap but crappy knockoffs done in Fontographer.
1014. But now, thanks to mass amateurization, there are people who actually know what they’re doing, who design new typefaces for the fun of it and give them away.</description>
1015.    </item>
1016.    
1017.    <item>
1018.      <title>In Which I Think About Java Again, But Only For A Moment</title>
1019.      <link>https://jens.mooseyard.com/2007/01/21/in-which-i-think-about-java-again-but-only-for-a-moment/</link>
1020.      <pubDate>Sun, 21 Jan 2007 12:00:00 -0800</pubDate>
1021.      
1022.      <guid>https://jens.mooseyard.com/2007/01/21/in-which-i-think-about-java-again-but-only-for-a-moment/</guid>
1023.      <description>It’s amusing how Steve Jobs’ remarks disparaging the idea of Java on the iPhone have ignited controversy. His point was, obviously, that the iPhone’s browser won’t support Java applets; which is a no-brainer because applets were killed dead-dead-dead by Flash and Ajax. But this seems to have riled up everyone who still cares about non-server-based Java, leading to the weird situation of seeing “Java” and “Mac” in the same sentence again*.</description>
1024.    </item>
1025.    
1026.    <item>
1027.      <title>Ozone</title>
1028.      <link>https://jens.mooseyard.com/2006/10/09/ozone/</link>
1029.      <pubDate>Mon, 09 Oct 2006 12:00:00 -0800</pubDate>
1030.      
1031.      <guid>https://jens.mooseyard.com/2006/10/09/ozone/</guid>
1032.      <description>I’ve always picked at my nails, bitten them, the cuticles too. A sign of nervousness, I know, and unsightly and unsanitary. Can’t help it, though. The nails, fingertips, are always growing, always in different configurations, and some of those configurations are just wrong, asymmetrical, with sharp bits sticking out. And I can’t leave those alone: I always think in the moment that I can peel off the wrong part and leave the nail smooth and right.</description>
1033.    </item>
1034.    
1035.    <item>
1036.      <title>Only Known Instance Of Zork Slash</title>
1037.      <link>https://jens.mooseyard.com/2006/05/05/only-known-instance-of-zork-slash/</link>
1038.      <pubDate>Fri, 05 May 2006 12:00:00 -0800</pubDate>
1039.      
1040.      <guid>https://jens.mooseyard.com/2006/05/05/only-known-instance-of-zork-slash/</guid>
1041.      <description>My friend Tanya asked her friends to write her a short bit of Slash fictionas a birthday present. Which is not something I’m accustomed to, but here goes…
1042. >N
1043. The Troll Room
1044. This is a small room with passages to the east and south and a forbidding hole leading west. Bloodstains and deep scratches (perhaps made by an axe) mar the walls.
1045. A nasty-looking troll, brandishing a bloody axe, blocks all passages out of the room.</description>
1046.    </item>
1047.    
1048.    <item>
1049.      <title>your sword is glowing with a faint blue glow</title>
1050.      <link>https://jens.mooseyard.com/2006/05/01/your-sword-is-glowing-with-a-faint-blue-glow/</link>
1051.      <pubDate>Mon, 01 May 2006 12:00:00 -0800</pubDate>
1052.      
1053.      <guid>https://jens.mooseyard.com/2006/05/01/your-sword-is-glowing-with-a-faint-blue-glow/</guid>
1054.      <description>I dabbled in Interactive Fiction, aka Text Adventures, long ago —- I played Adventure on my Apple ][ and Dungeon/Zork on a VAX; I wrote a primitive game in BASIC and later in college partially implemented a language for building games in yacc; and then after graduating, my first serious Mac program was a souped-up and nearly finished version of that language. After that I was too busy with “real” jobs, but others kept the flame alive even after Infocom tanked, building their own adventure-design languages like TADS and Inform and spawning a cult scene of increasing complexity and literary merit.</description>
1055.    </item>
1056.    
1057.    <item>
1058.      <title>Multisensory CPU meter</title>
1059.      <link>https://jens.mooseyard.com/2006/03/28/multisensory-cpu-meter/</link>
1060.      <pubDate>Tue, 28 Mar 2006 12:00:00 -0800</pubDate>
1061.      
1062.      <guid>https://jens.mooseyard.com/2006/03/28/multisensory-cpu-meter/</guid>
1063.      <description>It just occurred to me that my newish MacBook gives me no less than four sensory modalities for detecting high CPU usage:
1064. The scrolling bar-graphs [one per CPU] of the Activity Monitor icon in the Dock The unobtrusive little purring fan that comes on every few seconds after the CPU’s been busy for a while The extra warmth of the computer against my palms and lap (I won’t say it gets “hot”; maybe “toasty”.</description>
1065.    </item>
1066.    
1067.    <item>
1068.      <title>The Ballad Of badtz-maru</title>
1069.      <link>https://jens.mooseyard.com/2006/01/10/the-ballad-of-badtz-maru/</link>
1070.      <pubDate>Tue, 10 Jan 2006 12:00:00 -0800</pubDate>
1071.      
1072.      <guid>https://jens.mooseyard.com/2006/01/10/the-ballad-of-badtz-maru/</guid>
1073.      <description>&lt;p&gt;I had a &lt;a href=&#34;http://206.14.132.88/products/Travla/c138/C138.html&#34;&gt;tiny Linux
1074. box</a><br>
1075. Its name was <a href="http://www.badtzmaru.com/">badtz-maru</a> ;<br>
1076. It sat out in the office<br>
1077. <a href="http://www.slimdevices.com/su_downloads.html">Serving tunes</a> for me and
1078. you.</p>
1079. <p>One day the <a href="http://www.slimdevices.com/su_downloads.html">Squeezebox</a>
1080. just went black!<br>
1081. I didn’t know what to do!<br>
1082. Safari, ssh and ping<br>
1083. Lost touch with badtz-maru.<br>
1084. The living room was silent<br>
1085. (Between games of
1086. &lt;a href=&#34;http://cube.ign.com/articles/656/656659p1.html&#34;&gt;Pikachu&lt;/a&gt;).&lt;/p&gt;</description>
1087.    </item>
1088.    
1089.    <item>
1090.      <title>Just Like The Cool Kids</title>
1091.      <link>https://jens.mooseyard.com/2006/01/07/just-like-the-cool-kids/</link>
1092.      <pubDate>Sat, 07 Jan 2006 12:00:00 -0800</pubDate>
1093.      
1094.      <guid>https://jens.mooseyard.com/2006/01/07/just-like-the-cool-kids/</guid>
1095.      <description>&lt;p&gt;Like most geeks, as a kid I not only despised the Cool Kids, but also
1096. wanted to be one of them too. My own school-age development trajectory
1097. took me from a state of total ignorance of what that required<sup id="fnref:1"><a href="#fn:1" class="footnote-ref" role="doc-noteref">1</a></sup>, to
1098. brave attempts to fit in<sup id="fnref:2"><a href="#fn:2" class="footnote-ref" role="doc-noteref">2</a></sup>, to a realization that different was
1099. cool<sup id="fnref:3"><a href="#fn:3" class="footnote-ref" role="doc-noteref">3</a></sup>.</p>
1100. <p>Anyway: these days being a Cool Kid is within every geek’s reach.
1101. Perhaps that’s because the shared culture has exploded into an
1102. uncountable number of fragments, each of which is a tribe with its own
1103. parallel hierarchies of coolness. Amen to that.&lt;/p&gt;</description>
1104.    </item>
1105.    
1106.    <item>
1107.      <title>Jens’s Tangled Job History</title>
1108.      <link>https://jens.mooseyard.com/2005/12/02/jenss-tangled-job-history/</link>
1109.      <pubDate>Fri, 02 Dec 2005 12:00:00 -0800</pubDate>
1110.      
1111.      <guid>https://jens.mooseyard.com/2005/12/02/jenss-tangled-job-history/</guid>
1112.      <description>&lt;p&gt;I write code for a living. After all these years I still find it really
1113. exciting — I was instantly and permanently addicted at age 11, it’s just
1114. that the programs have gone from 20-line BASIC powers-of-two table
1115. printers, to enormous Java and Objective-C juggernauts — and moreover
1116. I’ve found it’s the one thing that I can work on consistently enough
1117. over a long period of time to finish a project of any size. My childhood
1118. was littered with unfinished stories, unfinished plans for undersea
1119. cities, unfinished D&D maps. But the programs got finished. (Most of the
1120. time.)</p>
1121. <p>Herewith, entirely too much detail about the different programs people
1122. have paid me to write. Read on if you want, but you’re in the driver’s
1123. seat so feel free to hit that Back button if your eyes glaze
1124. over…&lt;/p&gt;</description>
1125.    </item>
1126.    
1127.    <item>
1128.      <title>Lesser-known scripting languages</title>
1129.      <link>https://jens.mooseyard.com/2005/06/29/lesser-known-scripting-languages/</link>
1130.      <pubDate>Wed, 29 Jun 2005 12:00:00 -0800</pubDate>
1131.      
1132.      <guid>https://jens.mooseyard.com/2005/06/29/lesser-known-scripting-languages/</guid>
1133.      <description>&lt;p&gt;Just when it seemed, a decade ago, that the programming world had
1134. settled on C++ as the <em>lingua franca</em>, the One Language To Rule Them
1135. All, instead we got an explosion of new high-level languages that have
1136. risen to popularity. Why did this happen? Chiefly because the World-Wide
1137. Web has conditioned users to expect five-second delays before any
1138. responses to their actions, which provides an environment ideally suited
1139. for interpreted, garbage-collected scripting languages. This movement
1140. has been encouraged by server vendors like Sun and IBM who are eager to
1141. show Web developers the productivity increases they can get by using
1142. such languages, especially after they then install massively powerful
1143. servers.&lt;/p&gt;</description>
1144.    </item>
1145.    
1146.    <item>
1147.      <title>Lua and unique strings</title>
1148.      <link>https://jens.mooseyard.com/2005/06/28/lua-and-unique-strings/</link>
1149.      <pubDate>Tue, 28 Jun 2005 12:00:00 -0800</pubDate>
1150.      
1151.      <guid>https://jens.mooseyard.com/2005/06/28/lua-and-unique-strings/</guid>
1152.      <description>Lua is an interesting scripting language. I can’t say I have much familiarity with it; I’ve only read the book, and a couple of papers, and downloaded and built the interpreter (which takes less than a minute). But what I’ve seen of it gives me a warm feeling, like reading a concise little poem, a haiku. It’s a small language, but what’s there is well-considered, and it appears that you can build bigger things (like object models, whether class- or prototype-based) out of its building blocks pretty easily.</description>
1153.    </item>
1154.    
1155.    <item>
1156.      <title>Little Boxes Of Words</title>
1157.      <link>https://jens.mooseyard.com/2005/06/15/little-boxes-of-words/</link>
1158.      <pubDate>Wed, 15 Jun 2005 12:00:00 -0800</pubDate>
1159.      
1160.      <guid>https://jens.mooseyard.com/2005/06/15/little-boxes-of-words/</guid>
1161.      <description>&lt;p&gt;Much of what I’m consumed with (at work) boils down to a question of:
1162. what is the right <!-- raw HTML omitted -->shape<!-- raw HTML omitted --> for the small but plentiful bits of
1163. writing that we are all creating daily? Here <!-- raw HTML omitted -->shape<!-- raw HTML omitted --> means largely
1164. visual representation but also sequencing and topology.</p>
1165. <p>It’s a problem of hypertext, primarily. The World Wide Web established
1166. one shape for hypertext: individual pages with one-way links in the
1167. text, replacing one another in a back-forwards chain. It’s proven to be
1168. a pretty good shape, but it’s not the only one, and earlier thinkers
1169. like Engelbart and Nelson had lots of other ideas.&lt;/p&gt;</description>
1170.    </item>
1171.    
1172.    <item>
1173.      <title>For Alba</title>
1174.      <link>https://jens.mooseyard.com/2005/02/13/for-alba/</link>
1175.      <pubDate>Sun, 13 Feb 2005 12:00:00 -0800</pubDate>
1176.      
1177.      <guid>https://jens.mooseyard.com/2005/02/13/for-alba/</guid>
1178.      <description>Not pink yet, she: bloody red.
1179. Not one to be held back, she, even by the host’s noose,
1180. even by constraints of brute geometry.
1181. Her universe distended, tore and bled for her.
1182. Thus the advent of the smallest unstoppable force:
1183. wee Alba hurled through the plate glass into life,
1184. now fixes us with a blue gaze,
1185. her raised arms encompassing it all,
1186. and says “I am an old soul. I’m back now.</description>
1187.    </item>
1188.    
1189.    <item>
1190.      <title>Anagrams</title>
1191.      <link>https://jens.mooseyard.com/2004/05/19/anagrams/</link>
1192.      <pubDate>Wed, 19 May 2004 12:00:00 -0800</pubDate>
1193.      
1194.      <guid>https://jens.mooseyard.com/2004/05/19/anagrams/</guid>
1195.      <description>Way back in 1989 my friend M@ and I used to work at a font company called Kingsley/ATF Type Corporation. One evening after work — actually we were still at work, physically speaking — we began to consider the subject of anagrams of the company name. After running off the necessary letters (in 100pt ITC Galliard all caps from an Adobe Type 1 font, using Microsoft Word 4.0 on a Mac SE, printing to a 300dpi Apple LaserWriter NTX) and cutting them out (I forget the brand name of the scissors) we set to with gusto.</description>
1196.    </item>
1197.    
1198.    <item>
1199.      <title>Cocteau Twins interview (November 1985)</title>
1200.      <link>https://jens.mooseyard.com/2004/05/19/cocteau-twins-interview-november-1985/</link>
1201.      <pubDate>Wed, 19 May 2004 12:00:00 -0800</pubDate>
1202.      
1203.      <guid>https://jens.mooseyard.com/2004/05/19/cocteau-twins-interview-november-1985/</guid>
1204.      <description>&lt;p&gt;This is one of my favorite interviews &lt;em&gt;ever&lt;/em&gt;, and it reminds me of a
1205. long-gone era when the Cocteau Twins mattered, mattered <em>really deeply</em>,
1206. and were making music I could barely believe possible. Music I was not
1207. the only one to find wholly impossible to describe…&lt;/p&gt;</description>
1208.    </item>
1209.    
1210.    <item>
1211.      <title>“Whose round soft dog fidgeting.”</title>
1212.      <link>https://jens.mooseyard.com/2004/05/13/whose-round-soft-dog-fidgeting./</link>
1213.      <pubDate>Thu, 13 May 2004 12:00:00 -0800</pubDate>
1214.      
1215.      <guid>https://jens.mooseyard.com/2004/05/13/whose-round-soft-dog-fidgeting./</guid>
1216.      <description>Whose round soft dog fidgeting. Whose noisy laptop is on fire. Our round mp3 player falls. Whose stupid shining hairy bluish expensive white noisy mp3 player arrives. Any given odd shaped forg arrives as soon as his slopy pensil is angry at the place that his brothers stupid magazine stinks. Their well-crafted book run while whose white tv stinks and a given white mp3 player walks. His slopy binocyles stares at the place that a noisy ram lies.</description>
1217.    </item>
1218.    
1219.    <item>
1220.      <title>My Geek History</title>
1221.      <link>https://jens.mooseyard.com/2004/04/17/my-geek-history/</link>
1222.      <pubDate>Sat, 17 Apr 2004 12:00:00 -0800</pubDate>
1223.      
1224.      <guid>https://jens.mooseyard.com/2004/04/17/my-geek-history/</guid>
1225.      <description>&lt;p&gt;Time to bore you young whippersnappers with my early history in
1226. computers. (I saw a couple of other people do it and thought hey! I can
1227. do that
1228. too&lt;img src=&#34;&#34; alt=&#34;&#34;&gt; First we have to set the Wayback Machine for the darkest depths of the &amp;rsquo;70s, a decade that&amp;rsquo;s oh-so-much funner as retro than it was to live through&amp;hellip;&lt;/p&gt;</description>
1229.    </item>
1230.    
1231.    <item>
1232.      <title>SMTP</title>
1233.      <link>https://jens.mooseyard.com/2004/03/01/smtp/</link>
1234.      <pubDate>Mon, 01 Mar 2004 12:00:00 -0800</pubDate>
1235.      
1236.      <guid>https://jens.mooseyard.com/2004/03/01/smtp/</guid>
1237.      <description>&lt;p&gt;The Simple Mail Transfer Protocol is by no means perfect — its lack of
1238. authentication is a prime reason why spam is such a problem — but I
1239. think it got one thing right: it has the right topology for building a
1240. person-to-person communications system.&lt;/p&gt;</description>
1241.    </item>
1242.    
1243.    <item>
1244.      <title>Super Leaf Blower 64™ Official Players’ Guide</title>
1245.      <link>https://jens.mooseyard.com/2003/12/08/super-leaf-blower-64-official-players-guide/</link>
1246.      <pubDate>Mon, 08 Dec 2003 12:00:00 -0800</pubDate>
1247.      
1248.      <guid>https://jens.mooseyard.com/2003/12/08/super-leaf-blower-64-official-players-guide/</guid>
1249.      <description>Yesterday I got acquainted with our leaf-blower. It’s electric, thank Cthulhu, but not what you’d call “whisper quiet”. We got it as a gift several years ago, and I tried it once back then and it just blew the leaves into a huge swirling cloud that settled down exactly where it began. So I disappointedly put it in the shed and forgot about it.
1250. This time, though, I treated it as if it were some new and powerful item from a game.</description>
1251.    </item>
1252.    
1253.    <item>
1254.      <title>We (had black boxes)</title>
1255.      <link>https://jens.mooseyard.com/2003/10/11/we-had-black-boxes/</link>
1256.      <pubDate>Sat, 11 Oct 2003 12:00:00 -0800</pubDate>
1257.      
1258.      <guid>https://jens.mooseyard.com/2003/10/11/we-had-black-boxes/</guid>
1259.      <description>…each of us had a little box. We didn’t know each other, not at first; we weren’t even aware of each other. “We” was a grouping defined solely by the fact of our having these little boxes. Each box was black lacquer and about two inches on a side. A network of fine black raised lines covered it. The lid could be opened, revealing nothing much inside.
1260. To be honest, it was hard to remember what was inside after you shut the lid.</description>
1261.    </item>
1262.    
1263.    <item>
1264.      <title>We (decided that staying awake)</title>
1265.      <link>https://jens.mooseyard.com/2003/10/10/we-decided-that-staying-awake/</link>
1266.      <pubDate>Fri, 10 Oct 2003 12:00:00 -0800</pubDate>
1267.      
1268.      <guid>https://jens.mooseyard.com/2003/10/10/we-decided-that-staying-awake/</guid>
1269.      <description>…we decided that staying awake as late as possible was the way to write new and creative things. This to be accomplished without the aid of stimulants since the goal was to be as sleepy as possible. In ideal circumstances we would actually fall asleep while typing without stopping, finding ourselves squatting in a gray hypnogogic landscape still tapping on the keyboard finishing up priceless new thoughts. The dream-laptop could then be carried along throughout the night as a powerful and modern spirit guide, helping us to keep appointments with buried archetypes and instantly add new dream symbols to our address books, in addition to the obvious utility of taking dictation during the dream, before the veil is torn on waking and the dream story scattered.</description>
1270.    </item>
1271.    
1272.    <item>
1273.      <title>Apricots Are Falling</title>
1274.      <link>https://jens.mooseyard.com/2003/06/23/apricots-are-falling/</link>
1275.      <pubDate>Mon, 23 Jun 2003 12:00:00 -0800</pubDate>
1276.      
1277.      <guid>https://jens.mooseyard.com/2003/06/23/apricots-are-falling/</guid>
1278.      <description>The apricots are falling, bit by bit
1279. helped along by interfering squirrels.
1280. Though not yet ripe, they roll upon the bricks,
1281. all with tooth-marks, some with chewed-up pits.
1282. This fruit debacle fills us with dismay,
1283. as we had hoped the ripe fruit to preserve
1284. and so retain the sweetness of the day
1285. In far December when light’s gone away.</description>
1286.    </item>
1287.    
1288.    <item>
1289.      <title>Silver “S”s</title>
1290.      <link>https://jens.mooseyard.com/2003/04/07/silver-ss/</link>
1291.      <pubDate>Mon, 07 Apr 2003 12:00:00 -0800</pubDate>
1292.      
1293.      <guid>https://jens.mooseyard.com/2003/04/07/silver-ss/</guid>
1294.      <description>Arranged on a torn out page,
1295. silver “S”s of old wire pulled from broken clocks.
1296. A razor shadow scratched by halogen behind each,
1297. tracing its shape in intersections with blue ink lines,
1298. a curve modeling stresses and crystal faults.
1299. Exhausted by years of funneling pulses from a quartz chip,
1300. the wires relax now bit by bit,
1301. slow motion snakes,
1302. emitting sub-audible scritchings against the paper fibers.
1303. As it unwinds, each proudly imagines itself a mainspring.</description>
1304.    </item>
1305.    
1306.    <item>
1307.      <title>A Koan For Video Gamers</title>
1308.      <link>https://jens.mooseyard.com/2002/09/04/a-koan-for-video-gamers/</link>
1309.      <pubDate>Wed, 04 Sep 2002 12:00:00 -0800</pubDate>
1310.      
1311.      <guid>https://jens.mooseyard.com/2002/09/04/a-koan-for-video-gamers/</guid>
1312.      <description>The Zen master Yoshi was playing a video game. Seated in the lotus position, he expertly maneuvered the controller with his gnarled hands. Nevertheless, on the screen Mario failed to leap from one block to the next and plummeted screaming into the void.
1313. Again, Yoshi began the same level. Again, the moving platforms eluded the sprite onscreen.
1314. Seventeen more times, master Yoshi caused the hapless plumber to fall into nothingness and lose another life.</description>
1315.    </item>
1316.    
1317.    <item>
1318.      <title>We are all snakes</title>
1319.      <link>https://jens.mooseyard.com/2002/01/28/we-are-all-snakes/</link>
1320.      <pubDate>Mon, 28 Jan 2002 12:00:00 -0800</pubDate>
1321.      
1322.      <guid>https://jens.mooseyard.com/2002/01/28/we-are-all-snakes/</guid>
1323.      <description>We are all snakes. We have a tail and onetwothree mouths. The middle mouth bites the tail to hold fast to form, to keep the extra blessings from dropping off one end and becoming lost in the untidy æther. Leftright mouths are perhaps free to latch onto other snakes should the local geometry and snake density so permit. When our fangs sink into each other we exchange blessings. It must be so.</description>
1324.    </item>
1325.    
1326.    <item>
1327.      <title>Fulfillment</title>
1328.      <link>https://jens.mooseyard.com/2002/01/12/fulfillment/</link>
1329.      <pubDate>Sat, 12 Jan 2002 12:00:00 -0800</pubDate>
1330.      
1331.      <guid>https://jens.mooseyard.com/2002/01/12/fulfillment/</guid>
1332.      <description>Eli finally entered the Fulfillment Center at dusk, through the wide metal doors opening into the chilly space within. He had been waiting in line since dawn, shuffling slowly back and forth through the cracked remnants of the old parking lot under the eyes of the security guards. The Center was an old, damaged warehouse – this had been an industrial area before the war – and was lit within by banks of fluorescent tubes suspended from the high ceiling.</description>
1333.    </item>
1334.    
1335.    <item>
1336.      <title>DXM, Big Fun, And My Favorite Hypertext</title>
1337.      <link>https://jens.mooseyard.com/2002/01/05/dxm-big-fun-and-my-favorite-hypertext/</link>
1338.      <pubDate>Sat, 05 Jan 2002 12:00:00 -0800</pubDate>
1339.      
1340.      <guid>https://jens.mooseyard.com/2002/01/05/dxm-big-fun-and-my-favorite-hypertext/</guid>
1341.      <description>By way of introducing my favorite hypertext, I have to digress a bit. Last March [2001] I had a particularly nasty flu for about three weeks, which ended up as a wretched dry cough. I couldn’t go one minute without coughing, and I had a horrible sharp pain in my ribs caused by a sprained chest muscle. One night I was lying on the couch (so I wouldn’t keep Diana up all night) trying in vain to sleep, and decided to look up exciting Drug Facts about various medications I was taking.</description>
1342.    </item>
1343.    
1344.    <item>
1345.      <title>Splendor</title>
1346.      <link>https://jens.mooseyard.com/2001/12/20/splendor/</link>
1347.      <pubDate>Thu, 20 Dec 2001 12:00:00 -0800</pubDate>
1348.      
1349.      <guid>https://jens.mooseyard.com/2001/12/20/splendor/</guid>
1350.      <description>We stepped out our back door into splendor:
1351. – the rain-choked hills casting off their muddy carapace of topsoil
1352. – uprooted trees shedding their last dead leaves like ticker-tape
1353. – all of up heading for down.
1354. All the wet rot of the rotating Earth converged on our yard
1355. but was held back by cinderblock walls
1356. with a splash.
1357. Our house lay alone at the foot of a brown slope devoid of landmarks:</description>
1358.    </item>
1359.    
1360.    <item>
1361.      <title>Polar Star</title>
1362.      <link>https://jens.mooseyard.com/2001/10/30/polar-star/</link>
1363.      <pubDate>Tue, 30 Oct 2001 12:00:00 -0800</pubDate>
1364.      
1365.      <guid>https://jens.mooseyard.com/2001/10/30/polar-star/</guid>
1366.      <description>The horizon folded down its blackness.
1367. Overhead curled exalted green clouds
1368. of Sun-born particles spiraling in.
1369. Now upward in an arc, tied to the long invisible armature of the Pole,
1370. flew my humble cardboard tube of Earthly minerals,
1371. in one moment transmuted into circlets and spheres of sparks —
1372. dark materials achieving by dint of effort
1373. glory surpassing the Sun’s electrons,
1374. if only for a second.
1375. Hood thrown back I howled a warning to low-flying angels.</description>
1376.    </item>
1377.    
1378.    <item>
1379.      <title>They Made Me An Offer I Couldn’t Refuse</title>
1380.      <link>https://jens.mooseyard.com/1997/04/13/they-made-me-an-offer-i-couldnt-refuse/</link>
1381.      <pubDate>Sun, 13 Apr 1997 12:00:00 -0800</pubDate>
1382.      
1383.      <guid>https://jens.mooseyard.com/1997/04/13/they-made-me-an-offer-i-couldnt-refuse/</guid>
1384.      <description>System Software were looking for a Post-It Notes™ type of program for System 7.5. They were already buying several other utilities — including Find File, Scrapbook, SuperClock — from third parties, and offered Antler Software (me) the same lump sum deal for the “Antler Notes” utility I was working on. It was a nice piece of change. I was happy.
1385. This came to the attention of certain people in upper management, whose conclusion was (I’m paraphrasing here) “Why are we going to pay for this?</description>
1386.    </item>
1387.    
1388.    <item>
1389.      <title>Jens The Consumer</title>
1390.      <link>https://jens.mooseyard.com/1995/08/24/jens-the-consumer/</link>
1391.      <pubDate>Thu, 24 Aug 1995 12:00:00 -0800</pubDate>
1392.      
1393.      <guid>https://jens.mooseyard.com/1995/08/24/jens-the-consumer/</guid>
1394.      <description>The problem of leisure
1395. What to do for pleasure
1396. Ideal love a new purchase
1397. A market of the senses
1398. —Gang Of Four, “Natural’s Not In It”
1399.  “He realizes everything he does is second-hand, a waking dream, a dream someone else has dreamed for him — when he walks into a pub and greets friends with a line he’s half-consciously lifted from last night’s sit-com, he’s an advertisement. He hears himself and he feels tricked, humiliated, so he smashes into his friends … as if he’s never seen them before but knows they mean him no good.</description>
1400.    </item>
1401.    
1402.    <item>
1403.      <title>Piling Up Sheets / the face in the soup bowl</title>
1404.      <link>https://jens.mooseyard.com/1995/08/23/piling-up-sheets-/-the-face-in-the-soup-bowl/</link>
1405.      <pubDate>Wed, 23 Aug 1995 12:00:00 -0800</pubDate>
1406.      
1407.      <guid>https://jens.mooseyard.com/1995/08/23/piling-up-sheets-/-the-face-in-the-soup-bowl/</guid>
1408.      <description>&lt;p&gt;I decided I would only work on this page after ten PM, when I think
1409. differently. When I’m tired but alert, and everyone around me is asleep,
1410. and it’s dark and quiet.</p>
1411. <p>The cognitive scientist and AI researcher David Gelernter has a model of
1412. consciousness that has <em>focus</em> as its parameter: varying focus produces
1413. mental states from rigorous logical thought (when focus is at its
1414. highest) all the way down to dreaming (when focus is at its lowest.) In
1415. high focus states the mind seizes precisely on individual concepts and
1416. ideas. In low focus states, multiple ideas, concepts and memories
1417. overlay each other such that they can’t be distinguished; they’re
1418. superimposed and common features line up, connections between disparate
1419. thoughts. In this mode the mind jumps from one memory to another, linked
1420. by a chain of connections formed by lining up fragmentary images of
1421. those memories. Like a dream.&lt;/p&gt;</description>
1422.    </item>
1423.    
1424.    <item>
1425.      <title>Glass Lizard</title>
1426.      <link>https://jens.mooseyard.com/1993/06/21/glass-lizard/</link>
1427.      <pubDate>Mon, 21 Jun 1993 12:00:00 -0800</pubDate>
1428.      
1429.      <guid>https://jens.mooseyard.com/1993/06/21/glass-lizard/</guid>
1430.      <description>&lt;p&gt;The beach that fall was overrun by glass lizards; I had never seen them
1431. before. I knew there had been none at the beach when we had visited
1432. during the summers (I could remember four summers, and my parents said
1433. there had been more.)&lt;/p&gt;</description>
1434.    </item>
1435.    
1436.    <item>
1437.      <title>The Cow Telescope</title>
1438.      <link>https://jens.mooseyard.com/1991/03/03/the-cow-telescope/</link>
1439.      <pubDate>Sun, 03 Mar 1991 12:00:00 -0800</pubDate>
1440.      
1441.      <guid>https://jens.mooseyard.com/1991/03/03/the-cow-telescope/</guid>
1442.      <description>WHEN I stick my head out of the skylight and look to the left I can see the Cow Telescope atop its hill, red light at the tip blinking to ward off low-flying aircraft. You can see it from Interstate 280; from the back of my parents’ Volvo I used to watch it as we drove past, a big metal parabolic dish pointed at something in the sky, on a grassy hill alone except for the odd ruminating cow.</description>
1443.    </item>
1444.    
1445.  </channel>
1446. </rss>
1447.  

If you would like to create a banner that links to this page (i.e. this validation result), do the following:

1. Download the "valid RSS" banner.

2. Upload the image to your own server. (This step is important. Please do not link directly to the image on this server.)

3. Add this HTML to your page (change the image src attribute if necessary):

   <a href="http://www.feedvalidator.org/check.cgi?url=http%3A//jens.mooseyard.com/index.xml"><img src="valid-rss-rogers.png" alt="[Valid RSS]" title="Validate my RSS feed" /></a>

If you would like to create a text link instead, here is the URL you can use:

http://www.feedvalidator.org/check.cgi?url=http%3A//jens.mooseyard.com/index.xml

Home · About · News · Docs · Terms