UXesSEO

When you choose to read the tweets of your friends in Google Reader, notice that you will only see the first 20 every time Google Reader checks your Twitter account. If there are more than 20 tweets between two connexions of Google, you miss them !

It is well known that this occurs if you pass through another service such as freemyfeed, feedburner or yahoo_pipes. But it actually also occurs if you directly use the Twitter option to import you friends_timeline.

I noticed it because of the new authentication process of Twitter. Because of that, I found no way to keep following my Twitter account with efficiency that adding each RSS of all the people I follow one by one into Google Reader !! No other way to avoid the 20 tweets limit (or extended 50 adding ?n=50) AND still keep updated on real-time.

Well, I notice that I receive much more tweets now that I added each RSS feed manually than when I added the Twitter friends_feed before their new authentication process! This means Google Reader and the Twitter friends_timeline actually doesn't combine. Be aware !

Did you ever wonder what is that small search field below a few search results in Google ?

1. user attention is catched by a layout break-down : a form field in the middle of the result list
2. a form field immediately calls for action, which is especially interesting for e-commerce
   
3. a (performant) search feature is the quickest way to find a product in a e-store; this shortcut to the product also attracts the potential customer

According to Google itself (Google blog announcement on March 08), it is based on the high match potential rate of the result compared to the query, and to the kind of website targeted (width, page rank, etc).

Now the question is : why does this search field not always appear for the same query and same site target? For instance, a query on 'bebo' (the social networking), not always shows that search field (depending on the computer on which I tested). For the same query, it sometimes shows, sometimes not. Any idea of the user settings that could be involved in this behaviour?

Anyway, this feature that already exists from nearly two years now in Google UK, only shows up rarely in Google BE. Did it lack of the expected success in UK ? I found no update about that on the Google blog, nor others...