Odd, I tend to send to ORG (after all, I mainly setup the lists, and
administered them for a good portion of time)...

Now, when I reply to all, well... let the TLDs fall where they may
(*cough*)

Charles Daminato
TUCOWS Product Manager
[EMAIL PROTECTED]

On Mon, 25 Jun 2001, Jack Broughton wrote:

> Hey Team,
>
> I'm finding this disussion a little comical about the philosophical
> distinctions for the 3 suffixes at OpenSRS. (.COM/NET/ORG).
>
> Know why that would be?  When I joined this list I created a little
> Netscrape mail filter to plunk all these discuss-list profundities into
> a separate folder.  Much to my surprise I found a large percentage of my
> maillist stuff wasn't being filtered properly.  A quick investigation
> led me to the discovery that a whack of folks were sending to
> [EMAIL PROTECTED] and the rest were sending to
> [EMAIL PROTECTED] (Yes... I've fixed my filter now thanks.)
>
> While the unwashed masses in the ranks of RSP-dom can be excused for a
> lack of uniformity I am surprised that the powers that be at odds on
> this issue.  (Chuckles Daminato seems to prefer [EMAIL PROTECTED]
> whilst Kenneth Joy is an ORG man. :)
>
> Tell me... is this more of the open sores of which Ross speaks? :)
>
> Jack
>
> Charles Daminato wrote:
> >
> > Yeah, but legacy attitudes prevail.  As Ross said - something to do with
> > open sores...
> >
> > Charles Daminato
> > TUCOWS Product Manager
> > [EMAIL PROTECTED]
> >
> > On Mon, 25 Jun 2001, Derek Balling wrote:
> >
> > > Except that e-mail addresses belong to people at the COMpany,
> > > (they're paid, right?).
> > >
> > > I can understand the net/com distinction, but the only place .org
> > > should have in the equation is to prevent someone from cybersquatting
> > > it. There is nothing about Tucows/OpenSRS that "doesn't fit
> > > elsewhere" (as, paraphrased, the RFC puts it)... OpenSRS is a network
> > > services provider (.NET), as well as a commercial entrprise (.COM).
> > >
> > > D
> > >
> > >
> > > At 12:39 PM -0400 6/25/01, Charles Daminato wrote:
> > > >Well, initially we had three parts to OpenSRS:
> > > >
> > > >opensrs.org - the website, information, and staff working at the
> > > >"Org"anization
> > > >opensrs.net - the servers and backend for the "Net"work
> > > >opensrs.com - for anything involving the "Com"pany
> > > >
> > > >Ross felt it appropriate (and I agree) to use these TLDs for their
> > > >intended purpose, or at least as close as possible.
> > > >
> > > >So, email addresses end in org, servers end in net, and other stuff ends
> > > >in com :)
> > > >
> > > >Charles Daminato
> > > >TUCOWS Product Manager
> > > >[EMAIL PROTECTED]
> > > >
> > > >On Mon, 25 Jun 2001, Philippe Landau wrote:
> > > >
> > > >>  it's great to have such fast support now on the list, thanks OpenSRS staff.
> > > >>
> > > >>  >> That's not funny...
> > > >>  >> https://landrush.opensrs.net/info/index.cgi?action=prereg_info
> > > >>  >> i receive "unrecognized certificate" warning both on IE 4.72.3110.4
> > > >>  >> and NN 4.7 and on Opera 5.01. Is this a normal situation for all
> > > >>  >> Tucows certs or site was not properly configured ?
> > > >>  >That's odd, it works fine for me - this is a signed Cert from Entrust,
> > > >>  >checking the details will show you that.  *hrm...*
> > > >>  my NN 4.08 mac says:
> > > >>  "Netscape does not recognize the signer of this Certificate,
> > > >>  you may decide to accept it anyway..."
> > > >>
> > > >>  something else: is there a reason for the apparent preference to use
> > > >>  OpenSRS.org over OpenSRS.net ? it seems unnecessarily misleading to me.
> > > >>
> > > >>  kind regards     philippe, http://InternetRoot.com
> > > >>
> > >
> > >
> > > --
> > > +---------------------+-----------------------------------------+
> > > | [EMAIL PROTECTED]  | "Conan! What is best in life?"          |
> > > |  Derek J. Balling   | "To crush your enemies, see them        |
> > > |                     |    driven before you, and to hear the   |
> > > |                     |    lamentation of their women!"         |
> > > +---------------------+-----------------------------------------+
> > >
>

Reply via email to