When JS-Kit first announced their Echo platform, declaring the death of comments, many thought it to be hyperbole. But as we have seen with a metamorphosis of the way people react to content around the Web, sharing it downstream with followers on Facebook, Twitter, Google Buzz and many other outposts, blog comments no longer hold the lofty role they once did, and it has become increasingly important to discover reactions - wherever they are. Since that announcement almost a year ago, JS-Kit rebranded as Echo, and has been promoting their premium reaction platform to more than just blogs - but old media titans. Today, the company announced a wide array of publishers who have chosen Echo to capture their real-time reaction stream.

Included in the morning's announcement were names such as The Washington Post, Newsweek, Time, Forbes, and Sports Illustrated. In a quick e-mail announcement the company said they were "extremely excited and gratified to be working with these high profile and influential brands, helping each of them create real-time conversations on their sites."

In parallel, the company also relaunched its Web site, now at http://aboutecho.com/.

Unlike its Web 2.0 cousin, Disqus, Echo is not focused on offering a free comment platform for bloggers, and has been creating a robust system that starts at $99 a year. For its part, Disqus announced the acquisition of Harvard Business Review as a customer today. Also, recently, Intense Debate, the quietest of the three offerings, was selected by TechCrunch as the tech blog's comments engine.

Echo's announcement can also be found on their Web site: Echo partners with Washington Post, Time, Forbes and others

BackType, the most robust and feature-rich comments tracker on the Web, has expanded its services over the last few months to include a number of new items, including the launch of BackTweets, to find shared links on the microblogging service, a TweetCount plugin to highlight the number of times items have been retweeted, and a BackType Connect plugin for WordPress to show related conversations around the Web attached to your blog. The company's API is also used by popular services including Bit.ly and Disqus, who leverage the service to find external links and related tweets. Today, these downstream partners can expect updates to happen in near real-time, thanks to BackType's jumping on the PubSubHubbub bandwagon, in a partnership with Superfeedr, providing practically instantaneous updates downstream.

Superfeedr, one of the more aggressive services promoting PubSubHubbub, is providing the legwork for BackType, acting as a hub, pushing updates automatically as they are discovered. In today's post, BackType says the move reduces load on publishers by sending feed updates to all potential subscribers, without requiring multiple polls, and avoiding the arbitrary nature of clients' periodic requests.

If you subscribe to BackType to follow individuals' comments, or if you simply use Disqus or BackType connect on your blog, the move will ensure updates reach your content faster than they ever have before. In a Web world that is getting increasingly real-time, the name PubSubHubbub keeps popping up, and BackType is staying on the leading edge of innovation.

As comments on the Web become fragmented, conversations that occur on downstream aggregation sites often are taking place in a silo, disjointed from parallel discussions on the originating Web site. Over the last two years, many people have found this evolution controversial, hoping to unify the conversations in a central location - and some services, including JS-Kit's Echo and Disqus, have taken the first step by pulling external discussions to the source. But a brand new proposal, authored by John Panzer of Blogger, called the Salmon Protocol, is looking to take advantage of Pubsubhubbub to unify the conversations in all places, both upstream and downstream. And yes... the name of Salmon comes because those fish manage to swim upstream, just like the comments.



An Initial Presentation on the Salmon Protocol
As discussed in Friday's panel at Blog World Expo on technology and the real-time Web, Pubsubhubbub essentially works as a middle-man conduit, taking information from a data's source passing along changed data to downstream destination sites. The proposed Salmon Protocol would similarly watch both source and destination sites for comments, and upon discovering new comments, it would send the new comments to the site which is lacking the full conversation. If multiple downstream destinations are designated, the Salmon Protocol will also populate these multiple sites.

In conjunction with Pubsubhubbub, the Salmon Protocol leverages the newest iteration of webfinger, enabling publishers to receive comments and verify subscribers - as a form of true identity recognition, similar to how both Disqus and JS-Kit have you register for individual accounts with either service. An additional side benefit to leveraging Webfinger would be to dramatically reduce the potential for spam, assuming each individual has a unique ID.

The debate over fractured conversations has risen and fallen over the last two years. In September, I essentially said I was done listening to people complain about the issue after hearing complaints regarding Google SideWiki - as I believe people will want to have conversations where they are comfortable, and that they shouldn't be forced to come back to a single source. This is a point I have been hammering since the first major flareup back in April of 2008. (See: Should Fractured Feed Reader Comments Raise Blog Owners' Ire?)

