AI or artificial intelligence applications could be used to generate the search string to the search engines, this may help simple people get what they want in the internet, without having to rack their grey matter to improve their search results. The strength of a AI application depends on a human built database of knowledge with a capability to learn thru internet or by collaborative computing.
Then i have a small AI - DOS based program made by Greg Leedberg which works pretty well, it is called daisy, i taught it many things for over a year, now it comes up with interesting things, i have never heard about.
Idea - Oct-05, Posted in Ideas of delabs Blog, Revised again - 4 April 2008, Nature - Open Source
This section had a domain of its own in 2008 and the Tagline i conjured for this was
Engineering the Computing Device, Data and Delivery
Secure Search - Encrypted Search
When we search and get the results the keywords and results can be monitored and recorded at different points in the network.
In some cases : examples - a researcher working on a sensitive topic, an inventor gathering data for his next innovation, which he wishes to patent and make a living.
In the above instances, the user can become a victim of eStalking, which means servers, caching computers in the path and even routers can be tampered, for access to this data. When a competing firm or group gets the keywords and results, they will be ahead in getting their products or patents ahead of the original inventor.
The technology is similar to Enterprise Search, but Secure Search is a search that has all web content with a subscribed-authorized access, SSL and encrypted 'like' gui-keywords-results.
Researchers, Companies and Inventors can subscribe and keep ideas and study hidden to prying eEyes.
What happens when we cannot trust a Search Engine or Search Service. The Solution is collect and keep data organized in your own computer and Search the offline data.
Entering Login details thru Keyboard has been found to pose security
risks. I just got an idea which i will explain with an example. This is
much safer as it uses mouse clicks and no ASCII characters encrypted or
otherwise move on the SSL Page in TCP/IP, No keystrokes are generated since only a Mouse is used.
When the Secure Login page is visited by the User, He will see an image (png) with randomly generated Numbers (or Alphabets).
This is done using a Captcha like process.
the user in order to Login to his Account will click the Numbers (image
map - js onclick). The numbers can be scrolled, inc/dec (area on number
top/bot). He will set the User ID and Password with a series of clicks
(just like Combination lock.
When he is done he will
Press Login. The safest Login that can ever be achieved, no trace of
number anywhere. The only risk is posed by an Onlooker or a Webcamera,
Hence this can be used in closed Opaque kiosks only.
Random Captcha AlphaNumeric KeyBoard Layout Imagemap. The User and
Password field will be textboxes as usual. The User will click into
textbox, a key-layout appears on right (ajax). The user clicks the
alphabets and numbers on keyboard image and then he presses Login.
Here the password will appear as ****. And the keyboard imagemap layout is random size usable AlphaNumeric Single png Image.
Now many third part scripts like Stats, Ads, Videos, Gadgets and Ajax
elements are available for embedding in the template of a service or
community-network template page.
Average user cannot tackle code snippets and inadvertently introduce errors, while adding the code to his template html source.
important is that this snippets will change syntax as the webapps
evolve and the service api changes or even new web standards.
may be best to make this snippet invisible to users and available to
programmers if needed. Even the code coming on the browser client html
makes the page cluttered and there is a bandwidth element too.
A new HTML tag may help clean the clutter and leave the snippet at the server. It is similar to embedding images ..
xgz tag is for gz compressed xhtml code analogous to "img src" for
embedding images. The gz file has CSS-JS and XHTML code that is current
to that service and account.
The Browser decompresses
the gz and renders the page and effects as designed. The Browser View
source just shows the xgz tag for every code-embed. Expanding the
element gives more details. As this code is at host, it cannot be
modified or tampered by any user.
The best part of this
is, some code gz can be password protected so the code wont unzip or
render for user browsers that are not logged in. The password
protection of code gz can also protect the code to some extent. Which
may be the DHTML or AJAX IP of creative web designers.