Scott.L
Top Contributor
Thanks for helping Michaelg, really appreciate the effort of highlighting that none of the other names that dropped are of any value, they had no bids, all are still available and none are high profile enough that could be used to drive any incentive for auDA to instruct afilias to fix this rather important bug. We have highlighted this on many similar names before to them with no result. The company domain was our best chance to have this serious bug fixed to make the drop catch system fair.
David, why would it be important to single out a domain with bids? It’s a “bug” manually programmed by you to exploit the domain from dropping on the day, it has nothing to do with bids on your platform.
In fact, what you proved to every watching was how easy it was for a 3rd party to run off with the loot, leaving your customers bidding on a fake drop auction. Accordingly, it calls into question the arms length dealing between each related entity, and whether or not not you have other undisclosed agreements with other registrars for registry connections.
Now whilst it's unfortunate for you to be at the epicenter of criticism about an event that you claim was beyond your control - you can't deny or shrug off the controversy you caused by proxy of you enabling this situation to occur in the first place.
In light of this event, My question to auDA would be; If terrific is licensed by auDA as a drop catcher and shares connections with other drop catchers, then why didn't auDA disclosed it to the public? Because, what we now see is a new drop catcher closed off from the public with the capacity and technology to catch names for themselves to the exclusion of all others.