Many people believe that transporting comments from one site to another and making the conversations one could cause confusion, or even make potential commenters uncomfortable. With this in mind, John has suggested that users "be made aware of the publishing scope of the comments they leave," adding "For some aggregators, this may be implied (all data is public), for others a warning or a checkbox may be necessary." (See: Salmon Protocol (Draft) Protocol Summary)



A Test Comment from the Aggregator Via Salmon


The Resulting Comment Back On the Blog Via Salmon
There is a test playground for the Salmon Protocol, and I can verify that it already works. If you want to test it, one option is to take a testbed Blogger account and point the Salmon Protocol your way. It occurs automatically, and comments that happen on the downstream aggregator will make it back to the blog immediately, thanks to Pubsubhubbub. Now, the quest becomes to turn this brand-new protocol into a new standard - one that could pose a serious challenge to services like JS-Kit Echo and Disqus, even including threaded replies. If done well, the long debate over unified conversations could soon be over.

Learn more at: http://www.salmon-protocol.org/.

The world of comments on blogs has changed quite a lot just in the past few years. Once the central discussion point for all activity around posts, comments have become distributed, floating to a myriad of social networks and RSS feed readers, while still others are simply retweeting the items they like. The changes were enough to see one comment provider, JS-Kit, say that comments were "dead". Meanwhile, amidst the noise, Disqus has rolled out version 3 of its product today, providing a new, smoother look and feel, and most-importantly for today's Web, real-time updating and greatly improved "reactions" that pull in activity from around the Internet.


Disqus Has Now Split Into Two With Profiles and Comments
In parallel with the company's revamp of its comments engine, Disqus has also added a separate product, called your Profile, which lets users add or delete comments, without impacting the original site, and also presents yet another place to add your third party services, so you can tie all your activities on a post through your profile. Other benefits include a personal URL, such as http://www.disqus.com/louismg for me.


My New Disqus Profile


The New Look of Disqus Comments
Disqus's improvements are coming none too soon. With a great deal of comments taking place elsewhere, as I mentioned with my recent post on Google Reader, and have seen with various sites trying out JS-Kit's Echo platform, the world of comments on the blog has to adapt. I just wonder how the real-time aspect of comments can keep people on the site instead of venturing somewhere else, where they may have established a community. I am looking forward to seeing Disqus 3 play a more connected role to the social ecosystem.

Bloggers who are tied into social media sites have long used FeedBurner's FeedFlare functionality to help promote their blog posts, from pushing visitors to Digg or Stumble posts, add them to Delicious, or e-mail them to friends. But increasingly, information from external social networks is being fed back to the blog itself - from the number of retweets a post may have received to the number of Google Reader users who shared the item, for example. A new custom feedflare, designed by Kevin Fox, the lead designer of FriendFeed, and the artist behind popular sites such as GMail and Google Reader, is now available to display the likes and comments your post might have gotten on FriendFeed. It's already running on this site, and can be seen on his RSS feed as well.


FriendFeed Activity Displayed on My Site
The FeedFlare can be displayed on your site, on your RSS feed, or both - and clicking on the comments and likes statistics takes you to where your blog post is shared on FriendFeed, bridging visitors of your site to the conversation there.

Setting up the FeedFlare for FriendFeed likes and comments is not a one-click process, so if you are interested, here's how you do it:

