It's all hosted at telnic. So if they get hit by a DDoS or hacked – everyone's contact details are vulnerable. If they go out of business – the same.

I could write a scrap of PHP or ASP which anyone could host on their website – where does their business model go? A _facebook_ app could provide the same functionality.

Don't get me wrong – that it updates via DNS is a nice idea. But given the time it takes for DNS updates to propagate around the world, what's the advantage compared to just sticking the details up on your site?

Ultimately – what, in a dozen words, makes this better than me sticking a VCARD or hCard on my website?

T
(Not having a go – just genuinely confuzzeled)

http://rikkles.blogspot.com/2008/09/demo-confer…

I can set up a page like that – see http://shkspr.mobi/about.php – which has a secret URL / password to show different contact information to each person. Or, even better, you can connect to me at http://zyb.com/terenceeden and instantly know when I change my details.

Why should I pay .tel for yet another domain when I could make tel.example.com or example.com/tel ?

And what happens when my neighbour – who is also called Jonathan Jensen – wants a .tel? He either needs a hotmail-esque jon-jensen-1944.tel or chain multiple subdomains – j.onanthan.jen.sen.tel.

I think the basic idea of a unified contact manager – like zyb.com* – is a good idea. I just don't see why it needs to be attached to a (paid-for) domain.

T
*Owned by my corporate overlord, Vodafone.