<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>hyperspasm.com &#187; Software</title>
	<atom:link href="http://www.hyperspasm.com/hyperblog/?cat=3&#038;feed=rss2" rel="self" type="application/rss+xml" />
	<link>http://www.hyperspasm.com/hyperblog</link>
	<description>just in case I forget...</description>
	<lastBuildDate>Sat, 18 Aug 2012 18:32:17 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>aiffpack</title>
		<link>http://www.hyperspasm.com/hyperblog/?p=40</link>
		<comments>http://www.hyperspasm.com/hyperblog/?p=40#comments</comments>
		<pubDate>Tue, 17 Mar 2009 00:33:11 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Software]]></category>

		<guid isPermaLink="false">http://www.hyperspasm.com/hyperblog/?p=40</guid>
		<description><![CDATA[I wrote a command line utility that will create a single multi-channel AIFF file from a set of input audio files. It uses the libsndfile library for reading and writing sound files. You can download the OSX (ppc/i386) binary along with the source code here. You you should also be able to easily build it [...]]]></description>
			<content:encoded><![CDATA[<p>I wrote a command line utility that will create a single multi-channel AIFF file from a set of input audio files. It uses the libsndfile library for reading and writing sound files. You can download the OSX (ppc/i386) binary along with the source code here. You you should also be able to easily build it from source on any *nix platform that has <a href="http://www.mega-nerd.com/libsndfile/" target="_blank">libsndfile</a> installed.</p>
<p><a href="http://www.hyperspasm.com/hyperblog/wp-content/uploads/2009/03/aiffpack-012.tgz">aiffpack-012</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.hyperspasm.com/hyperblog/?feed=rss2&#038;p=40</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>TextWrangler plug-ins</title>
		<link>http://www.hyperspasm.com/hyperblog/?p=1</link>
		<comments>http://www.hyperspasm.com/hyperblog/?p=1#comments</comments>
		<pubDate>Mon, 16 Mar 2009 20:34:11 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Software]]></category>

		<guid isPermaLink="false">http://www.hyperspasm.com/hyperblog/?p=1</guid>
		<description><![CDATA[TextWrangler is my favorite editor. I made some plug-ins for syntax highlighting. Lately I have been writing assembly for Analog Devices SHARC processors and also a little bit of PIC16 stuff. Here are the TextWrangler plug-ins that I made for their instructions sets. To use them, copy them to ~/Library/Application Support/TextWrangler/Language Modules. SHARC.plist PIC16.plist 10/15/09: [...]]]></description>
			<content:encoded><![CDATA[<p>TextWrangler is my favorite editor. I made some plug-ins for syntax highlighting. Lately I have been writing assembly for Analog Devices SHARC processors and also a little bit of PIC16 stuff. Here are the TextWrangler plug-ins that I made for their instructions sets. To use them, copy them to ~/Library/Application Support/TextWrangler/Language Modules.</p>
<p><a href="http://www.hyperspasm.com/hyperblog/wp-content/uploads/2009/03/sharc.plist">SHARC.plist</a></p>
<p><a href="http://www.hyperspasm.com/hyperblog/wp-content/uploads/2009/03/pic16.plist">PIC16.plist</a></p>
<p>10/15/09:<br />
Updated both language modules fixing a bug which showed up in TextWrangler 3.0.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.hyperspasm.com/hyperblog/?feed=rss2&#038;p=1</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>underline 1.9.5</title>
		<link>http://www.hyperspasm.com/hyperblog/?p=77</link>
		<comments>http://www.hyperspasm.com/hyperblog/?p=77#comments</comments>
		<pubDate>Tue, 23 Dec 2003 13:31:13 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Software]]></category>

		<guid isPermaLink="false">http://www.hyperspasm.com/hyperblog/?p=77</guid>
		<description><![CDATA[Underline is a variant of the Openline client, an open source hotline client for MacOS and Windows.  The primary difference between Underline and the Openline client is that Underline optionally uses blowfish to encrypt connections to servers that support it. Underline only supports encryption on the primary socket and not on sockets established for file transfers. [...]]]></description>
			<content:encoded><![CDATA[<p>Underline is a variant of the Openline client, an open source hotline client for MacOS and Windows. </p>
<p>The primary difference between Underline and the Openline client is that Underline optionally uses blowfish to encrypt connections to servers that support it. Underline only supports encryption on the primary socket and not on sockets established for file transfers. At this time no known hotline client/server supports the encrytion of file transfers. </p>
<p>Underline (like Openline) is released under the <a href="http://www.fsf.org/copyleft/gpl.html">GNU GPL</a>. The source code can be obtained here: <a href="http://www.hyperspasm.com/hyperblog/wp-content/uploads/2003/12/underline-src.sit">underline-src.sit</a><br />
MacOSX users should use the carbon version of Underline and MacOS9 users should use the classic version, both downloadable here: <a href="http://www.hyperspasm.com/hyperblog/wp-content/uploads/2003/12/underline-macos.sit">underline-macos.sit</a><br />
The Windows version can be downloaded here: <a href="http://www.hyperspasm.com/hyperblog/wp-content/uploads/2003/12/underline-win.zip">underline-win.zip</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.hyperspasm.com/hyperblog/?feed=rss2&#038;p=77</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