1. Download this compressed .zip file. It contains the three documents you need, and an "About" file. Unzip the file and you will see a folder titled "friendfeedflare".
2. Open the file "flare.php". Next to where it says USERNAME, replace "notlouisgray" with your FriendFeed user name.
3. Open the file "friendflare.xml" and replace the pathname of "http://www.yourdomain.com/directory/flare.php" with where you will host the flare.php file. For example, I host mine at http://www.louisgray.com/feed/flare.php.
4. Upload the files "flare.php", "friendflare.xml" and "friendfeed.php" to a directory on your site which matches the path you provided in step 3.
5. Log in to your FeedBurner account, and go to the "FeedFlare" section in the "Optimize" tab.
6. At the bottom of the page, where you have the option to add a "Personal FeedFlare", paste in the URL of your XML file. (e.g. http://www.louisgray.com/feed/friendflare.xml)
7. Hit "Add New Flare" and then "Save".

The FeedFlare Displayed In FeedBurner
At this point, the likes and comment counts on your items will be displayed on your blog or RSS feed. They will continue to accrue until you have 30 newer items in your blog feed.

A year or so ago, the blogosphere lit up around how social sites were stealing the conversation away from blogs, and operating in silos. With tools like this, and Disqus and BackType's integration of FriendFeed comments, the disparate conversations are becoming ever more unified.

If you like this FeedFlare, be sure to check out Kevin Fox's FriendFeed here, or his personal blog at fury.com. And if you get it up and running, it'd be great to see it on your site, so post your blog URL in the comments.

As social networking and social media sites increasingly become as much about companies and brands as they are about people, you are seeing names like Zappos and JetBlue tweeting alongside you, and Comcast answering complaints. Companies might be making comments on FriendFeed and asking you to join their fan page on Facebook. Many of you, possibly tasked with maintaining the social media presence for your company, might be maintaining multiple accounts on practically every network, and trying to keep your personalities in check, lest you make the mistake of getting the two mixed up. For the last four months, I've been doing the same thing. Here's how.

Put Your Work Life In One Browser, and You In Another

Everybody has multiple browsers these days. Whether you prefer Safari, Internet Explorer, Firefox, Chrome, or something else, you probably have a second one which you use less. Rather than ask you to login and log out over and over, set up one of your browsers with bookmarks to all your work activity and the social media sites with that account, and keep your preferred browser all yours.

For my work account, I use Firefox, and for me, I use Safari.

When I open Firefox, the browser opens five distinct tabs:

• Gmail
• Google Reader
• Twitter Search
• Twitter
• FriendFeed

The GMail account tracks new subscribers and DMs. Google Reader populates the link blog. Twitter search watches what is being said online, and Twitter and FriendFeed let the company participate.

Running the browsers in parallel lets me do the work I need to in both, without suffering from multiple personality disorder.

Make A Second Login, Preferences for TweetDeck

TweetDeck, in my opinion, is still the best way to track groups and saved searches in Twitter. I set up TweetDeck so if I am logged in as me, the application has the standard black look and feel. But when I am logged in with the company ID, TweetDeck is in the company colors of blue and orange. Yes, the combination is somewhat garish, but it serves as a reminder to me that I'm logged in for work, so I won't screw up.


Logged Into TweetDeck as the Company

Logged Into TweetDeck as Me
Beyond the colors, you should leverage TweetDeck's saved search functionality to track your company and product mentions, as well as that of competitors.

Create a Second Disqus Account for Commenting

When commenting on blogs around the Web, as yourself, or for the company, it makes sense to use best practices and identify who you are. But you don't necessarily want to track your work comments to your personal ID. I recommend getting a second Disqus account that ties back to your work e-mail address, and have that registered in the "work" browser. When I make comments on sites as work, it says my first and last name, and then, in parentheses, the company name.

Always Work Methodically When Acting on Behalf of the Company

Tweeting or commenting or blogging or bookmarking as a brand is more risky than when you do it on your own. As with all things on the Web, you should consider how they could be interpreted downstream. But when you are doing something on behalf of a corporate entity that represents products, people, history and finance, you should take an extra breath before acting, and pay extra attention to every word, character or nuance.

Be Replaceable

If you do your job well, it should be easy for you to pass off the reins of the social media strategy at your company to somebody else with very little impact. If you make the company's social media presence all about you, it will follow you where you go next, and could negatively damage the company you are leaving, and distract from the company where you are going. See that you can work on behalf of the company without it being all about you. Try to offer personality without it necessarily being your distinct personality.

You'll note I don't often talk about work here on the blog. It was a conscious decision I made when starting the site at the beginning of 2006. It's not a secret where I work (check my LinkedIn profile) but it's not about where I work. It's all part of keeping things separate. Are you running the social media activity for your company, or looking to get started? I would be interested in the tips you may have as well.

While venture capital is said to be very expensive these days, hard to obtain, and with questionable potential returns given a closed market for public offerings and multiples for mergers and acquisitions, companies on the periphery of blogging appear to still be hot. We saw Auttomatic acquire Intense Debate late last year. You also remember strong funding rounds for my personal favorites, Lijit and Disqus, who are adding strong search and commenting functionality to sites like mine. Now, you can add Outbrain to the list, following this morning's announcement the company scored a $12 million round to expand its blog rating and recommendation platform.

Now, before you cry foul and ask where the money is in such a little widget, as is tempting, you can read between the lines in today's release to see that Outbrain has bigger plans - ones they no doubt shared with their VC partners, and not necessarily with me.

Outbrain is talking less about a widget, and more about finding great content across the Web. As one VC partner said, "Finding great content is getting both more difficult and more important... Outbrain's personalized recommended links offer great value to readers by combining their collective wisdom..."

If you think about it, Lijit and Outbrain are solving similar issues, from different angles. Lijit scours your personal blog and your social network of approved sites to find content you are searching for. Outbrain analyzes your individual posts, your previous blog entries and other blogs in their network to provide recommendations of what to read next. Both are useful, and both are getting traction. And it's good to see that good ideas are going to be rewarded, even when times are more difficult.

By Mike Fruchter of MichaelFruchter.com (Twitter/FriendFeed)

Our Doings is a simple and unique photo sharing service. While it may not have the lengthy feature set and large community of a Flickr or Picasa, that's okay, as it's primarily a much smaller operation, and the feature set built into the service leaves it standing in a league of its own, in my opinion.

Getting started with Our Doings takes less then five minutes. Once you register for an account, you have the option of creating a custom URL for your photos, such as the one I created for testing purposes, or you can let the system automatically generate one for you. Both URLs can be viewed by the public. The key difference is the indexing option, which you can select on or off. If you select "no indexing", search engines are advised not to index your URL.


Uploading is made easy. Give it everything you can throw at it!


The service gives you a multitude of ways to send photos into the system.

• e-mail to publish
  
• Web Publishing Wizard lets you upload straight from Windows XP or Vista
• Picasa photo albums button
• Web form to upload individual photos
• Ability to upload a zip archive of up to 100MB

Why do I like this service so much? Automatic organization of your photos by date!

While the service has plenty of nook and crannies, this is by far the best feature yet. There is not one service out there that I could find that automatically organizes and sorts your photos by date. This is not a feature currently offered by any of the other major photo sharing services currently on the market.


For someone like me, who is not meticulous with organizing my photos, this feature is a godsend. I have dozens of folders on my desktop with random images taken at any given time. The images from a specific occasion in time, such as a birthday party or wedding are easy to organize. It's simply a matter of creating a photo album titled "someones wedding" and dumping all the correlating images into that album. The other hundreds of photos are taken on random occasions, random days and so forth. Most recently, with the birth of my daughter, my wife or I will grab the camera at any given time to capture that perfect Kodak moment of our daughter doing something that warrants a digital snap. It's these Kodak moments that I specifically would like to know the day that it had happened and reflected on the photo album. Now with this service, I can begin to upload the hundreds of images that I have stored on my desktop, and have them chronologically organized by the date that they were taken. This core feature will keep me using the service hands down.

It gets better. Site integration with your favorite Web 2.0 services:


Ourdoings.com offers integration with a lot of the popular Web 2.0 services, such as Disqus. Oh, and did you see FriendFeed is on that list too? They implemented SUP, which means if you configure it for FriendFeed, your images will appear on the site in real time. I configured mine to import my images into FriendFeed, you can see my feed here. It took no longer than 15 seconds for the images to import onto my feed. Without the implementation of SUP, you would be waiting anywhere from 30 minutes to an hour for photos from other photo sharing services to import into FriendFeed. You could always uses the manual refresh link, but that defeats the whole purpose.

You also get a Media RSS URL for all of your photo albums:

Media RSS is a special type of RSS feed that contains rich media assets like video, audio and imagery. Many media sharing and news sites publish content using Media RSS. This is an added bonus, and one feature I'm sure the bigger competitors in the space do not currently offer. Do you have a wireless photo frame? Without getting too technical, it solves the nagging problem of photo orientation.This explains it in more depth. This is something I will use for my wireless photo frame that I have been eyeing for purchase for some time now.

In closing:
I'm thoroughly impressed with this service. It's the simplicity of it, along with the automatic organization of my photos by date, that has sold me. I don't need all the fancy bells and whistles that some of the other bigger name services offer. I have a Picasa account that suits me just fine as a backup. Will this be a replacement for Picasa? It's strongly looking like it. I have not made the switch yet, as I only have tested the service out for less than an hour or so. I would like to see some photo editing features such as cropping and red eye reduction added, but in the meantime this service is something worth looking into.

Read more by Mike Fruchter at MichaelFruchter.com.

Who really owned the comments... the original poster or the aggregation site that "stole them away" was one of the biggest small-time blog wars on the Web in 2008. Whether bloggers were complaining about seeing comments and conversation moved from their blog and instead taking place on FriendFeed, Socialmedian or Shyftr, or debating whether they could trust comments in the cloud, it became clear that the only consensus was that there would be no consensus. You either embraced the new tools, or you yelled loudly against them. Today, an interesting tool via Disqus has let bloggers effectively synchronize comments between their blogs and the popular FriendFeed service, meaning people can comment in either place, and see it end up as part of the conversation - wherever it is.

And guess what? We've already implemented it on this blog for louisgray.com.


Set up your API key on both services...

As the Disqus blog points out, an enterprising Disqus community member, Carter Rabasa, put together a quick application on Google's App Engine, called FF2Disqus. By entering your API key for both Disqus and FriendFeed, assuming you use both services, the tool will check your blog posts on FriendFeed and pull in FriendFeed comments to your site, or send Disqus comments to FriendFeed.


The result spits out the copied over comments...
There's no installation process, no scripting and no code. Just run it once and you're good to go.

You can choose to make the connection unidirectional, from either FriendFeed to your blog, or the other way, or to have full synchronization. I enabled it to copy over FriendFeed comments to my site, effectively replacing the Yahoo! Pipes solution I'd asked Pat Hawks to create last June.

The result is pretty straight forward. If there is a comment on FriendFeed, it is displayed by Disqus on my site, in the order it was posted, and the author's ID links to their FriendFeed user profile. Now, what the solution doesn't do is crawl FriendFeed and find all comments on all reshares or tweets of your blog. It just gets the one main entry, which I think is good enough. It also is bound to have some disjointed entries as conversations are smashed together, but it should be a good experiment to see how the two could merge.

If you're a FriendFeed user and a Disqus-enabled blogger, you should really check out FF2Disqus at https://ff2disqus.appspot.com/.

By Mike Fruchter of MichaelFruchter.com (Twitter/FriendFeed)

Lifestreaming was a big thing for social media in 2008, and surely will be even bigger in 2009. Thanks to sites like FriendFeed, Lifestream.fm and others, we can easily aggregate our social activities into one central place. As with all of these services, we must log into the service's Web site to see and stream our activity. That is fine for the majority of us, but what about self-hosted lifestreaming? Solutions include Sweetcron and a ton of advanced PHP scripts that can be found at the lifestreamblog.

The problem, however, is that a lot of these scripts are complicated, and if you do not have basic PHP coding skills, you are pretty much out of luck. This is where Kakuteru comes into play. Kakuteru is an open source lifestreaming application built on Ruby On Rails, with the key difference being that it uses your your FriendFeed.com stream as the core lifestream backend. It falls into the self-hosted lifestreaming category because you have the ability to mask your Kakuteru service URL to a domain name, as I did for testing purposes. It's completely customizable as well.


Wait a second. This looks a lot like Sweetcron!

Dominiek ter Heide, the creator of Kakuteru, got his inspiration and design from sweetcron, but that's where the similarities end. Sweetcron is completely self hosted, being you must install and upload the files to your Web server. Sweetcron also runs on PHP, and gives you the ability to import any type of activity stream via an RSS feed. Lastly, Sweetcron stores all of your content on your server.

Kakuteru, on the other hand, is Web-based, and only aggregates your FriendFeed activity for your lifestream backend. In other words, you need a FriendFeed account for this to work properly. You have the ability to strictly post HTML content, if you decided not to aggregate any of your FriendFeed services. You also have the ability to toggle on and off the FriendFeed services you want to lifestream, so if you wanted your Kakuteru lifestream to strictly display Google Reader shares and Youtube videos, you would be able to do so.

Okay, so what's so special about this?

• The ability to import your FriendFeed stream to a custom domain name with full customization
• Semantic features such as autotagging of tweets and articles using Zemanta.com
• Related articles & tweets are shown for each entry.
• Blog posts can be written and posted using textile, markdown or HTML.

Kakuteru uses Disqus.com to support comments on articles & stream updates, and published articles have the ability to display Tweet-this, Digg and also Addthis.com, if you choose to enable these social components. "Me on other sites" are automatically gathered from your Friendfeed account.

Oh, and did I mention it's open source?

Out of the box:


It's very vanilla out of the box, as you can see in the screenshot above, or by going to mikefruchter.com. Give your stream a custom feel and fit by customizing your CSS, headers and about page. Select the services you want to display, by default it will stream all of your FriendFeed services. Be sure to add your domain name and follow the instructions for pointing your dns to your Kakuteru account.



Extra integration:

Kakuteru allows you to seeminglessly incorporate Web 2.0 features and functions, such as your own custom Disqus forum, Feedburner feed, Dopplr schedule and social bookmarking services. No editing of code is necessary, it's a simple plug and play process.


Activity stats:

One of the features I particularly like is the activity stats. Kakuteru gives you two sets of stats. Daily activity, services used and hoURLy activity. Who doesn't love colorful bar graphs?

Final verdict:

I'm particularly not too big on self-hosted lifestreams, as I prefer the real deal with the community interaction behind it, i.e. FriendFeed. If I was looking for a custom solution, I would use this, but it's currently limited to only your FriendFeed data. If you are not on FriendFeed, this application will be of little use to you other than creating a bare-bones HTML blog post. I do like that it is semantically-driven and offers a ton of bells and whistles, and like Sweetcron, it's open source. This application showcases a lot of what Sweetcron is currently lacking, the creator has put some thought and time into it and it's obvious by looking at the feature set. Since the creator of this app took his que from Sweetcron, I would like to see this application be able to save your lifestreaming data to your server. Offer that, and you have a real winner on your hands.

Kakuteru is currently in closed Beta, so be sure to register as a second round of invites will be going out soon.

Read more by Mike Fruchter at MichaelFruchter.com.

To most readers here, it's no secret I'm fairly active online. I try to keep up with the news by absorbing a strong amount of feeds in Google Reader, and then share the best of those with you on my shared links blog. I try to keep the blog consistently published with good insight, both from me and the rapidly-expanding team of contributors. I attempt to be visible and participate in a small array of social networks, from Facebook to Twitter to Friendfeed, Socialmedian and Strands. I try to answer e-mail as it comes in, and monitor or reply to comments. But I know I'm not doing a perfect job. If I only had more hours in the day, and made this my priority, here are some of the things I wish I would do better on the Web, and things I'll be paying more attention to as the calendar flips from 2008 to 2009:

1) Make More Comments on Original Blog Posts

Every day I come in contact with hundreds and hundreds of new stories. The vast majority of them I read in my RSS reader. I click through a small percentage, share a different percentage and e-mail others. I am also encountering many other new stories via FriendFeed and other social aggregators, exposing me to new ideas and news.

But while I already know I am not reading enough stories at their source, I'm certainly not participating and commenting enough. I need to make more time to do this in 2009.

2) Respond to More Comments on louisgray.com

Some days I do this well, and other days, not really well at all. A while ago, I talked about whether comments on blog posts were conversation, or just replies, and I find too often I lean toward the latter. Disqus makes it super-easy to blast through comments and respond via e-mail, so I should do a better job of being engaged with the best audience on the Web in 2009.

3) Be More Interactive On Twitter

There's no one right way to use Twitter, as we mentioned earlier today, but I'm pretty sure the way I use it isn't perfect. I signed up to Twitter in early 2008 after being, for me anyway, a longtime holdout. It's likely that more than half of my Twitter posts are simply announcing new blog posts here, and I could do a better job of listening and engaging than simply broadcasting in 2009.

4) Spend Less Time on a Few Sites, and More Time on Many Sites

Being visible and active on social networks that have similar capabilities, like FriendFeed, Socialmedian and Strands, is hard. It's no secret that there is a tendency to pick one or two places to build up a community and leave the others dry, and in 2008, I overweighted FriendFeed for sure. It makes sense that maybe I should dial back a bit on FriendFeed and spend more time in far-flung places in 2009.

