public inbox for [email protected]
help / color / mirror / Atom feedFrom: Andrew Sullivan <[email protected]>
To: [email protected]
Subject: Re: New email list for emergency communications
Date: Wed, 26 Mar 2008 09:44:49 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
<20080324120112.12a57ef7@jd-laptop>
<[email protected]>
On Wed, Mar 26, 2008 at 11:39:33AM +0100, Magnus Hagander wrote:
> I don't see a reason for us to run one private and one public server. In
I agree with that. The problem is that the protocol is actually designed so
that you don't need these infernal private servers.
> AFAIK every reasonable IM client people would use today can easily add
> two jabber accounts (or more), so I don't see the problem, really.
Part of the point of the Jabber protocol is to avoid having to track which
account you have to use to talk to which people. Having all these private
servers is taking us back to the days of GEnie, CompuServe, and other such
closed networks: you had to know which gateway (or series of gateways, in
the case of UUCP mail) to use in order to reach your party. Computers are
better at routing than humans.
A
view thread (78+ messages)
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected]
Subject: Re: New email list for emergency communications
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox