[vox] Self-replying [Was "XFree86 Core Team Disbands" (?)]

[Karsten M. Self]

--lQSB8Tqijvu1+4Ba
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

on Fri, Jan 02, 2004 at 12:51:42AM -0800, Jeff Newmiller (jdnewmil@dcn.davi=
s.ca.us) wrote:
> On Thu, 1 Jan 2004, Tim Riley wrote:
>=20
> > ME wrote:
> >=20
> > > Look! My (lack of) nettiquette is showing:
> > > (replying to myself)
> >=20
> > Why is adding an additional thought after pressing the <send>
> > button bad nettiquette?
>=20
> I can think of two reasons off the top of my head:
>=20
> a) pushing the send button too quick is something to be frowned upon... it
> suggests that you do not respect your readers' time spent interpreting
> your thoughts.  Specifically, having to thread two messages together to
> identify a complete thought may not always be possible, since related
> messages may not always be presented together.
>=20
> b) if your audience is so uninterested in your topic that there is no one
> else to reply to after your message, then perhaps you shouldn't be talking
> to yourself on that topic in that forum.
>=20
> I don't think either of these sufficient justification to condemn someone
> for replying to themselves once in awhile, but I do think they at least
> suggest that doing so should be a rare event.

I've engaged in the practice myself on occasions when working through a
technical problem for which it appears there's no recorded solution
and/or nobody on channel with useful advice.  In which case, I'll detail
the problem, initially, provide additional context, if this seems
appropriate, and if I _do_ find a solution, post this.  On the basis
that comprehensive indices such as Google turn the Internet into my
filing cabinet.

I've received several comments over the years thanking me for particular
solutions posted in this way.  One that comes to mind was a problem in
which my video card (S3 ViRGE VX) locked on any subsequent invocation of
X (either serial or parallel), and the fix was to *not* use the
recommended video driver.  Lonely set of comments out on
comp.os.linux.x, which was still getting unsolicited thanks years later.

    http://tinyurl.com/2topx

=2E..if anyone's interested ;-)


Peace.

--=20
Karsten M. Self <kmself@ix.netcom.com>        http://kmself.home.netcom.com/
 What Part of "Gestalt" don't you understand?
    The black hat community is drooling over the possibility of a secure
    execution environment that would allow applications to run in a
    secure area which cannot be attached to via debuggers.
    - Jason Spence, on Palladium aka NGCSB aka "Trusted Computing"

--lQSB8Tqijvu1+4Ba
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQE/9ccqefG8443k044RAp6eAKCHEc/WDSVAgcuqfsk7iBsyoyAo+ACeJF9x
DAOsZEZFnPntxKgIr03NYK0=
=iHL0
-----END PGP SIGNATURE-----

--lQSB8Tqijvu1+4Ba--