<?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>blog.ryara.net</title>
	<atom:link href="http://blog.ryara.net/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.ryara.net</link>
	<description></description>
	<lastBuildDate>Sat, 17 Dec 2011 04:21:08 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>PuTTY-url 0.62</title>
		<link>http://blog.ryara.net/2011/12/17/putty-url-0-62/</link>
		<comments>http://blog.ryara.net/2011/12/17/putty-url-0-62/#comments</comments>
		<pubDate>Sat, 17 Dec 2011 04:13:09 +0000</pubDate>
		<dc:creator>tobbez</dc:creator>
				<category><![CDATA[Computers]]></category>

		<guid isPermaLink="false">http://blog.ryara.net/?p=226</guid>
		<description><![CDATA[The PuTTY patch with clickable URL support has been updated for PuTTY 0.62. You can find the patch (and a binary) on the new web site for the patch at http://ryara.net/putty-url/.]]></description>
			<content:encoded><![CDATA[<p>The PuTTY patch with clickable URL support has been updated for PuTTY 0.62.</p>
<p>You can find the patch (and a binary) on the new web site for the patch at <a href="http://ryara.net/putty-url/" title="http://ryara.net/putty-url/">http://ryara.net/putty-url/</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.ryara.net/2011/12/17/putty-url-0-62/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>PuTTY 0.61 with clickable links</title>
		<link>http://blog.ryara.net/2011/07/14/putty-0-61-with-clickable-links/</link>
		<comments>http://blog.ryara.net/2011/07/14/putty-0-61-with-clickable-links/#comments</comments>
		<pubDate>Thu, 14 Jul 2011 21:23:08 +0000</pubDate>
		<dc:creator>tobbez</dc:creator>
				<category><![CDATA[Computers]]></category>

		<guid isPermaLink="false">http://blog.ryara.net/?p=178</guid>
		<description><![CDATA[The patch now has a web site at http://ryara.net/putty-url/, where all future updates will be posted. Since PuTTY tray (which I have been using for this functionality so far) has been discontinued, I decided to port its clickable link functionality &#8230; <a href="http://blog.ryara.net/2011/07/14/putty-0-61-with-clickable-links/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p><ins datetime="2011-12-17T04:18:35+00:00">The patch now has a web site at <a href="http://ryara.net/putty-url/" title="http://ryara.net/putty-url/">http://ryara.net/putty-url/</a>, where all future updates will be posted.</ins></p>
<p>Since <a href="http://haanstra.eu/putty/">PuTTY tray</a> (which I have been using for this functionality so far) has been discontinued, I decided to port its clickable link functionality to PuTTY 0.61 myself.</p>
<p>For some reason the code (which originally comes from <a href="http://groehn.net/nutty/">Nutty</a>) was written in C++ while PuTTY is written in C, so I rewrote the C++ parts in C at the same time. This means it should be at least a little bit closer to a possible <a href="http://www.chiark.greenend.org.uk/~sgtatham/putty/wishlist/url-launching.html">inclusion in PuTTY</a>.</p>
<p>What I&#8217;ve done:</p>
<ul>
<li>Ported C++ parts to C</li>
<li>Launching the URL now uses ShellExecute directly, meaning any type of URL should work (e.g. spotify) when using an appropriate regex.</li>
<li>Set default font to Consolas and enable ClearType on Vista and later (kept from PuTTY Tray)</li>
<li>Change icons to the ones from PuTTY Tray (I like them better)</li>
<li>Patch the build Recipe so that you can make a patched build using PuTTY&#8217;s build system</li>
<li>Bugfix: Clicking a wrapped link with the window scrolled up should now work as expected</li>
</ul>
<p>To build it yourself (using mingw on linux):</p>
<ol>
<li>Download the PuTTY source and the patch</li>
<li>Unpack the source and apply the patch: <code>tar xzf putty-0.61.tar.gz; cd putty-0.61; patch -p1 &lt; ../putty-tobbez-0.61-r1.patch</code></li>
<li>Drop the replacement icons into the <code>windows/</code> subdirectory if you want them.
<li>Generate build files: <code>./mkfiles.pl</code></li>
<li>Export the <code>TOOLPATH</code> variable so that the variables CC and RC in windows/Makefile.cyg to point to your tools (for me it was <code>export TOOLPATH="i686-mingw32-"</code>)</li>
<li>Build it: <code>cd windows; make -f Makefile.cyg</code></li>
<li>The executable has been created in the same folder.</li>
</ol>
<p>Download:<br />
Executable: <a href="http://blog.ryara.net/files/2011-07-14/putty.exe">putty.exe</a> (Only if you trust me)<br />
Patch: <a href="http://blog.ryara.net/files/2011-07-14/putty-tobbez-0.61-r1.patch">putty-tobbez-0.61-r1.patch</a> <del>putty-tobbez-0.61.patch</del><br />
Icons: <a href="http://blog.ryara.net/files/2011-07-14/putty.ico">putty.ico</a>, <a href="http://blog.ryara.net/files/2011-07-14/puttycfg.ico">puttycfg.ico</a></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.ryara.net/2011/07/14/putty-0-61-with-clickable-links/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>So&#8230;</title>
		<link>http://blog.ryara.net/2011/07/02/so/</link>
		<comments>http://blog.ryara.net/2011/07/02/so/#comments</comments>
		<pubDate>Sat, 02 Jul 2011 22:41:44 +0000</pubDate>
		<dc:creator>tobbez</dc:creator>
				<category><![CDATA[Random stuff]]></category>

		<guid isPermaLink="false">http://blog.ryara.net/?p=169</guid>
		<description><![CDATA[&#8230;I invented something in minecraft: (Link: http://www.youtube.com/watch?v=OcwhkymtBH0)]]></description>
			<content:encoded><![CDATA[<p>&#8230;I invented something in minecraft: <iframe width="640" height="510" src="http://www.youtube.com/embed/OcwhkymtBH0?rel=0&amp;hd=1" frameborder="0" allowfullscreen></iframe><br />
(Link: <a href="http://www.youtube.com/watch?v=OcwhkymtBH0">http://www.youtube.com/watch?v=OcwhkymtBH0</a>)</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.ryara.net/2011/07/02/so/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Patch for FiSH for irssi with recode</title>
		<link>http://blog.ryara.net/2010/06/14/patch-fish-irssi-with-recode/</link>
		<comments>http://blog.ryara.net/2010/06/14/patch-fish-irssi-with-recode/#comments</comments>
		<pubDate>Mon, 14 Jun 2010 20:37:47 +0000</pubDate>
		<dc:creator>tobbez</dc:creator>
				<category><![CDATA[Computers]]></category>

		<guid isPermaLink="false">http://blog.ryara.net/?p=154</guid>
		<description><![CDATA[This patch fixes a buffer overflow (causing a segfault) that would happen if an ISO-8859-1 sent a string consisting of many instances of a single extended character (å, ä, ö etc). The patch is against FiSH v1.0-RC5, and is only &#8230; <a href="http://blog.ryara.net/2010/06/14/patch-fish-irssi-with-recode/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>This patch fixes a buffer overflow (causing a segfault) that would happen if an ISO-8859-1 sent a string consisting of many instances of a single extended character (å, ä, ö etc).</p>
<p>The patch is against FiSH v1.0-RC5, and is only relevant if you use the recode support in FiSH.</p>
<p>The side effect of this patch is that lines that would previously make irssi segfault will now be cut off (due to limits with the structure of irssi modules).</p>
<p>You can download the patch here: <a href="http://blog.ryara.net/files/FiSH-irssi.v1.00-RC5-recode-segfault-fix.patch">FiSH-irssi.v1.00-RC5-recode-segfault-fix.patch</a></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.ryara.net/2010/06/14/patch-fish-irssi-with-recode/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>libucfg</title>
		<link>http://blog.ryara.net/2010/04/29/libucfg/</link>
		<comments>http://blog.ryara.net/2010/04/29/libucfg/#comments</comments>
		<pubDate>Thu, 29 Apr 2010 18:07:42 +0000</pubDate>
		<dc:creator>tobbez</dc:creator>
				<category><![CDATA[Computers]]></category>

		<guid isPermaLink="false">http://blog.ryara.net/?p=150</guid>
		<description><![CDATA[I just released libucfg, a small configuration library in ANSI C. You can find it here.]]></description>
			<content:encoded><![CDATA[<p>I just released libucfg, a small configuration library in ANSI C. You can find it <a href="http://github.com/tobbez/libucfg">here</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.ryara.net/2010/04/29/libucfg/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>ld-preload-reverse</title>
		<link>http://blog.ryara.net/2009/12/22/ld-preload-reverse/</link>
		<comments>http://blog.ryara.net/2009/12/22/ld-preload-reverse/#comments</comments>
		<pubDate>Tue, 22 Dec 2009 03:27:17 +0000</pubDate>
		<dc:creator>tobbez</dc:creator>
				<category><![CDATA[Computers]]></category>

		<guid isPermaLink="false">http://blog.ryara.net/?p=141</guid>
		<description><![CDATA[I though I would post this piece of code since it has been laying around for quite a while. ld-preload-reverse is a LD_PRELOAD library that overrides the most common functions for writing text to a terminal, and reverses their output: &#8230; <a href="http://blog.ryara.net/2009/12/22/ld-preload-reverse/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>I though I would post this piece of code since it has been laying around for quite a while.</p>
<p>ld-preload-reverse is a LD_PRELOAD library that overrides the most common<br />
functions for writing text to a terminal, and reverses their output:</p>
<p>Looks like this:<br />
<code><br />
tobbez@sagiri ~/dev/ld-preload-reverse $ LD_PRELOAD=./ld-preload-reverse.so bash<br />
 $ esrever-daolerp-dl/ved/~ irigas@zebbotls<br />
GNIYPOC  elifekaM  EMDAER  c.esrever-daolerp-dl  os.esrever-daolerp-dl<br />
 $ esrever-daolerp-dl/ved/~ irigas@zebbotcat Ma elifek<br />
os.esrever-daolerp-dl :lla</p>
<p>c.esrever-daolerp-dl :os.esrever-daolerp-dl<br />
c.esrever-daolerp-dl os.esrever-daolerp-dl o- derahs- CIPf- ldl- llaW- ccg</p>
<p>:naelc YNOHP.<br />
os.esrever-daolerp-dl f- mr<br />
 $ esrever-daolerp-dl/ved/~ irigas@zebbottixe<br />
</code></p>
<p>It&#8217;s licensed under the Eiffel Forum License 2, and you can find the code <a href="http://github.com/tobbez/ld-preload-reverse/">here</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.ryara.net/2009/12/22/ld-preload-reverse/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>lighttpd rewrite rules for Symphony CMS</title>
		<link>http://blog.ryara.net/2009/12/05/lighttpd-rewrite-rules-for-symphony-cms/</link>
		<comments>http://blog.ryara.net/2009/12/05/lighttpd-rewrite-rules-for-symphony-cms/#comments</comments>
		<pubDate>Sat, 05 Dec 2009 16:46:08 +0000</pubDate>
		<dc:creator>tobbez</dc:creator>
				<category><![CDATA[Computers]]></category>

		<guid isPermaLink="false">http://blog.ryara.net/?p=135</guid>
		<description><![CDATA[For Symphony 2.0.6. url.rewrite-once += ( "^/symphony/favicon.ico$" => "$0", "^/symphony/symphony/(assets&#124;content&#124;lib&#124;template)/.*$" => "$0", "^/symphony/workspace/[^/]+/.*$" => "$0", "^/symphony/image/(.+\.(jpg&#124;gif&#124;jpeg&#124;png&#124;bmp))$" => "/symphony/extensions/jit_image_manipulation/lib/image.php?param=$1", "^/symphony/symphony/?(\?(.*))?$" => "/symphony/index.php?mode=administration&#038;$2", "^/symphony/symphony(/(.*/?))?(\?(.*))?$" => "/symphony/index.php?symphony-page=$1&#038;mode=administration&#038;$4", "^/symphony/([^?]*/?)(\?(.*))?$" => "/symphony/index.php?symphony-page=$1&#038;$3" ) Replace the first occurrence of &#8216;symphony&#8217; on every line with the location &#8230; <a href="http://blog.ryara.net/2009/12/05/lighttpd-rewrite-rules-for-symphony-cms/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>For <a href="http://symphony-cms.com/">Symphony</a>  2.0.6.</p>
<pre>url.rewrite-once += ( "^/symphony/favicon.ico$" => "$0",
                      "^/symphony/symphony/(assets|content|lib|template)/.*$" => "$0",
                      "^/symphony/workspace/[^/]+/.*$" => "$0",
                      "^/symphony/image/(.+\.(jpg|gif|jpeg|png|bmp))$" => "/symphony/extensions/jit_image_manipulation/lib/image.php?param=$1",
                      "^/symphony/symphony/?(\?(.*))?$" => "/symphony/index.php?mode=administration&#038;$2",
                      "^/symphony/symphony(/(.*/?))?(\?(.*))?$" => "/symphony/index.php?symphony-page=$1&#038;mode=administration&#038;$4",
                      "^/symphony/([^?]*/?)(\?(.*))?$" => "/symphony/index.php?symphony-page=$1&#038;$3" )
</pre>
<p>Replace the first occurrence of &#8216;symphony&#8217; on every line with the location of your Symphony installation.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.ryara.net/2009/12/05/lighttpd-rewrite-rules-for-symphony-cms/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Ebuild for libsummer</title>
		<link>http://blog.ryara.net/2009/03/28/ebuild-for-libsummer/</link>
		<comments>http://blog.ryara.net/2009/03/28/ebuild-for-libsummer/#comments</comments>
		<pubDate>Sat, 28 Mar 2009 17:48:36 +0000</pubDate>
		<dc:creator>tobbez</dc:creator>
				<category><![CDATA[Computers]]></category>

		<guid isPermaLink="false">http://blog.ryara.net/?p=93</guid>
		<description><![CDATA[I wrote an ebuild for the broadcatching library libsummer, that recently released version 0.1.0: # Copyright 1999-2009 Gentoo Foundation # Distributed under the terms of the GNU General Public License v2 # $Header: $ DESCRIPTION="A broadcatching library" SRC_URI="http://flukkost.nu/libsummer/${P}.tar.bz2" HOMEPAGE="http://wrya.net/services/trac/summer/" KEYWORDS="~x86 &#8230; <a href="http://blog.ryara.net/2009/03/28/ebuild-for-libsummer/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>I wrote an ebuild for the broadcatching library <a href="http://wrya.net/services/trac/summer/">libsummer</a>, that recently <a href="http://wrya.net/services/mailman/pipermail/summer/2009-March/000001.html">released</a> version 0.1.0:<br />
<code>
<pre>
# Copyright 1999-2009 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
# $Header: $

DESCRIPTION="A broadcatching library"
SRC_URI="http://flukkost.nu/libsummer/${P}.tar.bz2"
HOMEPAGE="http://wrya.net/services/trac/summer/"
KEYWORDS="~x86 ~amd64"
SLOT="0"
LICENSE="LGPL-2"
IUSE="bittorrent doc python"

DEPEND=">=dev-libs/glib-2.18.4
        >=net-libs/libsoup-2.24.3
        dev-libs/libxml2
        python? ( >=dev-python/pygobject-2.15.4 )
        bittorrent? ( >=net-libs/rb_libtorrent-0.14.1 )
        doc? ( dev-util/gtk-doc )"

RDEPEND="${DEPEND}"

RESTRICT="mirror"

src_compile() {
        econf $(use_enable bittorrent) $(use_enable python) $(use_enable doc gtk-doc) || die "econf failed"
        emake || die "emake failed"
}

src_install() {
        emake install DESTDIR="${D}" || die "Install failed"
        dodoc ChangeLog NEWS README AUTHORS
}</pre>
<p></code><br />
Download available <a href='http://blog.ryara.net/files/libsummer-0.1.0-ebuild.tar.bz2'>here</a>. To use unpack directly to your portage overlay.</p>
<p>Note: If you want the bittorrent functionaliy you will have to unmask net-libs/rb_libtorrent-0.14.1. It&#8217;s hard masked because it breaks a lot of packages relying on 0.13. Libsummer, however, was built on 0.14.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.ryara.net/2009/03/28/ebuild-for-libsummer/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Mailman with lighttpd and Postfix on Gentoo</title>
		<link>http://blog.ryara.net/2009/03/27/mailman-with-lighttpd-and-postfix-on-gentoo/</link>
		<comments>http://blog.ryara.net/2009/03/27/mailman-with-lighttpd-and-postfix-on-gentoo/#comments</comments>
		<pubDate>Fri, 27 Mar 2009 00:38:41 +0000</pubDate>
		<dc:creator>tobbez</dc:creator>
				<category><![CDATA[Computers]]></category>
		<category><![CDATA[gentoo]]></category>
		<category><![CDATA[lighttpd]]></category>
		<category><![CDATA[mailman]]></category>
		<category><![CDATA[postfix]]></category>

		<guid isPermaLink="false">http://blog.ryara.net/?p=67</guid>
		<description><![CDATA[This post details how to setup mailman using lighttpd and postfix on gentoo. Before starting I assume that you have: * Lighttpd setup and working * Postfix setup to handle mail from one domain * MX records setup for the &#8230; <a href="http://blog.ryara.net/2009/03/27/mailman-with-lighttpd-and-postfix-on-gentoo/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>This post details how to setup mailman using lighttpd and postfix on gentoo.</p>
<p>Before starting I assume that you have:<br />
* Lighttpd setup and working<br />
* Postfix setup to handle mail from one domain<br />
* MX records setup for the subdomain you want to use for lists</p>
<p>First, we need to install mailman, but before we do that we need to make sure it uses the right UID and GID (lighttpd) instead of apache, which is the default. To do this append </p>
<p><code>
<pre>MAILMAN_CGIGID="lighttpd"
MAILMAN_CGIUID="lighttpd"
</pre>
<p></code><br />
to <strong>/etc/make.conf</strong> and then proceed to install mailman:</p>
<p><code>
<pre># emerge mailman</pre>
<p></code></p>
<p>Now it&#8217;s time to configure lighttpd. This we do by adding the following to <strong>/etc/lighttpd/lighttpd.conf</strong>:</p>
<p><code>
<pre>alias.url += (
          "/services/mailman/mailman-icons" => "/usr/lib64/mailman/icons/",
          "/services/mailman/pipermail" => "/var/lib/mailman/archives/public/",
          "/services/mailman" => "/usr/lib64/mailman/cgi-bin/",
)

$HTTP["url"] =~ "^/services/mailman" {
        cgi.assign = (
                "/admin" => "",
                "/admindb" => "",
                "/confirm" => "",
                "/create" => "",
                "/edithtml" => "",
                "/listinfo" => "",
                "/options" => "",
                "/private" => "",
                "/rmlist" => "",
                "/roster" => "",
                "/subscribe" => "")
        server.indexfiles = ("listinfo", "index.html")
}
$HTTP["url"] =~ "^/services/mailman/pipermail/" {
             dir-listing.activate = "enable"
             dir-listing.hide-dotfiles = "enable"
             server.follow-symlink = "enable"
}
</pre>
<p></code><br />
I choose not to serve mailman from a vhost, if you want to do that you&#8217;ll need to change the above accordingly. Otherwise you&#8217;ll just have to change the url matches and aliases to reflect from where you want to host mailman. You will also need to make sure that the alias and cgi modules are enabled (located at the top of <strong>lighttpd.conf</strong>).</p>
<p>The next thing to configure is mailman itself. Append the following to <strong>/etc/mailman/mm_cfg.py</strong>:</p>
<p><code>
<pre>MTA = 'Postfix'
DEFAULT_EMAIL_HOST = 'lists.example.tld'
DEFAULT_URL_HOST = 'example.tld'
DEFAULT_URL_PATTERN = 'http://%s/services/mailman/'
add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
IMAGE_LOGOS = '/services/mailman/mailman-icons/' 

POSTFIX_STYLE_VIRTUAL_DOMAINS = [DEFAULT_EMAIL_HOST]

PUBLIC_ARCHIVE_URL = 'http://%(hostname)s/services/mailman/pipermail/%(listname)s'
</pre>
<p></code><br />
You should set <code>DEFAULT_EMAIL_HOST</code> to the subdomain you want your lists to use, <code>DEFAULT_URL_HOST</code> to the host from which you will serve the mailman web pages, and change <code>DEFAULT_URL_PATTERN</code>, <code>IMAGE_LOGOS</code>, <code>PUBLIC_ARCHIVE_URL</code> so that they are consistent with your settings in <strong>lighttpd.conf</strong>. The call to <code>add_virtualhost</code> is need when you change either of the <code>_HOST</code> variables like this.</p>
<p>Continuing, there is a few things we need to do as the mailman user. First install the cron jobs:</p>
<p><code>
<pre># su - mailman
mailman $ cd cron
mailman $ crontab crontab.in
mailman $ cd ..
</pre>
<p></code><br />
Then set the site password:</p>
<p><code>
<pre>mailman $ bin/mmsitepass
</pre>
<p></code><br />
The site password works instead of any other password in the mailman installation, and is used to adminstrate it.</p>
<p>Next we create the site-wide mailing list, which is needed for proper operation of mailman:</p>
<p><code>
<pre>mailman $ bin/newlist mailman
</pre>
<p></code><br />
And logout from the mailman account and continue&#8230;</p>
<p>&#8230;with configuring postfix. This is as simple as adding the following two lines to <strong>/etc/postfix/main.cf</strong>:</p>
<p><code>
<pre>virtual_alias_domains = lists.example.tld
virtual_alias_maps = hash:/var/lib/mailman/data/virtual-mailman
</pre>
<p></code></p>
<p>Once again replacing lists.example.tld with the subdomain you want your lists to use.</p>
<p>Now we only need to reload postfix, start mailman and add it to the default runlevel:</p>
<p><code>
<pre># /etc/init.d/postfix reload
# /etc/init.d/mailman start
# rc-update add mailman default
</pre>
<p></code><br />
Congratulations, you should now have a working mailman install!</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.ryara.net/2009/03/27/mailman-with-lighttpd-and-postfix-on-gentoo/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Quake Live</title>
		<link>http://blog.ryara.net/2009/02/27/quake-live/</link>
		<comments>http://blog.ryara.net/2009/02/27/quake-live/#comments</comments>
		<pubDate>Fri, 27 Feb 2009 02:01:41 +0000</pubDate>
		<dc:creator>tobbez</dc:creator>
				<category><![CDATA[Games]]></category>

		<guid isPermaLink="false">http://blog.ryara.net/?p=56</guid>
		<description><![CDATA[So today I got around to trying out Quake Live, which went into open beta the other day. If you didn&#8217;t know already, Quake Live is very similiar to Quake 3, with the exception that it&#8217;s played in a browser. &#8230; <a href="http://blog.ryara.net/2009/02/27/quake-live/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>So today I got around to trying out <a href="http://www.quakelive.com/">Quake Live</a>, which went into open beta the other day. If you didn&#8217;t know already, Quake Live is very similiar to Quake 3, with the exception that it&#8217;s played in a browser.</p>
<p>My first impression is that it seems to have quite some potential, however I won&#8217;t be playing it in the near future, as there&#8217;s too many bugs left to be able to enjoy it properly. For example, I couldn&#8217;t even play through the &#8220;warmup match&#8221;<sup>[<a href="http://blog.ryara.net/2009/02/27/quake-live/#footnote_0_56" id="identifier_0_56" class="footnote-link footnote-identifier-link" title="You play against a bot to estimate your skill level, so QL can set you up against opponents with a similiar skill level.">1</a>]</sup> without QL crashing several times (in both Firefox and IE7, which are the only supported browsers at the moment).</p>
<p>So now I&#8217;m looking forward to trying it again in a couple of months or so.</p>
<ol class="footnotes"><li id="footnote_0_56" class="footnote">You play against a bot to estimate your skill level, so QL can set you up against opponents with a similiar skill level.</li></ol>]]></content:encoded>
			<wfw:commentRss>http://blog.ryara.net/2009/02/27/quake-live/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
	</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using apc
Page Caching using apc
Database Caching using apc
Object Caching 709/829 objects using apc

Served from: blog.ryara.net @ 2012-02-05 08:00:10 -->
