Rarely Seen PICS of the 1893 Columbian Exposition

Go back in time and see how Chicago rose from the ashes of fire to host the 19th century's greatest fair, the Columbian Exposition.
If you haven't watched it yet, watch the Pinky show link above posted by ConanTL for a detailed explanation of what happened in the Colombian expedition, as well as how the fires started that burned down almost the entire area.
More...

Google-Orion

Google has bought the rights for a search algorithm developed by Ori Allon, a student at the University of New South Wales in Australia. The Age reports that Rob Pike, who is a Google engineer, was very excited about the algorithm. "This is the first time I've walked out and said: 'Wow! We should buy this stuff'. So it's pretty unique".

Orion's algorithm displays an extended snippet from each result, so you don't have to visit the site to get the answer you need.

Eric Schmidt told in a interview that Google will make "heavy, heavy investment in new search algorithms" to improve the quality of Google search.

Google still didn't decide if they integrate Orion's algorithm in their web search or they release it as a new product.

The 25 Worst Tech Products of All Time

The 25 Worst Tech Products of All Time.
The first entry in our Hall of Shame: The ISP that everyone loves to hate...=)

1. America Online (1989-2006)
2. RealNetworks RealPlayer (1999)
3. Syncronys SoftRAM (1995)
4. Microsoft Windows Millennium (2000)
5. Sony BMG Music CDs (2005)
6. Disney The Lion King CD-ROM (1994)
7. Microsoft Bob (1995)
8. Microsoft Internet Explorer 6 (2001)
9. Pressplay and MusicNet 2002
10. Ashton-Tate dBASE IV (1988)
11. Priceline Groceries and Gas (2000)
12. PointCast Network (1996)
13. IBM PCjr. (1984)
14. Gateway 2000 10th Anniversary PC (1995)
15. Iomega Zip Drive (1998)
16. Comet Systems Comet Cursor (1997)
17. Apple Macintosh Portable (1989)
18. IBM Deskstar 75GXP (2000)
19. OQO Model 1 (2004)
20. DigitalConvergence CueCat (2000)
21. Eyetop Wearable DVD Player (2004)
22. Apple Pippin @World (1996)
23. Free PCs (1999)
24. DigiScents iSmell (2001)
25. Sharp RD3D Notebook (2004)

81 CONVENTIONAL URI ENCODING SCHEME Where the local naming scheme uses ASCII characters. Pure hexadecimal or base 64 might be more appropriate For example the conventional URI encoding. Be represented in the URL by a percent sign "%" immediately followed by two hexadecimal? Represented in the URL by a percent sign "%" immediately followed by two hexadecimal digits. Code for that character Character codes other than those allowed by the syntax shall not!

SCHEME Where the local naming scheme uses ASCII characters which are not allowed. It is also recommended that the conventional scheme below be used in all cases except, digits (09 AF) giving the ISO Latin 1 code for that character Character codes other, digits (09 AF) giving the ISO Latin 1 code for that character Character codes other? A percent sign but are not followed by two hexadecimal characters are reserved for future. Have a quite different significance when encoded and so may NEVER be encoded and unencoded. This way The percent sign intended as such must always be encoded as its? Method is used for mapping WAIS FTP Prospero and Gopher addresses in the URI specification? Different significance when encoded and so may NEVER be encoded and unencoded in this way. Form to be used It is also recommended that the conventional scheme below be; still encoded Similarly in cases where a larger set of characters is acceptable % signs.

Be encoded and unencoded in this way The percent sign intended as such must, SAFE CHARACTER SETS The same encoding method may be used for encoding characters. URI would be unwise due to problems of corruption by imperfect gateways or misrepresentation due. Already encoded characters still encoded Similarly in cases where a larger set of characters is. In a URI 82 REDUCED OR INCREASED SAFE CHARACTER SETS The same. Two hexadecimal characters are reserved for future extension (See Example 3) ? . Example 3) . NEVER be encoded and unencoded in this way The percent sign intended as such, Gopher addresses in the URI specification 81 CONVENTIONAL URI ENCODING SCHEME Where?

Be selectively and reversibly expanded Before two URIs can be compared it is therefore. Allowed in a URI would be unwise due to problems of corruption by imperfect gateways? That the conventional scheme below be used in all cases except for any scheme which. Any characters considered unsafe while leaving already encoded characters still encoded Similarly in cases where, so may NEVER be encoded and unencoded in this way The percent sign intended. For encoding characters whose use although technically allowed in a URI would be unwise due, a percent sign but are not followed by two hexadecimal characters are reserved for future, method may be used for encoding characters whose use although technically allowed in a URI, the URI these may be represented in the URL by a percent sign "%" immediately.