5) Have More Time for In-Depth Reviews

At the beginning of the year, I feel I did a fairly good job of having the time to invest in fully reviewing new sites and services, to explain their every feature. From Toluu to ReadBurner to Feedly and Assetbar, it was not uncommon to show you every nook and cranny of a new site, so you could join it as an expert. But in the second half of the year, especially after the arrival of Matthew and Sarah, this time comparatively evaporated, making my reviews less detailed. I still try to do a good overview of new sites and iPhone applications, for example, but it'd be good to feel sharp about these reviews again in 2009.

6) Follow Up On Sites and Services After Their Launch

I want to avoid being a "hit and run" blogger, as I put it the other day, announcing something and then only covering them again if they had something major. Doing that, I feel, makes you a tertiary part of the story, and certainly not an embedded expert. I'd like to look back on the many different services that have either debuted here or been covered, and see how they have progressed in 2009.

7) Attend More Industry Conferences and Panels

Given blogging and the social media space is not my full-time job, I can't exactly say attending all the different events in the space is something that makes sense for my career or pocketbook. But I did get to attend Web 2.0 Expo in the Spring, and BlogWorld Expo in the fall, and enjoyed meeting many of the people with whom I'd only engaged online. I would like to make more time to see the industry mingle and participate in 2009.

8) Participate More Visiblity on Conferences and Panels

