> The fact is that mp3s.com DID expire, it was mp3.com's fault, and their most > basic business processes failed. It really shouldn't matter what reason it > took a while for them to figure it out -- it could have been that they had a > perfect monitoring system that alerted someone who was killed in a car > crash. It's irrelevant. Their own record-keeping failed, and that's > inexcusable.
The domain expiring without MP3.com realizing it isn't the point here. The point is that sitefinder caused confusion (I tried going to one site and ended up at another) and caused basic monitoring techniques to fail (no matter how flawed they are) that many websites employ. These are a couple of the possible problems that I heard many people argue about regarding sitefinder. At the time it was just theory, now there is at least one case showing it did happen. I don't think anyone is saying that the expiration of the domain was Verisign or sitefinders fault.
