<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet type="text/xsl" href="../assets/xml/rss.xsl" media="all"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Other Wise (Posts about Site)</title><link>https://kanga.nu/~claw/blog/</link><description></description><atom:link href="https://kanga.nu/~claw/blog/categories/site.xml" rel="self" type="application/rss+xml"></atom:link><language>en</language><copyright>Contents © 2023 &lt;a href="mailto:claw@kanga.nu"&gt;J C Lawrence&lt;/a&gt; &lt;a rel="license" href="https://creativecommons.org/licenses/by-nc-sa/4.0/ &gt;Creative Commons License&lt;/a&gt;</copyright><lastBuildDate>Sun, 27 Aug 2023 20:59:23 GMT</lastBuildDate><generator>Nikola (getnikola.com)</generator><docs>http://blogs.law.harvard.edu/tech/rss</docs><item><title>Dust may Happen</title><link>https://kanga.nu/~claw/blog/posts/2018/03/21/dust_may_happen/</link><dc:creator>J C Lawrence</dc:creator><description>&lt;p&gt;Muddling about, cleaning things up a bit and getting a few more bits
and other bobs standardised.  Fixing old broken image links, having
another whack at the CSS width issue, re-tagging artcles more
approriately (eg the new &lt;a href="https://kanga.nu/~claw/blog/categories/18xx/"&gt;18xx tag&lt;/a&gt;), etc.&lt;/p&gt;</description><category>Site</category><guid>https://kanga.nu/~claw/blog/posts/2018/03/21/dust_may_happen/</guid><pubDate>Wed, 21 Mar 2018 07:06:53 GMT</pubDate></item><item><title>Shivering Newness</title><link>https://kanga.nu/~claw/blog/posts/2017/04/17/shivering-newness/</link><dc:creator>J C Lawrence</dc:creator><description>&lt;p&gt;Welcome to the new old blog.  &lt;/p&gt;
&lt;p&gt;In short I’m moving off Wordpress and moving to a static-HTML solution
built atop &lt;a href="https://getnikola.com/"&gt;Nikola&lt;/a&gt;.  Why?  Because it doesn’t
come with the load and security concerns of Wordpress, PHP, database
servers, XSS, etc.  Smaller, simpler, easier and rather more
care-free, not least across upgrades.&lt;/p&gt;
&lt;p&gt;The old blog:&lt;/p&gt;
&lt;p&gt;&lt;img src="https://kanga.nu/~claw/blog/images/Screenshot_from_2017-04-17_00-57-42.png" alt="The prior blog format" width="75%"&gt;&lt;/p&gt;
&lt;p&gt;Some features are being lost in the transition:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href="http://www.dict.org/bin/Dict"&gt;dict&lt;/a&gt; integration (I’d link keywords
to their dictionary definitions) is gone.  Mayhap I’ll get around to
writing an extension for PyMarkdown for that, but it won’t be now.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Automatic cross-linking of keywords and phases to other pages/sites.
This mostly means that a lot of links to
&lt;a href="http://boardgamegeek.com/"&gt;BoardGameGeek&lt;/a&gt; for various game names have
fallen out.  The names are still there, but the links are not.
Again…maybe I’ll write an extension some day to do that.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Comments.  They’re gone.  Sorry.  I’m not yet sure what I want to do
here.  &lt;a href="https://posativ.org/isso/"&gt;Isso&lt;/a&gt; is a strong possibility –
not least because I’ll have a possibility of porting the old comments
over – but I don’t want to hang up this migration with the larger
question of what comment system to use.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Image galleries are not quite so nice.  Sigh.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;And of course there was an excuse for a visual redesign.  I so rarely
do UI work; this was rather enjoyable.&lt;/p&gt;
&lt;p&gt;Ahh well, I now see 20 things to fix 5 seconds after hitting deploy.
‘Tis ever thus.  If you notice any problems, please feel free to drop
me a note at the email address in the footer.&lt;/p&gt;</description><category>Site</category><guid>https://kanga.nu/~claw/blog/posts/2017/04/17/shivering-newness/</guid><pubDate>Mon, 17 Apr 2017 07:06:54 GMT</pubDate></item><item><title>And upon the far horizon in the east</title><link>https://kanga.nu/~claw/blog/posts/2010/04/22/site/and-upon-the-far-horizon-in-the-east/</link><dc:creator>J C Lawrence</dc:creator><description>&lt;p&gt;Kanga.nu and its services have been moved to a new host.  This marks the final decommissioning of the box I built from parts while working at VA Research.  It has been a long time..and it is somewhat sad to see her fade into scrap.&lt;/p&gt;
&lt;p&gt;If you notice problems or inconsistencies, please comment below or email me.&lt;/p&gt;</description><category>Site</category><guid>https://kanga.nu/~claw/blog/posts/2010/04/22/site/and-upon-the-far-horizon-in-the-east/</guid><pubDate>Thu, 22 Apr 2010 14:33:41 GMT</pubDate></item><item><title>Site: OpenID logins are now enabled for commenters</title><link>https://kanga.nu/~claw/blog/posts/2009/07/17/site/site-openid-logins-are-now-enabled-for-commenters/</link><dc:creator>J C Lawrence</dc:creator><description>&lt;p&gt;I have enabled &lt;a href="http://openid.net/"&gt;OpenID&lt;/a&gt; account creation and login support.  Now you don’t have to maintain a separate login for this blog in order to post comments!&lt;/p&gt;
&lt;p&gt;Enjoy.&lt;/p&gt;</description><category>Site</category><guid>https://kanga.nu/~claw/blog/posts/2009/07/17/site/site-openid-logins-are-now-enabled-for-commenters/</guid><pubDate>Sat, 18 Jul 2009 03:46:34 GMT</pubDate></item><item><title>Site upgrade</title><link>https://kanga.nu/~claw/blog/posts/2009/03/29/site/site-upgrade/</link><dc:creator>J C Lawrence</dc:creator><description>&lt;p&gt;I’m about to start a site-upgrade for Wordpress and a few other key packages, moving from Wordpress 2.5 (plus a long list of security patches) to Wordpress 2.7 (plus a shorter list of security patches).  As I hand-wrote the Wordpress theme this site uses, and several of the plugins were extensively edited away from their defaults, things may look odd or broken for a while.  Please bear with me…&lt;/p&gt;</description><category>Site</category><guid>https://kanga.nu/~claw/blog/posts/2009/03/29/site/site-upgrade/</guid><pubDate>Sun, 29 Mar 2009 22:37:27 GMT</pubDate></item><item><title>Nurse, I really can't wait any longer</title><link>https://kanga.nu/~claw/blog/posts/2009/02/23/site/nurse-i-really-cant-wait-any-longer/</link><dc:creator>J C Lawrence</dc:creator><description>&lt;p&gt;I’m currently fiddling about with integrating my iPhone, various supplemental iPhone features (eg camera), Twitter, Facebook and this blog.  There will be some noise and dust.  Patience!&lt;/p&gt;</description><category>Site</category><guid>https://kanga.nu/~claw/blog/posts/2009/02/23/site/nurse-i-really-cant-wait-any-longer/</guid><pubDate>Mon, 23 Feb 2009 19:17:25 GMT</pubDate></item><item><title>Chrome, comments and this site</title><link>https://kanga.nu/~claw/blog/posts/2009/02/22/site/chrome-comments-and-this-site/</link><dc:creator>J C Lawrence</dc:creator><description>&lt;p&gt;One of the Muck &amp;amp; Brass playtesters has been unable to post comments using Google Chrome.  I don’t know why as I can’t test here with Chrome as I don’t run Windows on any of my machines.  I’ve tested with multiple test accounts under Firefox, Safari, Konqueror, Lynx and W3: all have been able to post comments without trouble.  &lt;/p&gt;
&lt;p&gt;Comments are moderated in order to trap spam.  When you post a comment, the next page should show the original entry and its comment thread.  The last comment in the thread should be the one you just submitted, along with an annotation that it is being held for moderation:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Author:  Test User | Date:  Saturday 21 February 2009 | Time:  11:20&lt;/p&gt;
&lt;p&gt;Your comment is awaiting moderation.&lt;/p&gt;
&lt;p&gt;This is a test comment.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;If you are having trouble posting comments, please &lt;a href="mailto:claw+blogproblem@kanga.nu"&gt;email me directly&lt;/a&gt; with the details.&lt;/p&gt;</description><category>Site</category><guid>https://kanga.nu/~claw/blog/posts/2009/02/22/site/chrome-comments-and-this-site/</guid><pubDate>Sun, 22 Feb 2009 20:24:52 GMT</pubDate></item><item><title>Moving categorical confusion</title><link>https://kanga.nu/~claw/blog/posts/2008/10/25/site/moving-categorical-confusion/</link><dc:creator>J C Lawrence</dc:creator><description>&lt;p&gt;Ooops.  I just noticed that one of the side effects of &lt;a href="https://kanga.nu/~claw/blog/posts/2008/10/23/site/category-management/"&gt;nesting the game-project categories&lt;/a&gt; is that the RSS feed URLs for the categories have now changed to represent the nesting.  Arghh.  Sorry guys.  If this is a real problem please comment below and I’ll stick in some Apache rewrite rules to handle it.&lt;/p&gt;</description><category>Site</category><guid>https://kanga.nu/~claw/blog/posts/2008/10/25/site/moving-categorical-confusion/</guid><pubDate>Sun, 26 Oct 2008 06:31:57 GMT</pubDate></item><item><title>Category management</title><link>https://kanga.nu/~claw/blog/posts/2008/10/23/site/category-management/</link><dc:creator>J C Lawrence</dc:creator><description>&lt;p&gt;In order to ease managment and overview of the site I’ve created a &lt;em&gt;Game Project&lt;/em&gt; category and moved all my design projects under it.  Aside from some resultant sorting and nesting of the category list, there’s also now an &lt;a href="https://kanga.nu/~claw/blog/categories/game-projects.xml"&gt;RSS feed for just my game projects&lt;/a&gt;.  See the &lt;em&gt;This Category&lt;/em&gt; link in the sidebar when viewing the category.&lt;/p&gt;</description><category>Site</category><guid>https://kanga.nu/~claw/blog/posts/2008/10/23/site/category-management/</guid><pubDate>Fri, 24 Oct 2008 04:05:02 GMT</pubDate></item><item><title>A failure to communicate</title><link>https://kanga.nu/~claw/blog/posts/2008/07/12/a-failure-to-communicate/</link><dc:creator>J C Lawrence</dc:creator><description>&lt;p&gt;The tool I’ve been using to footnote definitions of terms some readers may not know has a problem.  It can result in broken RSS and Atom feeds which don’t validate, usually due to non-UTF8 characters in strings which are defined as UTF8 strings.  In turn this causes various RSS readers and aggregators (eg &lt;a href="http://bloglines.com/"&gt;Bloglines&lt;/a&gt; and &lt;a href="http://technorati.com/"&gt;Technorati&lt;/a&gt;) to fail to import the feed.  Ooops.&lt;/p&gt;
&lt;p&gt;For now I’ve removed the offending definition linkages (suet and jocund) and am on the lookout for a replacement WordPress plugin, preferably one based on &lt;a href="http://dict.org/"&gt;dict&lt;/a&gt;&lt;sup id="fnref:1"&gt;&lt;a class="footnote-ref" href="https://kanga.nu/~claw/blog/posts/2008/07/12/a-failure-to-communicate/#fn:1"&gt;1&lt;/a&gt;&lt;/sup&gt;.&lt;/p&gt;
&lt;div class="footnote"&gt;
&lt;hr&gt;
&lt;ol&gt;
&lt;li id="fn:1"&gt;
&lt;p&gt;I’m a frequent, nay, near-constant user of dict. &lt;a class="footnote-backref" href="https://kanga.nu/~claw/blog/posts/2008/07/12/a-failure-to-communicate/#fnref:1" title="Jump back to footnote 1 in the text"&gt;↩&lt;/a&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;/div&gt;</description><category>Site</category><guid>https://kanga.nu/~claw/blog/posts/2008/07/12/a-failure-to-communicate/</guid><pubDate>Sat, 12 Jul 2008 22:33:56 GMT</pubDate></item></channel></rss>