Recently MightyQ noticed some chitika-like ads being delivered by adsense. Although adsense has tested various rich media ad types in the past, I have never seen interactive “gadget ads” like these on adsense before.

google gadget ad

These advertisements are being delivered from which redirects to the typical google home page:

<iframe scrolling=”no” frameborder=”0″ src=”…

Google seems to like the “gadget” nomenclature:


I am assuming that the ad itself was designed by Echo3 has a long history of releasing cool google gadgets. It is no surprise that they are being used to generate these gadget ads. The gadgets are driven by XML:


For pointing out their coolness, I am going to hotlink to the spinner they use. Just using that, everybody will think that some cool gadget is loading, right? ;) Wwwwwwwweeeeeee….

Google gadget ads have the same problems that all gadgets, everywhere have. They are difficult to get to work on every browser system on every OS in every situation. I had to refresh this one a couple of times in firefox 2 OS X to get it unstuck. Here it is in eternal loading…

google gadget ad loading

I can not imagine the pain of trying to code and debug this type of complex javascript. Here is firebug showing the coding structure. iFrame within iFrame, anyone?

gadget ads iframe within iframe

For rich media ads, these are very tasteful and painless. I do not have any idea how the publisher is compensated for these ads. If somebody clicks and interacts with the ad but never navigates to the sponsor page, is that enough for the publisher to get paid? Does the visitor actually have to visit the sponsoring page or compete a transaction to trigger the adsense payment?

Google has been pushing google gadgets for igoogle, for for any webpage, and for the desktop. The extension of the gadget format into adsense has started.

Technorati Tags: , , , ,

If Digg is a young teenager, Slashdot is its parent.  Slashdot is now developing “Firehose” to keep up with Digg’s success.

The story of how Slashdot inspired Digg is well known.  Now, digg has surpassed slashdot, and slashdot traffic is actually slipping.

Now, the old fogey slashdot has announced a new (dare I say, Web 2.0) youthful, digg-like voting system–Firehose.  If you are a paid subscriber to Slashdot, go login and check it out. 

( Leave a comment to this post and you will be eligible for a slashdot subscription too. )

Firehose in action…

Here is slashdot’s description of what Firehose is…

The Slashdot Firehose is a collaborative system designed to allow users to assist our editors in the story selection process. Try tagging and voting on the entries below, and by using the ‘feedback’ menu by each entry. The hose can contain submissions, RSS Feeds, bookmarks, journal entries and Slashdot stories. Please send your feedback to but be forgiving of beta code!

Here is a break down of the various components:


Sliding this filter toward the red isolates the more popular, more voted articles.  In contrast, sliding the filter toward the darker colors increases the noise.  This compares to Slashdot’s current ability for users to view comments at a certain moderation level or higher.

Control Bar:

  • a — Play or Pause the Updates
  • b — Sort by Popularity or Time
  • c — Sort by Ascending or Descending
  • d — Toggle Abbreviated or Full


The thumb up and thumb down allows users to vote on an article.  Once a user has voted, the icons dynamically change to show a user’s vote.  I believe the color highlight on the left side is a measure of an article’s popularity.  These colors likely correspond to the colors in the slidefilter.

Once an article is accepted for front page submission the title bar turns from gray to the traditional slashdot #004F50 green.

Different Views:

I showed an example of the expanded view in the examples above.  Here is an example of the compressed view. 

This view will likely increase the ”catchy title” popularity effect that already weakens Digg’s effectiveness.


What was probably the most surprising to me is that the new slashdot layout uses yahoo’s ajax developer toolset.  The yahoo references can be found throughout the source code:

<div id=”firehose” class=”aduserbox”><script type=”text/javascript”>
  YAHOO.slashdot.App = function()


Display Bugs:

True to the beta tag (and to slashdot tradition), the new layout is not yet IE7 friendly. 

More User Generated Content / Socialization:

Slashdot users are famous for generating content.  Their superior comment system has been the cornerstone of their success.  Early adoption of a blog-ish journal system has helped as well.  Slashdot also developed a primitive friend/foe system long before social networks became popular.

Slashdot seems to be continuing to build on this process.  Now journal entries can be automatically added to the firehose.  This will encourage people to post in their journal and thus generate more content for the slash lords.

Discussion2 is slashdot’s introduction of ”JavaScript/CSS” into its well known threaded/moderated comment system.


I think everybody saw this coming.  I have mixed feelings about it.  Do you remember the first time you parents did something to appear “cool” to your friends?  I can remember when slashdot users slamming javascript as a security weakness were the norm; now slashdot is sliding into AJAX.

The strength of slashdot IMHO has always been the comments of its expert users.  The stories were just an excuse to read the opinions of the real, non-journalistic experts. 

Will these changes promote more interesting stories and increase the interest?  Will the quicker pace scare off the hardcore experts that are powering the place?

As a slashdot fan and subscriber, I hope these changes make the system stronger and more successful.

If you have a slashdot account but do not have a subscription, maybe we can help.  If you leave an insightful or funny comment (and your slashdot ID), we’ll pick a couple of give away 1000 page view subscriptions.  Then you’ll be able to play with Firehose too!

AJAX pitfalls

October 10th, 2005

Some important considerations for web programmers using AJAX on their sites in this article.

What Google Reader Needs

October 8th, 2005

This is what I believe Google Reader needs…

1. Soon after importing my OPML into Google Reader, I realized that it needs some way to bulk mark feeds as read. Some days I do not want to read everything. I just want it clean.
2. When AJAX is thinking, it needs an hourglass. For all of the evils of microsoft, at least you know when the OS is busy processing. Nothing in AJAX.
3. When I click on a blog subscription, I want to see all the entries at once. Newspaper view. Headline view. Whatever you want to call it…every non-web aggregator has this.

I am fascinated by AJAX.

September 14th, 2005

I bet nobody can tell that I am fascinated by AJAX. I only post a half-a-dozen cool links about it per day… Once we get tech-recipes (and once I get my life) a little more stable, I’m going to blaze through these AJAX links like crazy. AjaxPatterns has a ton of great examples in a wiki format.