Harsh J

Memoirs of a QWERTY Keyboard

Archive for January, 2011

The whole deal with auto-complete and the alleged censorship by Google

one comment

TorrentFreak has run an article claiming that Google has begun ‘censoring’ the auto-complete and instant responses of its search bar for terms that have anything to do with popular sources of downloads of copyrighted content, like ‘torrent’, various download sites, etc.

What they don’t realize is that auto-complete and instant result generation for keywords that involve such terms is plainly useless (as are many others, which must be filtered away to save some load too). It isn’t censorship, but an optimization.

The search still returns results when queried in the proper Return-key manner. The only thing blocked away is to see highest ranking terms in auto-complete, which is worthless cause there are so many new releases made in those streams that it makes no sense to process, rank and display them in an order via auto-complete, or stream cached results while the user looks for something.

Google Instant is a good tool if it can predict what you’re going to search for, and is a great tool if it knows when it should do so. Which it does.

TorrentFreak just isn’t what it used to be. I dislike a couple of its authors. It isn’t worth linking back to their article, which can be searched on their site — unless they’ve ‘censored‘ it away. Meh.

Written by Harsh

January 27th, 2011 at 11:25 pm

Posted in Personal

Tagged with , ,

Interesting Articles for January 27th

leave a comment

googlereader (feed #7)
googlereader (feed #7)
googlereader (feed #7)
googlereader (feed #7)
googlereader (feed #7)
googlereader (feed #7)
googlereader (feed #7)
googlereader (feed #7)
googlereader (feed #7)
googlereader (feed #7)
googlereader (feed #7)
googlereader (feed #7)
googlereader (feed #7)
googlereader (feed #7)
Shared gambit.
googlereader (feed #7)
googlereader (feed #7)
Shared iolang.
googlereader (feed #7)
Shared Na.
googlereader (feed #7)
googlereader (feed #7)
googlereader (feed #7)
Shared bashcrippled.
googlereader (feed #7)
Shared Spider-LOL.
googlereader (feed #7)
googlereader (feed #7)
googlereader (feed #7)
googlereader (feed #7)
googlereader (feed #7)
googlereader (feed #7)
Shared nfcd-svn.
googlereader (feed #7)
Shared nfcutils.
googlereader (feed #7)

Written by Harsh

January 27th, 2011 at 6:30 pm

Posted in Asides

Interesting Articles for January 20th

leave a comment

googlereader (feed #7)
googlereader (feed #7)
googlereader (feed #7)
googlereader (feed #7)
googlereader (feed #7)
googlereader (feed #7)
googlereader (feed #7)
googlereader (feed #7)
googlereader (feed #7)
Shared 3D.
googlereader (feed #7)
googlereader (feed #7)
googlereader (feed #7)
googlereader (feed #7)
Shared libkface-svn.
googlereader (feed #7)
Shared fizsh.
googlereader (feed #7)
googlereader (feed #7)
googlereader (feed #7)
googlereader (feed #7)
googlereader (feed #7)
googlereader (feed #7)
googlereader (feed #7)
googlereader (feed #7)
googlereader (feed #7)
googlereader (feed #7)

Written by Harsh

January 20th, 2011 at 6:30 pm

Posted in Asides

A simple email search trick

leave a comment

Oh boy, I love standards.

When I was wondering how do I search for mails sent by me, where I’m also the thread originator, I looked at what GMail had to offer as it search fields and other such advanced options. In the end my search was simply:

in:sent from:me term -Re

Now am wondering why it didn’t strike me immediately to look for the “Re” keyword that makes a mail a reply de-facto. Of course, there’s a much more neater, more RFC-5322 compliant way of searching such mails, but I’m unsure if GMail supports such querying.

Written by Harsh

January 17th, 2011 at 11:03 pm

Posted in Computing Issues,Fun,Software

Tagged with , ,

Writing Android Applications

leave a comment

Cause “app” is a slang I don’t seem to bear anymore. (What blows me over is a ‘you’ substitute in emails, though.)

Android

Android



I finally got around writing out simple applications for the Android mobile platform. For someone who comes from a background of event driven classes (a la Trolltech Qt), this RCP-styled programming in Android looks real bad. I wish we had simple @Override-driven eventing than defining new inline/external classes for every simple event that needs handling. Ah well, different worlds, different paradigms. I could actually go on for hours describing how Android could benefit with a Qt-style event driven programming model, but I have other things to do ;)

Written by Harsh

January 17th, 2011 at 1:08 am