<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/css" href="/stylesheets/rss.css"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/">
  <channel>
    <title>Trypticon: Still Worried about ZIM</title>
    <link>http://trypticon.org/articles/2005/11/21/still-worried-about-zim</link>
    <language>en-us</language>
    <ttl>40</ttl>
    <description>If it ain't broke, break it.</description>
    <item>
      <title>Still Worried about ZIM</title>
      <description>&lt;p&gt;Well, here we are again with yet another 5-day downtime for &lt;a href="http://jabber.zim.net.au/" title="Jabber.ZIM Web Page"&gt;Jabber.ZIM&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;It&amp;#8217;s a bit depressing to be the so-called admin of a server which continuously experiences this kind of downtime &amp;#8212; we used to have such good uptime, too &amp;#8212; but the reality of the whole thing is that a lot of factors stack up to prevent me having the control I need to keep the server running.&lt;/p&gt;

&lt;p&gt;It&amp;#8217;s currently hosted at ZIM itself, meaning that the odds of moving it to some other host is minimal (although starting a completely new server is something I&amp;#8217;ve been considering for a long time now.)  I don&amp;#8217;t own the ZIM domain name, so I can&amp;#8217;t just redirect the entries to point them somewhere else.&lt;/p&gt;

&lt;p&gt;Next, ZIM itself is actually a virtual ISP, and the server which runs the Jabber service occasionally crashes (I guess BSDs aren&amp;#8217;t as stable as the Slashdot BSD fanatics would like us to believe) and thus I become unable to fix it as I have no authority to go and do so, nor ability to sway the ISP to do so for me.&lt;/p&gt;

&lt;p&gt;And finally, occasionally we get situations where the machine itself is completely healthy and the Jabber server is up, but the Internet simply stops routing packets to it.&lt;/p&gt;

&lt;p&gt;All of these factors result in an awful lot of things which can go wrong which are all outside my control, and in some cases outside the control of ZIM itself.&lt;/p&gt;

&lt;p&gt;I guess the question is&amp;#8230; is it &lt;em&gt;really&lt;/em&gt; impossible to move this to another host?  ZIM would obviously have no direct connection with the server anymore, and we&amp;#8217;d have to put up banners for the new sponsor, but otherwise nothing would really change as long as we pulled all the spools over to the new server.&lt;/p&gt;

&lt;p&gt;I just don&amp;#8217;t know how to go about begging for sponsorship for something like this.  Maybe it&amp;#8217;s time to start learning.&lt;/p&gt;

&lt;p&gt;Jabber uses (using statistics from jabber.org) approximately 100 bits per second per user (outbound, slightly less inbound.)  It would take, then, around 4,000 users to max out a 512kbit ADSL connection, and ZIM has/had something like 150-200 frequent users so in reality it would be using only the tiniest amount of bandwidth.  Space requirements aren&amp;#8217;t a major issue, though CPU and memory requirements may be.  Overall the requirements aren&amp;#8217;t too harsh, so perhaps it wouldn&amp;#8217;t hurt to start prodding a few ISPs to see how they feel about hosting this kind of thing.&lt;/p&gt;

&lt;p&gt;Then we just need to see if ZIM is willing to relinquish control of the server which has their domain name in it&amp;#8230;&lt;/p&gt;</description>
      <pubDate>Mon, 21 Nov 2005 12:53:00 +1100</pubDate>
      <guid isPermaLink="false">urn:uuid:9f4306eb-807c-4e2f-856c-cd6c6c9a520d</guid>
      <author>Trejkaz</author>
      <link>http://trypticon.org/articles/2005/11/21/still-worried-about-zim</link>
      <category>zim</category>
      <category>jabber</category>
    </item>
  </channel>
</rss>
