At 3/3/01 5:12 AM, Chuck Hatcher wrote:
>Since OpenSRS is notified every time a domain name is transferred to another
>registrar, it seems logical that this could be taken care of at that level,
>rather than by each and every RSP.
>
>How about it, OpenSRS, can you take a break from working on non-functional
>multi-lingual domains long enough to clean up some glaring defects in your
>core business?
Yeah. I first pointed out this problem last August 18th, saying that it
would lead to exactly the same billing problem NSI had:
http://www.opensrs.org/archives/discuss-list/0008/0638.html
Scott Allan replied that a solution was in the works.
Since then, people have complained almost weekly on this list about how
evil NSI is for continuing to bill domains that had been transferred
months before, etc. At one point, there was a big groundswell of support
for trying to get NSI's accreditation revoked or filing a class-action
lawsuit.
Oh, look -- it turns out OpenSRS (i.e., each RSP) does the same thing.
OpenSRS has known about it for six months and still hasn't implemented
the relatively trivial fix to flag domains that have been transferred
away.
I know I sound like a broken record, but the current state of affairs is
appalling. OpenSRS has been aware of many of these urgent issues for
months, if not a year. Look at this message:
http://www.opensrs.org/archives/discuss-list/0006/0213.html
OpenSRS staff knew last June that there would be a big problem if
automated RSP transfers were not implemented before renewals were in
progress, but the issue was ignored while huge resources were allocated
to projects like multilingual domains (which in their current
implementation are nothing more than a scheme to prey on the ignorant or
accommodate those hoping to make a quick buck on land-rush speculation).
I'm annoyed. Every company makes mistakes and has problems; that's not
what I'm complaining about. The problem is (and has been, for the last
year) that OpenSRS ignores known problems rather than fixing them.
When are things going to change?
--
Robert L Mathews, Tiger Technologies