I've been lucky to learn that a panel I'll be participating in was accepted for the South By Southwest conference (SXSW) this upcoming Spring. This follows the panel I participated in with Chris Heuer and Tom Foremski, and a pair of panels and BlogWorld Expo this fall. As the blog has gained visibility, opportunities are making themselves available, and I would like to be less of a wallflower and more active in 2009.

9) Be More Active on Podcasts, Videoconferencing

Having blogged on the site for three full years now, showing I can put a blog post together and cover a story, or participate in social media is not a surprise. I also had the opportunity to participate in the Elite Tech News podcast earlier this year when it was more regular, and the ReadBurner podcast through the year. I think it would be fun to get the opportunity to showcase new entrepreneurs, bloggers and services using audio and video in 2009.

10) Highlight More Bloggers and Entrepreneurs

In 2008, one of the major focuses I had was to bring to light new bloggers that had previously toiled in obscurity. By launching the series of five new blogs each month, by bringing on a stable of talented writers and keeping a focus on startups and the people behind those services, we played a role in making people more known by the end of the year than the beginning. I don't want to lose momentum on this, and keep bringing new people to the fore in 2009.

These ten items are on my list because I believe, in combination, they will help my understanding of technology, the industry, and the people better. It will help me have a more rounded tech experience without being too focused on niche topics and insulated. 2008 saw some strides in many of these areas, but I know I need to step up my game in 2009, and I look forward to the challenge.

