I'm really beginning to like Google Chrome. It is definitely fast, loads web pages quickly, and uses just about the right amount of memory. The only caveat I've encountered is that there are still not many quality extensions available. Hopefully that will be fixed soon.

Anyone remember the Gopher protocol? I don't---at least, I don't remember it at its height. I first came across gopher in 1999, but only really started exploring it about five years ago, well after most nodes had been shuttered and their content moved to http. But even in its reduced form, there was a charm about gopher that drew me in, and which has taken root. And so, every so often, I wander through gopherspace, just to see what might be new, or old, or forgotten, or simply to enjoy the peace...

Programmes: elinks
Files to edit: ~/elinks/elinks.conf

URI passing allows a frame, link, or tab in elinks to be opened in another browser (say, Firefox, or Konqueror). It can be quite helpful when dealing with those sites that have not yet embraced the Any-Browser philosophy, or for which image-viewing (either consol- or X-based) does not work.

There are two ways to enable URI passing in elinks, the menu way, and the editor way. I'll be using the editor way here....

Programmes: elinks, fbida
Files to edit: ~/.elinks/elinks.conf

Start by installing a suitable image viewer. I use fbida, as it provides both a framebuffer-, and X-based image viewer (fbi and ida respectively).

Next, add some MIME types to elinks.conf.

...

web page loads as follows
1.when you type in the url in the address bar,resolver,the program in browser sends it to dns server.
2.the dns server looks up the url in its database and returns the corresponding ip address of that url
3.the browser now forms a TCP connection and content transfer takes place.
4.then the browser interprets the content.

the time taking things in this process are dns lookup and content transfer,interpretation.
there is nothing...