The .TEL Discussion Thread

[brendan52190]

Hi

For this, let's assume that .tel will not be a total flop.

What type of keywords will be most valuable for this extension? Will it be geographical keywords, like newyork.tel, losangeles.tel, etc, or what else?

 

[plaggypig]

While I see the potential interest of .tel for some uses (starting with having one's own information available in one place and having just to print myname.tel on a business card, without the need to add anything else, at some point in the near future), I am somewhat perplexed by the idea of buying LLL or LLLL .tel names. If this can be shared, which kind of use do you have in mind when buying such names unless they are acronyms for your name or your company's name? If some who do buy such names could explain, this would interest me!

I haven't taken this route personally, but I guess the logic is that plenty of businesses use LLL acronyms for their trading names. The same is probably also true of LLLL, but to a lesser extent?

I think there are probably also still a lot of opportunities to pick up category generics in different languages - different cultures have their own unique customs/services that maybe nobody has thought of yet.. either people with understanding of these, or those willing to research them, could benefit. And in any event, reading through random Wikipedia articles is a fun exercise

 

[chader144]

While I see the potential interest of .tel for some uses (starting with having one's own information available in one place and having just to print myname.tel on a business card, without the need to add anything else, at some point in the near future), I am somewhat perplexed by the idea of buying LLL or LLLL .tel names. If this can be shared, which kind of use do you have in mind when buying such names unless they are acronyms for your name or your company's name? If some who do buy such names could explain, this would interest me!

I will try to give you idea of my thought process on the LLL.tel...
so no brainer if it is an acroynm of your company's name.

My thoughts:

• 3 letters in majority of tld's are some of the first to go and rarest to find
• Easy to make acroynms from
• when typing on a mobile device, inputting in 6 characters is shorter then a phone number (555-5555)vs (LLL.tel) "course you could argue to count the taps on the keys for the letters"
  

ex:
Alt.tel {(1-A) + (3-L) + (1-T) + (1-.) +(1-T)+(2-E)+(3-L) = 12 taps}
{1-555-555-5555) = 11 taps}

 

[onspec]

What if...

This from a healthy, opportunistic skeptic point of view...

I assume that all Telsters know the potential benefits of getting with the plan as early as possible.

My question is: what if disaster strikes? Massive use brings down the servers. Security breaches. Denial of service attacks, etc.

It would be reassuring if Telnic offered up what plans they have in place to avoid such calamities in the first place and to recover/restore the systems and integrity afterwords.

Cheers,

 

[cobo]

.TEL Domainer Breaks Dynadot !?!?

It is possible that I broke Dynadot early this morning.
I'm very sorry if I did.
I certainly did not intend to break it.
I just wanted to get VID .TEL, not break Dynadot! :o :notme:

 

[chader144]

This from a healthy, opportunistic skeptic point of view...

I assume that all Telsters know the potential benefits of getting with the plan as early as possible.

My question is: what if disaster strikes? Massive use brings down the servers. Security breaches. Denial of service attacks, etc.

It would be reassuring if Telnic offered up what plans they have in place to avoid such calamities in the first place and to recover/restore the systems and integrity afterwords.

Cheers,

Preface:
I am by no means an expert...

I have never heard of a DNS root server going down or having issues with DOS attack.
You may see attacks on the actual interface providers like the domain registrar that would keep you from entering in your information.
DNS by nature is distributed.

http://en.wikipedia.org/wiki/Domain_Name_System#DNS_servers

Now we could see something like DNS cache poisoning could be a concern. But it is the same concern you should have any .com or other tld that you own.

 

[onspec]

Gotcha

Thx. And you may have answered in concert with how Telnic will, but it would be good to hear from the horses mouth on these issues.

Cheers,

 

[phase111]

Hehe, I love it!

jjj.tel is gone now.
Some LLLL.tel's left and many LLLLL.tel's left

For a bit of fun I started with xxxxx.com and kept adding x's until a .com was available. I got to about 12 before I gave up. How would you make money off xxxxxxxxxxxx.com? Is it given preference above xxx.com in search?

I decided to get the last one available, hhh.tel, lol. Wasnt going to get one of these but Im sure their rarity factor will ensure it's a good investment- only 26 possibilities when you think about it in a repeating character pattern. Wish I was faster to get the jjj.tel that soemone else grabbed first since my first name begins with that letter.

 

[plaggypig]

This from a healthy, opportunistic skeptic point of view...

I assume that all Telsters know the potential benefits of getting with the plan as early as possible.

My question is: what if disaster strikes? Massive use brings down the servers. Security breaches. Denial of service attacks, etc.

It would be reassuring if Telnic offered up what plans they have in place to avoid such calamities in the first place and to recover/restore the systems and integrity afterwords.

Cheers,

Depends which part you're looking at:

1. Telnic is using Neustar's infrastructure for the root .tel servers so there's already proven operational reliability and robustness there.

2. For TelHosting you'll have the choice between using Telnic's infrastructure, or another TelHosting provider, i.e. your registrar. This is the authoritative part of the system for adding/removing/modifying records, and for hosting the web proxy. Switching between providers will most likely be pretty straightforward.

3. If some of those nameservers go down then the network ought to adapt, and if all go down then your .tel data should still be available, because it would be distributed throughout the DNS network (so long as caches are primed somewhere along the way).

4. The friending system is the only centralised part of the system from what I understand, but it's certainly the least critical part.. in the worst case scenario an outage shouldn't mean the end of the world.

I'd also add that both Telnic and TelHosting providers have strict service levels to meet; for more information read, Technical Requirements for TelHosting [PDF]

Couple of wild thoughts:

1. Might somebody put the TelHosting part into Amazon's EC2 cloud?

2. Could you strategically place anchors around the world that periodically walk through every .tel zone, ensuring that caches are always primed everywhere? Pretty crazy Second thoughts, that would be extremely abusive!

Maybe Justin or Henri can chime in to correct anything I've gotten wrong or missed..

 

[Billy2009]

This from a healthy, opportunistic skeptic point of view...

I assume that all Telsters know the potential benefits of getting with the plan as early as possible.

My question is: what if disaster strikes? Massive use brings down the servers. Security breaches. Denial of service attacks, etc.

It would be reassuring if Telnic offered up what plans they have in place to avoid such calamities in the first place and to recover/restore the systems and integrity afterwords.

Cheers,

If Telnic crashes, I would see that to some degree as a positive. So much demand for the product!!!

 

[plaggypig]

If Telnic crashes, I would see that to some degree as a positive. So much demand for the product!!!

Um, not really - the threat is not too much demand, but a denial of service attack.

Anyway, I think Telnic has a good setup, and they employ some very talented people, so there's nothing obvious to me at this stage that's worth worrying about.

 

[Billy2009]

Um, not really - the threat is not too much demand, but a denial of service attack.

Anyway, I think Telnic has a good setup, and they employ some very talented people, so there's nothing obvious to me at this stage that's worth worrying about.

Sorry, mine was a newbie comment.

 

[Ms Domainer]

I was just about to secure kkk some time back when available and then it was gone a couple hours later when I decided to try and register it, what a shame...but not sure what I woulda done with it as im not a member, lol.

*

Really, you're MUCH better off without this one.

KKK has such a negative meaning that you would most likely be fending off angry people and hate emails/mail. I once worked for an organization that often tagged its reports with AAA, BBB, etc., but they skipped KKK. No kidding.

Consider it a bullet missed.



*

 

[phase111]

*

Really, you're MUCH better off without this one.

KKK has such a negative meaning that you would most likely be fending off angry people and hate emails/mail. I once worked for an organization that often tagged its reports with AAA, BBB, etc., but they skipped KKK. No kidding.

Consider it a bullet missed.



*

Cheers, your probably right on that one.

 

[kukgle]

Right, here would be the final countdown to see .TEL in real version on 6th Mar (no later than).

================== 4 Day lefts ==================

 

[hullswingerscom]

i did think we would see more domainers website promoting there dot tel,you need on of these to get users on your tel database.

 

[justinhayward]

Depends which part you're looking at:

1. Telnic is using Neustar's infrastructure for the root .tel servers so there's already proven operational reliability and robustness there.

2. For TelHosting you'll have the choice between using Telnic's infrastructure, or another TelHosting provider, i.e. your registrar. This is the authoritative part of the system for adding/removing/modifying records, and for hosting the web proxy. Switching between providers will most likely be pretty straightforward.

3. If some of those nameservers go down then the network ought to adapt, and if all go down then your .tel data should still be available, because it would be distributed throughout the DNS network (so long as caches are primed somewhere along the way).

4. The friending system is the only centralised part of the system from what I understand, but it's certainly the least critical part.. in the worst case scenario an outage shouldn't mean the end of the world.

I'd also add that both Telnic and TelHosting providers have strict service levels to meet; for more information read, Technical Requirements for TelHosting [PDF]

Couple of wild thoughts:

1. Might somebody put the TelHosting part into Amazon's EC2 cloud?

2. Could you strategically place anchors around the world that periodically walk through every .tel zone, ensuring that caches are always primed everywhere? Pretty crazy Second thoughts, that would be extremely abusive!

Maybe Justin or Henri can chime in to correct anything I've gotten wrong or missed..

We are using Anycast (http://en.wikipedia.org/wiki/Anycast) for best routing to several proxy pages that will both optimize access as well as provide resillience, combined with Neustar's Ultra Services for DNS with distributed servers in a number of different territories.

Interesting questions re: Amazon however - thanks!

 

[hullswingerscom]

thank the lord for wikipedia

 

[aliencafe]

Just wanted to stop in and Say Thanks To Henri Asseily and Justin Hayward for the replies regarding Apps and the Telnic Marketing.

Appreciate the update!

Ratings.tel

haha FiveStar.Ratings.tel

 

[hasseily]

Re. Amazon:

The Telhosting software is an open source Apache/Java/DB setup that runs under Linux/Win/OSX where the DB can be pretty much anything that has a JDBC connector. We've tested it with Postgres and Mysql.

Now running that under an Amazon setup, you'd need persistence of the DB engine. You'd have to put the DB engine under EBS (http://aws.amazon.com/ebs/). The Apache/Java part can run under standard EC2 instances.

So yes, using Amazon should work.

 

[lexisdomains]

Free .TEL Suggestions

Free 1 word .TEL suggestions:

1. Reminder.tel
2. Baja.tel

I'll post a few others later.