From: Charles Forsyth <forsyth@caldo.demon.co.uk>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Verisign's new "all your unregistered domains belong to us" trick
Date: Wed, 17 Sep 2003 08:17:37 +0100 [thread overview]
Message-ID: <27501dcbdc3060e6cf3b7d7da2c25a10@caldo.demon.co.uk> (raw)
In-Reply-To: <3F6714C1.3060604@plan9.bell-labs.com>
[-- Attachment #1: Type: text/plain, Size: 26 bytes --]
have they patented it yet?
[-- Attachment #2: Type: message/rfc822, Size: 2720 bytes --]
From: Russ Cox <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Verisign's new "all your unregistered domains belong to us" trick
Date: Tue, 16 Sep 2003 09:48:49 -0400
Message-ID: <3F6714C1.3060604@plan9.bell-labs.com>
David Presotto wrote:
>I'm actually mailing everyone I know to get it to stop. Anyone
>know the reason for it? Is verisign incompetent, hacked, or
>trying to circumvent something?
>
it's a top story on google news. apparently they're
trying to get extra web traffic?
next prev parent reply other threads:[~2003-09-17 7:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-16 10:52 matt
2003-09-16 10:16 ` boyd, rounin
2003-09-16 10:37 ` Lucio De Re
2003-09-16 11:07 ` Lucio De Re
2003-09-16 12:33 ` David Presotto
2003-09-16 13:48 ` Russ Cox
2003-09-16 14:54 ` [9fans] Verisign's new "all your unregistered domains belong matt
2003-09-16 13:58 ` paurea
2003-09-16 15:03 ` matt
2003-09-16 15:18 ` northern snowfall
2003-09-18 14:38 ` David Presotto
2003-09-18 17:05 ` northern snowfall
2003-09-17 7:17 ` Charles Forsyth [this message]
2003-09-17 14:06 ` [9fans] Verisign's new "all your unregistered domains belong to us" trick William Josephson
2003-09-16 14:28 ` Scott Schwartz
2003-09-16 15:33 ` Dan Cross
2003-09-16 14:39 ` matt
2003-09-18 14:34 ` David Presotto
2003-09-18 19:58 ` Lyndon Nerenberg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=27501dcbdc3060e6cf3b7d7da2c25a10@caldo.demon.co.uk \
--to=forsyth@caldo.demon.co.uk \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).