Like on-page linked text analysis in general, identifying grey areas like hidden links (and text) should be an important and thoroughly considered step. You will want to research hidden links: (!) When you need to diagnose a recently hacked site; (!) When you need to test a web design (some hidden text may be totally innocent and only appear illegal); (!) When you need to identify the reason of the possible penalty; (!) When you want to resd possibly rearch your competitors’ grey tactics (and possibly report them); (!) If want to find out if your hidden links can be found manually by search engineers or competitors; (!) Etc.

Excerpt from: 
3 Simple Tools to Find Hidden Links (and Text)

With SMX West this week, I was going to hold off on the 2nd part of my hands-on SEO Audit series.  Then I remembered that heck – I’m not going to be there so I bet enough other people in our industry won’t either that it will be a great way to give all the non-attendees a leg-up on the competition, as they all run around the conference hoping to grab actionable information.  If you haven’t read part 1 in this series, I encourage you to go read that first since it sets the foundation for what follows here.  Go ahead – I’ll wait. Okay did you actually think I was going to wait for you to read that before I continued writing?  I sure hope not.  Because if you did, you seriously need to work on your gullibility.  If you’re too gullible, you’re going to get toasted in this industry.  Also while you’re at it, another other great resource I highly recommend when it comes time to writing up an SEO audit is Glen Gabe’s  “ SEO Techinical Audits “. Don’t Give Away The Farm In this part of the series, I’d like to focus more on some of the things that should and shouldn’t go into an SEO audit.  This seems to be one of  the biggest areas of confusion for consultants just starting out.  And as I mentioned in part 1: a site Audit isn’t supposed to be an advanced course in SEO.  It’s to point out problems and recommend methods of solution.

Read the rest here:
Anatomy of a Hands-on SEO Audit – Part 2

See? Here’s one of the many reasons why the Nexus One phone could become a better Google-centric smartphone than the iPhone

Here is the original: 
Google Adds Personalized Suggestions to Nexus One Maps

Ever since Google Chrome blog announced the launch of Google Chrome Extensions , people have never stopped talking when this move is going to kill FireFox.

View original here:
FireFox Addons vs Google Chrome Extensions

One of the most cost-effective ways to drive traffic to your Web site is to optimize it for search engines….

Here is the original: 
Optimize to Get the Most from Search Engines

Treat Yahoo as both a directory AND a search engine.

Continued here: 
Tips for Getting Your Website Listed on Yahoo

We’ve recently made some changes to help improve the communication between plugin authors and plugin users about the changes that are made between versions.
We feel that all software should have a changelog that details, at a high level, what changes have been made in each version so that the user can make an informed decision about when to upgrade and how much testing they should do with their site.
In order to make this an easy and open communication channel we have added support for a Changelog section in the plugins readme.txt file.  This changelog information is then displayed as a separate tab in the plugin directory and also in the back end of your WordPress blog when you view the details on a new version of a plugin.
The new section is formatted as follows:

== Changelog ==

= 1.0 =
* A change since the previous version.
* Another change.

= 0.5 =
* List versions from most recent at top to oldest at bottom.

We would also like to recommend that you also provide meaningful log messages when you commit changes to the subversion repository for your plugin so that people who want to dig further into your changes can see why things are changing (At the moment is seems a large number of plugin authors leave this field blank which isn’t very helpful).