<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" 
      xmlns:thr="http://purl.org/syndication/thread/1.0">
  <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/reliance.php" />
  <link rel="self" type="application/atom+xml" href="http://www.readwriteweb.com/atom.xml" />
  <id>tag:,2008:/1/tag:72.47.210.69,2004://1.4244-</id>
  <updated>2008-09-24T12:29:07Z</updated>
  <title>Comments for Reliance</title>
  
  <generator uri="http://www.sixapart.com/movabletype/">Movable Type 4.1</generator>
  <entry>
    <id>tag:72.47.210.69,2004://1.4244</id>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/reliance.php" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.readwriteweb.com/cgi-bin/mt/mt-atom.cgi/weblog/blog_id=1/entry_id=4244" title="Reliance" />
    <published>2004-08-03T18:28:41Z</published>
    <updated>2007-12-16T23:15:34Z</updated>
    <title>Reliance</title>
    <summary> The thing about web technology - and computing in general - that continues to frustrate me, is that it forces me to rely on hardware and software that is often outside of my direct control. It&apos;s all very well embracing the server side and using browser-based products like Movable Type and Bloglines, as I...</summary>
    <author>
      <name>Richard MacManus</name>
      <uri>http://www.readwriteweb.com</uri>
    </author>
    
    <category term="Authoring Tools" />
    
    <content type="html" xml:lang="en" xml:base="http://www.readwriteweb.com/">
      <![CDATA[<p><img class="image" width="200" height="189" alt="Extra Limbs"
src="http://www.readwriteweb.com/images/extra_limbs.jpg" /></p>
<p>The thing about web technology - and computing in general - that continues to
frustrate me, is that it forces me to rely on hardware and software that is often outside
of my direct control. It's all very well embracing the server side and using
browser-based products like Movable Type and Bloglines, as I do. But it does mean I rely
on the people who control the servers I use. For example, I've been trying to contact my
web server hosts for the past week. They're based in the US and I've sent them a flurry
of emails... but no response. It's holding up the release of my new topic-focused blog.
And then this morning I notice that my website is down due to a server issue. And I'm
helpless, because I don't control the server.</p>
<p>The moral for living on the server side is
always to <b>Back Up Your Data</b>. Even so, when you rely on <b>services</b> - it's
about <i>more</i> than data. It's almost like the servers I rely on are a part of me.
Like extra limbs. Except in the back of my mind, I know the limbs can go dead or start
twitching uncontrollably at any time. Or even fall off!</p>

<p>Anyway there is a point to this macabre little rant (besides venting my frustration at
my web hosting company). Radio Userland's just appointed <a
href="http://houseofwarwick.com/2004/08/02.html#a854">Steve Kirks as Product Manager</a>
and Steve has written <a href="http://radio.userland.com/letterToUsers">a promising
letter</a> outlining the actions he'll be taking to improve the Radio Userland product.
This is great news for Radio users, even if it's at least 2 years late. <a
href="http://marc.blogs.it/archives/2004/08/i_want_my_old_b.html">Like Marc Canter</a>, I
used to use Radio - a desktop application - to publish my weblog. In May I swapped to
Movable Type, a server-side app. The big advantage of a desktop app is that it gives you
more control, or at least it is one step removed from the reliance on a server. If the
server goes down, you can at least continue to run the product on your desktop even if
you can't publish your content. So your extra limbs continue to work, albeit in a
restricted manner if the server is down.</p>

<p>I liked Radio, but decided to undergo a weblog transplant operation in May - opting for a
more flexible blogging limb with enhanced functionality. <a
href="http://www.readwriteweb.com/archives/001838.php">I wrote a long post at the
time</a> that outlined why I moved from Radio to MT, which would be a useful reference to
Steve now.</p>
<p>But the flexibility I got out of my new blogging limb came at the cost of
increased reliance on my web server, which I sometimes feel isn't attached to me as
closely as I'd like. Radio used to be marketed as a "personal web server" (not sure if it
still is), which implies that the server is attached to you personally rather than
being something you remote control from afar via an Internet connection. I have to admit,
<i>sometimes</i> living on the desktop makes your extra limbs feel more naturally a part
of you.</p>]]>
      
    </content>
  </entry>

  <entry>
    <id>tag:72.47.210.69,2004://1.4244-comment:35486</id>
    <thr:in-reply-to ref="tag:72.47.210.69,2004://1.4244" type="text/html" href="http://www.readwriteweb.com/archives/reliance.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/reliance.php#c35486" />
    <title>Comment from Steve Kirks on 2004-08-03</title>
    <author>
        <name>Steve Kirks</name>
        <uri>http://steve.userland.com</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://steve.userland.com">
        <![CDATA[<p>Thanks for the pointer to the outline about moving to MT.  I'll go through it in depth and add what I can to the roadmap for Radio.  All of the points are valid and well written, plus I considered abandoning Radio for the same reasons.  I never could quite leave it because of it's versatility.  Combined with an always-on Internet connection and a dyndns.org domain, I get MT-like benefits and ultimate control.</p>

<p>It will get better and it will be because of users, not promises.  I'm drawing the map; users will take the journey.</p>

<p>Steve</p>]]>
    </content>
    <published>2004-08-03T21:02:56Z</published>
  </entry>

</feed>