I usually code my html/javascript in a simple text editor like notepad++. I usually open it in IE ( Internet Explorer) or FF to test it. Firefox doesn’t have any problems in opening the local files. But IE doesnt belive my local files. Everytime I open a local html file using IE I will get a warning.

I need to unblock it for IE to execute javascript. I found a simple solution to fix this when working offline. Add the this line to top of your html file
<!-- saved from url=(0013)about:internet -->This line will allow IE bypass the security warning and execute the javascript.
For more information on this go to microsoft technet.

Sortable Table is a great javascript library for client side sorting of HTML table. Its under Apache 2.0 license so its very compatible. Recently I faced a bug when sorting date columns. It was not sorting the dates properly. After some debugging I got to know that the library assumes the date format to be yyyy-mm-dd. See line 287 or search for case “date”.

var parts = sText.split("-");
var d = new Date(0);
d.setFullYear(parts[0]);
d.setDate(parts[2]);
d.setMonth(parts[1] - 1);
return d.valueOf();
Now to make it compatible with your date format say mm/dd/yyyy. You need to update it as

var parts = sText.split(" ");
parts[0] = sText;
var date1 = parts[0].split("/");
var d = new Date(0);
d.setFullYear(1970 + parseInt(date1[2]), date1[0], date1[1]);
d.setHours(0);
d.setMinutes(0);
return d.valueOf();
The new version is v1.12 and it still has this problem. The code in the new version is
SortableTable.toDate = function (s) {
var parts = s.split("-");
var d = new Date(0);
d.setFullYear(parts[0]);
d.setDate(parts[2]);
d.setMonth(parts[1] - 1);
return d.valueOf();
};
You need to update this snippet to reflect your date format. You can reuse the above code. I am thinking of rewriting date parsing part to parse the date in any given format. So the fix becomes much generic. Will update once I do that.

Google Reader’s share tools on the other hand republish full blogs post for all to read without obtaining permission from blog publishers. So-called link blogs in Reader already break copyright and in a small way undermine blogs and content creators. If Google offers a comment service on shared items they are in effect creating copyright infringing blogs; after all they all have chronological entries and comments so they all look like blogs, even if they don’t provide a fully customizable CMS.-TechCrunch

A leaked Google video resulted in a post on Google Blogscoped . And plans of Google to introduce commenting system inside the shared reader items has sparked many posts including the one above by TechCrunch.

I doubt by aggregating and sharing the data Google/Users will be breaking any copyright rules. Feeds are given out for aggregating. If somebody is scared of their data being used should stop giving full feeds and go for partial feeds. They can even use the copyright notice or an url at the end of the post to make sure they get the credit. I am OK with people sharing my content in full/partial as long as they credit me and dont allow the search engines to index the aggregated content.

Coming back to comments on shared items. The system is similar to Facebook Notes App where you can import any feed ( but you should have the rights to import) and users can comment on it. These comments stay on Facebook and doesnt reach the original blogpost. If this is the concern of TechCrunch then I am with them. I would like Google to integrate the orginal blog comments into the reader. It could be either by extending the RSS/ATOM feed structure to include comments or simply linking to the original blog comment link. How about import/export comments functionality?

Further Reading:
There are many other reactions on the web about link blogging. You may want to read that of Scoble, greatest Google Reader Link Blogger.
On the same day comes another discussion between full tex feed v/s partial text feed at Problogger. In the debate are Gina Trapani of Lifehacker for partial feeds against Rick Klau from Feedburner supporting full text.

Inspired Mashable Gmail Toolbox and other Toolbox series. Here I have my DNS toolbox listed below. I will probably update the list when I get more.

1. DNSStuff: Useful for DNS Admins and web Admins
2. Some free services are DNSreport, DNS Lookup (A, MX, NS, SOA, etc.). Traceroute, Email Test and many more ( around 20+ free services)
3. OpenDNS: OpenDNS is a safer, faster, smarter and more reliable way to navigate the Internet. Free DNS service. Our service is free and requires nothing to download.
4. Who is Hosting? Who Is Hosting This is a tool that enables you to find out who is hosting any web site. Simply type in any domain name, and you’ll get a link to the company that’s hosting this particular domain.
5. No-IP : Reliable dynamic DNS and web redirection for your own domain name. Many other services related to Dynamic IP binding.
6. Free DNS:Free DNS Hosting, Dynamic DNS Hosting, Static DNS Hosting, subdomain and domain hosting.
7. DynDNS - A free DNS service for those with dynamic IP addresses
8. MX Toolbox:Everything about MX record lookup
9. Tutorial : Listed and explained all DNS parameters. A must read for DNS admins.
10. Tutorial: DNS tips and tricks

Its a “touch me not” plant flower. Taken at Office.