In the months I've had Disqus installed as the comments engine to my blog, I've been lucky enough to see some great engagement with readers of the site. The centralization and tracking of my comments around the Web, in addition to managing my comments in one place, and via e-mail have been a big help also, as has the service's extensibility and tracking via sites like BackType and FriendFeed. But one of the downsides of Disqus' popularity is that it has grown a bigger target for comment spammers aiming to shill for their prescription drug of choice, and all too frequently offering up ridiculous items, like gold for the game World of Warcraft. But as of tonight, Disqus has rolled out some new spam moderation functions that let you help fight the spam battle and, hopefully, reduce the amount of spam going forward.

In July, I suffered my first Disqus comment spam attack. Though it remains the largest flare-up to date, hundreds of spam messages have flowed into my mail box through the blog. Every morning, and at various points during the day, I'm faced with the routine of hitting reply to each e-mail and saying "Delete", to get the offensive gunk off my blog. I'd rather do that than leave the automated barnacles hanging on my posts, but the situation hasn't been getting better of late.


My Archive of Removed Messages Is Expanding
In addition to the 40 real comments I got on the blog today, I also got about 10 fakes - with about three or so a day in recent weeks. The topics themselves don't vary, but the names do.


Disqus Asks for Us to Help Them Fight Spam
Now, according to the Disqus blog, I can reply back to assumed spam with the simple one word command of "Spam", adding to the service's knowledge and helping them form a blacklist. You can also go into the admin section of your Disqus site and block the comments as spam there.

The war between Web services, e-mail, comments and spammers will never be over, I am afraid, but at this point, the move is yours, spammers. Disqus isn't taking this fight lying down. The service also promises some new features coming soon, including a new interface and internationalization.