We've just published the source code for "My .tel", an iPhone app for managing your .tel. I wrote it so I could switch my phone numbers as I boarded a plane, and it grew from there. It lets you add/edit/delete/reorder contact records, add/delete keywords, and synchronize your location using the phone's GPS.
The app is missing privacy management, but that will come. It's in active development and will be updated as my time permits.
Have fun with the code, it shows the usage of the Telhosting JSON API.
Here are some direct links for the app and iPhone resources:
- description of both iphone apps
- download source as an archive
- ViewSVN with SVN sources
- checkout link for SVN
- Tutorial for Sample iPhone app and SDK
Wednesday, January 07, 2009
Friday, December 19, 2008
Privacy now available on vip.tel
We updated the vip.tel public beta last night, and it now has full support for privacy. You can friend other vip.tel beta users, and decide what contact information you'd like each of your friends to see (or not).
Of course the friending APIs are now also active.
Get a free vip.tel beta account at http://www.telnic.org/vip/
Of course the friending APIs are now also active.
Get a free vip.tel beta account at http://www.telnic.org/vip/
Friday, December 12, 2008
Shortsightedness
Now that the .tel has been available to trademarks for a week, we're getting a lot of buzz and feedback in online communities.
Most of it is really good, but of course there's always the criticism. Some criticism is borne out of misunderstanding (or simply lack of reading about .tel) but some other criticism is very interesting, and shows how quickly one can jump to the seemingly obvious but wrong conclusion. More interestingly, the less technical a community, the more it embraces .tel as a great product. And vice versa. So what's the issue with techies?
Well, as soon as a techie reads "top level domain" (or the TLD acronym), she automatically associates it with "domainer money grab". As you try to explain why .tel is really fundamentally different from any other TLD, the techie will say "but you can publish your contact info hundreds of ways already!" And she doesn't see the connection between these two points, which is as follows:
In order to publish your own information in one place that is forever yours, the best (and arguably only) solution today is to use a top-level domain. If you don't use a TLD, you're subordinated to a service provider that may or may not sell you advertising, cut you off, or even go bankrupt. Then good luck telling everyone that you switched to *another* "forever" place, and listen to the snickers.
That is the reason why Telnic is using a TLD. We're not making money from hidden deals or advertising, or thinking up new business models that promise to make someone else pay for your chance to control your data. You simply pay a small price ($15/year or whereabouts) for your guaranteed freedom and control, and buy your own unique domain. A .tel TLD is the only guarantee for you to own your unique, forever, publishing platform for contact information.
Most of it is really good, but of course there's always the criticism. Some criticism is borne out of misunderstanding (or simply lack of reading about .tel) but some other criticism is very interesting, and shows how quickly one can jump to the seemingly obvious but wrong conclusion. More interestingly, the less technical a community, the more it embraces .tel as a great product. And vice versa. So what's the issue with techies?
Well, as soon as a techie reads "top level domain" (or the TLD acronym), she automatically associates it with "domainer money grab". As you try to explain why .tel is really fundamentally different from any other TLD, the techie will say "but you can publish your contact info hundreds of ways already!" And she doesn't see the connection between these two points, which is as follows:
In order to publish your own information in one place that is forever yours, the best (and arguably only) solution today is to use a top-level domain. If you don't use a TLD, you're subordinated to a service provider that may or may not sell you advertising, cut you off, or even go bankrupt. Then good luck telling everyone that you switched to *another* "forever" place, and listen to the snickers.
That is the reason why Telnic is using a TLD. We're not making money from hidden deals or advertising, or thinking up new business models that promise to make someone else pay for your chance to control your data. You simply pay a small price ($15/year or whereabouts) for your guaranteed freedom and control, and buy your own unique domain. A .tel TLD is the only guarantee for you to own your unique, forever, publishing platform for contact information.
Wednesday, December 03, 2008
.tel sunrise is ON!
The .tel sunrise just started!
The blogosphere is quite awash with comments, as was to be expected. Some are quite thoughtful, others somewhat off-base so I suppose I have to remind people that:
Privacy is fully supported: choose who sees what. Spammers will need to break 1024-bit encryption...
The blogosphere is quite awash with comments, as was to be expected. Some are quite thoughtful, others somewhat off-base so I suppose I have to remind people that:
Privacy is fully supported: choose who sees what. Spammers will need to break 1024-bit encryption...
Thursday, November 20, 2008
Testing the AJAX/JSON API
I'm testing the AJAX/JSON API outside of the Telhosting system.
What's the best way to ensure developers are happy with an API?
Simply by making an app myself using that API, of course. :)
Therefore, a new iPhone app is on the way that will let you manage your .tel directly from the iPhone. Get on the plane, and before you turn off your phone, update your .tel and tell everyone you're not available! Oh and while you're at it, use the GPS to show that you're at the airport.
At this point in the development of the app, I find the API easy to use and quite comprehensive. We made a couple of minor changes to simplify things, but otherwise I'm happy with it.
What's the best way to ensure developers are happy with an API?
Simply by making an app myself using that API, of course. :)
Therefore, a new iPhone app is on the way that will let you manage your .tel directly from the iPhone. Get on the plane, and before you turn off your phone, update your .tel and tell everyone you're not available! Oh and while you're at it, use the GPS to show that you're at the airport.
At this point in the development of the app, I find the API easy to use and quite comprehensive. We made a couple of minor changes to simplify things, but otherwise I'm happy with it.
Subscribe to:
Posts (Atom)