Hello Don,

The issue is that Tucows is OBLIGATED to consider the registrant, as a
result of their accreditation with ICANN.

OpenSRS does an excellent job balancing those functions where they
can, but their ability to do that is strictly limited.

Wednesday, April 25, 2001, 6:40:51 PM, Don Brown wrote:

> At 11:44 AM 4/25/01 -0400, you wrote:
>>That's not quite accurate. Once the registration has been paid for, ICANN
>>and therefore Tucows, has to consider it a done deal. There is no connection
>>between the non-payment of the web space/traffic and the domain name that we
>>can reliably fall-back on. This is a known shortcoming of the system we put
>>together.
>>
>>Anybody that been around for a while can attest to this - OpenSRS was a
>>hack/abomination when we released it. No one had considered doing what we
>>were doing and how we did it. The problem was, that in order for us to pull
>>it off, compromises had to be made. This is one of them.
>>
>>-rwr

> Shortcomings/Compromises can be fixed, unless they are locked in granite 
> for some other reason.

> For instance, from a pragmatic point of view, most of our customers don't 
> know how to spell byte and they think packets are those things that rats 
> carry around.  They look to us to take care of them -- it is called service 
> and that is what keeps us all in business.  After all, why would they 
> really need any of us, if they could do what we do for a living?

> To illustrate the point a bit further, about a year ago the author of the 
> canned shopping cart, which we use, decide to lock us out of the admin 
> interface for our customers' carts.  The author had noble ideals, but he 
> lived in another world, far away from the firing line where we live.  We 
> had to figure out a way to circumvent this problem and we did, but we were, 
> never-the-less, annoyed about the extra time it took us.  It was just 
> inconvenient and, after all, we were their customer -- our customers were 
> our customers and we had the burden of serving them or losing them.  The 
> unscrupulous provider, on the other hand, always loses in the end -- it 
> just takes time, but most providers do Not fall into this category - they 
> are the minority scan artists who hurt us all.  So, the approach of our 
> shopping cart author was like prosecuting mosquitos with 00 buck shot.  A 
> bit zealous, yet Nobel, but Nobel didn't work very well for their customers 
> (us) and unless we were tech enough to defeat the block, we were exposed to 
> losing customers.  The next release of the software removed the hindrance 
> to our job -- so go figure why they decided to change course.

> Equally, we think Tucows has very high ideals and that, among other things, 
> is why we chose to be a reseller.  However, we think the first order of 
> business is to serve the direct customer (we the resellers), and to shake 
> out those who are/maybe unscrupulous - which is good for all 
> concerned.  IOW, let us look out for our customers and y'all (that's a TX 
> term) look out for us.

> So, it wouldn't take a lot of rocket science programming to send the admin 
> contact an email, whenever the admin contact or the name servers were 
> changed, would it?  Those are the two ingredients to hijacking the domain 
> -- shouldn't you be doing that already, since the consumer is more 
> important than your real customer, by all appearances, anyway?

> There has to be a certain element of trust in any business deal.  From all 
> appearances, however, Tucows does not trust their resellers and that does 
> not make for a good relationship, either in the short or long term.

> Think about it.  I empower my auto mechanic with more . . .

> My opinion, FWIW.

> Thanks,

> ----
> Don Brown - Dallas, Texas USA       Internet Concepts, Inc.
> [EMAIL PROTECTED]            http://www.inetconcepts.net
> PGP Key ID: 04C99A55                  (972) 788-2364  Fax: (972) 788-5049
> Providing Internet Solutions Worldwide - An eDataWeb Affiliate
> ----



-- 
Best regards,
 William                            mailto:[EMAIL PROTECTED]


Reply via email to