[115665] in North American Network Operators' Group
RE: Using twitter as an outage notification
daemon@ATHENA.MIT.EDU (Tomas L. Byrnes)
Sun Jul 5 00:02:24 2009
Date: Sat, 4 Jul 2009 21:01:04 -0700
In-Reply-To: <!&!AAAAAAAAAAAuAAAAAAAAAKTyXRN5/+lGvU59a+P7CFMBAN6gY+ZG84BMpVQcAbDh1IQAAAATbSgAABAAAAAyPu8hd3WYRo3ipfQ16S4+AQAAAAA=@iname.com>
From: "Tomas L. Byrnes" <tomb@byrneit.net>
To: "Frank Bulk" <frnkblk@iname.com>,
"JC Dill" <jcdill.lists@gmail.com>
Cc: nanog@merit.edu
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
>-----Original Message-----
>From: Frank Bulk [mailto:frnkblk@iname.com]
>Sent: Saturday, July 04, 2009 4:51 PM
>To: 'JC Dill'
>Cc: nanog@merit.edu
>Subject: RE: Using twitter as an outage notification
>
>So does twitter address the mass public,=20
[TLB:]=20
The whole point of Twitter is that it works with SMS.
>
>My point in another fork of this thread is that for most people, the
>traditional forms of communication are *it*. I'm not saying that
>twitter
>hasn't been used and found a way to reach the some portion of the
>population
>-- the traditional methods (announcement at top of phone tree & note on
>homepage) should be maintained and as one more additional way to
>communication. I think you mentioned that yourself a few posts ago. =
=3D)
>
>Frank
>
[TLB:] I think everyone agrees it's not an "Either/Or".=20
The argument that Twitter is a good, inexpensive, way to mass
communicate operational issues with those that are able to use it, is
kind of axiomatic.
I'm not, in general, a fan of Twitter. To me, twits are those in my
killfile (yes, I know they call it "tweets"), however, as a way of using
Other People's Money to reduce your OPEX while improving CSI, it seems
like a no-brainer to me.
