Comments as a Platform, Or Silencing the Trolls

My plea to Jack on Twitter.

Web content has typically divided into three camps - those who create, those who react, and those who just watch. The lurkers, if you will. From the very earliest days of blogging, those first posts awaited the inevitable comments, and, given a clear revenue stream, you would see early participants like Fred Wilson say that "comments are how bloggers get paid."

[Source: https://vanelsas.wordpress.com/2008/06/02/the-real-value-of-social-media-interaction/#comment-2531]

The earliest engagements we had with people who read our site gave us incredible discussions, and spawned more posts and even, in rare cases, changed minds. Sites like Digg, Reddit, Slashdot and others became known for their diverse threads, and those in the comments are why you showed up.

But we've also seen the pendulum swing the other way. Everybody knows to "never read the comments" on popular news sites, as the most aggressive vitriol and ignorance floats to the top. YouTube comments have long been notorious for their lack of quality (though I feel this has improved of late). And Twitter, for many who should be able to use the platform, their every move can attract trolls who have a vendetta to take them down - but somehow don't get banned.

As social media sites eclipsed the momentum of blogs, conversations moved. We adapted by integrating social discussions from FriendFeed, Facebook and Twitter and appended them to our blogs. We would all share our posts on social, and then engage where the content landed. The best bloggers would find their readers wherever they were. But others simply turned comments off. Maybe it is because they were full of spam (they were) or the quality wasn't there (often true), but also, because the total quantity declined.

Let's go back to talking about Twitter. Twitter drives me nuts because it's fantastic and so poor at so many things. They seriously have real-time on lockdown. There is no better place to see what is happening right now. If there's a calamity, search Twitter. A breaking news event? Search Twitter. A sporting event? Twitter.

But Twitter has this awful habit of giving all users an equal voice. Now hear me out what I mean.

If you tweet publicly, anybody who you haven't blocked can reply, and their content is appended to your tweet. It follows you around. If a Republican politician posts, left-leaning posters race to take down their message, while the MAGA crowds prop it up and try to gain eyeballs. If the Kardashians say something, the crowds pounce on the valuable real estate quickly to show their adoration or pimp whatever link they've got going.

And down the publicity food chain, if you're a woman, especially a visible one, you get awful men saying foolish things. I guarantee it. They may call you names or question your ability. You block one and ten more pop up. If you're black, or Jewish, the racists will find you. They all know how to tweet.

So what I recommend above all other Twitter changes is the ability for people to reclaim their space. Hillary and Trump should both be able to post information without the crowd's replies being appended. Just like blogs and YouTube stars can turn comments off, Twitter users should be able to as well. The thing about social networks (and most products, to be honest) is that you should give the users control. But they haven't done it, and I think it delivers a great disservice to the platform, which has become a hotbed of harassment and hate - as Reddit and others have too.

If you can trust your commenters enough to give them a voice, by all means, amplify their voices. But when they have shown you time and again that they cannot be trusted, turn it off.

Echo Prepares World for Migration to a Web of Streams

The foundation of the Web is moving from one of unchanging static pages to continually updated streams fed by external services. Gone is the time when publishing an article or a site was the final step in creating content. Instead, this can often signify the beginning of the content's life, as it is shared, retweeted, liked, commented on, and further distributed. Echo, a company that first made its name in the comments space, explained to a full hall of industry onlookers Tuesday morning that dynamic social experiences are going to rule the future of the Internet, further arguing they have placed themselves at the center of this trend, having built a flexible environment for people to tap into the activity streams and benefit from the Web's continued evolution, instead of seeing visitors capitulate to household name social networks.

Companies like Facebook, Twitter and LinkedIn have unlocked billions of dollars in revenue around user streams of content, while traditional publishers have often held to traditional business models, unable to keep pace, said Echo's CEO, Khris Loux. "Today's publishers are ill-served to serve even their own audiences," he said. "The conversations, traffic flow and revenues have moved on."

What Echo recommended was to give publishers, ecommerce sites and startups the capability to craft user-centric, stream-centric experiences themselves, tapping into activity stream data as the unit of currency to power interactive next generation sites. To accomplish this work, the Echo team has created a stream server to deliver real-time experiences that support the existing brand and content without traditional costs of real-time. It was explained the company's new stream server supports thousands of queries per second, with live updates, based on open standards, with each item passing through the stream having the opportunity to be touched with the appropriate action (such as likes, replies, flags, votes, promotes, etc.)

But rather than building out a complex product portfolio to white label or charge premium fees to customers, Echo told attendees yesterday that they work "up to the API" and partner with other startups to connect their services to end users.

"We have coded up to the API and no further," said Loux. "It's scary as we can't solve anyone's problem ourselves. But that also means our partners have as much power as we do."

Echo, since its product shift in 2009, has signed up many top name brands to its platform, some of whom presented Tuesday, including Sports Illustrated. Displayed on SI.com and other partners' sites were real-time comments, user reactions, badges and achievements, and a visually appealing image gallery for hosted graphics. Partners supplying many of these things included Realtidbits, Janrain, Klout, Badgeville, Branchnext, Clicky and Arktan, who claim to have connected to Echo through open standards, enabling customers to switch providers in the future if desired.

"It's the beginning of a new way to look at software," Loux said. The company hopes to also offer a custom application store that enables partners to connect hours of effort to dollars through showcasing their apps on the market. Executing on a planned feature that is stream-centric looks right. Echo's demos from Tuesday and well before are showing real promise about the future of the Web. Rather than shying away from competing with the Web giants, Echo and its partners are set to offer a serious alternative - keeping ownership of the entire social experience on the corporate site.

Disclosure: Chris Saad, an Echo employee, and I occasionally collaborate on the Edge Theory conversations series, and I consider him a good friend.

Echo Debuts Real-Time River, Highlights Reader Activity

After declaring the world of traditional comments dead last year, Echo has continued its quest to bring the world of real time reactions from around the Web to publishers looking to surface more engagement with their community. Today, Echo introduces a product they call "Echo River", which brings responses from commenters to media stories practically to equal footing of that of the author, raising the visibility and surfacing real-time feedback that practically promises to make sites more sticky as users participate.

Last month, Echo introduced a "Recent Comments" widget, which brought the newest responses to the front of the site. This new real-time widget updates live, not requiring refresh. It plays a key role in this morning's update, as the comments widget runs alongside River-enabled sites, which also display real-time comment counts for new entries, and nests the reactions (be they from comments on the site, Twitter, Digg or other sources) below the entry.

Echo, which has a wide array of large media customers in its roster, highlighted its River offering with staged demos on Slate.com, TechCrunch and Mashable. The River function even managed to pull comments from disparate technology sources, such as WordPress (on TechCrunch) and Disqus (from Mashable). This move further separates Echo from its assumed competition, and puts them more into the real-time space, rather than vanilla comments.

"Displaying conversations on the home page in this way changes the way people see the front page of a typical news site," said Chris Saad, VP of Strategy for Echo in a press release. "Readers get to see a summary of what people like them are saying right from the front page, getting a new perspective on the headlines of the day... This new product continues our mission to turn static web pages into vibrant real-time experiences, driving Facebook style engagement on our publisher sites."

While the old way of comments might be dead, by their positioning, what this new product does do, for its premium members, is practically give sites' community equal prominence to that of the original writer, who sees their work do battle with often opinionated readers. And if a conversation flareup does ignite, Echo will show each update in real time. It's enough of a push that the service's executives used lofty phrases about changing the world of publishing "one product at a time", fighting against a world of static media.

For premium subscribers to Echo, adding the new River functionality is simple, just requiring a little Javascript code. The company says the River can be customized as to its content and appearance.

Disclosure: Chris Saad of Echo and I occsionally co-host the Edge Theory Conversations podcast.

Google Reader Enables Public Comments on Shared Items

One of the best benefits of sifting through hundreds of new RSS items each day in Google Reader and selecting the best ones to share has been the ensuing conversations that have developed as a result. It used to be that these conversations were limited to networks like Socialmedian and FriendFeed, but they later took place within Google Reader itself, for all friends I had hand approved, and later, in Google Buzz, assuming I had given people permission. Now, the Reader team has removed the hassle of picking who was enabled to comment or not - making shares have the option to be public to the world for conversation. This highly anticipated move is a big reason I have continued to be so bullish about sharing Reader items and participating where they land on Buzz.

If you have not already seen the prompt, the next time you enter Google Reader, you will see the option to "Keep my shared items public" or to "Make my shared items protected". Hit "Save" to keep comments public, or choose to keep the shares open to only contacts in your friend list.

You Can Now Make Your Shared Items Public to All

This move is incredibly simple, when contrasted to the labyrinth of privacy settings required at Facebook to determine where your content is being displayed, and it protects those who have previously opted to make their Reader shares private, as explained in the company's blog post announcing the changes this afternoon.

My Shared Reader Items Are Visible to All

The ability for the world to comment on Google Reader shares should be a big boost to Buzz, as even more places are open for discussion. As mentioned in April, statistics show Reader shares as the 2nd-highest source for conversations on the network. This should bring that percentage up a great deal.

Want to see my shared items? You can find them here, or we can get connected on Buzz.

Echo's Reactions Platform Hits It Big With Old Media

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

Cliqset, Status.net Support Salmon for Comments Migration

As Marshall Kirkpatrick noted in a post on ReadWriteWeb this morning, the Salmon Protocol project we first introduced back in October of 2009 looks like it is progressing beyond the planning stages, as it has been integrated in two small, but influential, social networking sites, Status.net and Cliqset - both of whom are strong open standards advocates laboring away in the shadows of larger communities.

The Salmon Protocol, which aims to define a standard protocol for comments and gestures (such as likes) to swim upstream to the originating blog, hopes to unify conversations across diverse locations. It's planned for adoption by Google Buzz (See: Designing Buzz for a Google-Free World) and solves the problem that first blew up back in 2008 around fractured conversations.

While many people, including myself, have adapted to a new world whereby conversations take place in a wide array of communities, it would be nice for the content originator to have one centralized location to see all downstream activity.

Evan Prodromou of StatusNet mentions integration of Salmon's digital signatures in a blog post from Sunday, where he also notes support for Activity Streams encoded in RSS 2.0 and Atom. The move, paralleled by deployment at Cliqset, should be what I hope is the start of a lot more announcements, from small and big companies alike, to make Salmon a reality. The next big target, which I am biased in favor of, obviously, would be for Disqus to integrate with Salmon and pull comments upstream to this blog.

I managed to find time to talk with Darren Bounds of Cliqset at SXSW earlier this month. In our quick discussion, recorded on CinchCast, you can find his comments on their support of open standards, and that network's direction - which could hint at why they're an early adopter of Salmon.

BackType Launches Labs, BackType Me, for Social News

BackType, the best comments search engine on the Web, which launched in 2008 and has since morphed to act as a "real-time, conversational" search engine, today announced the introduction of BackType Labs, an "in progress" look at some of their newer projects. The first to debut is a service called BackType Me, which aims to find out what content is being shared by people you follow on Twitter.

Funded by Y! Combinator, BackType has grown from its two cofounders to a team of three, and is actively looking to hire two more engineers, focused on software and search. In the last few months, the threesome has evolved the site to display news by category, such as "Technology", "Politics" or "Entertainment", and has grown closer to Twitter, displaying topics that are "Hot Right Now", much like Twitter's trending topics.

Shares from Within My Social Circle on BackType Me

Now, searching BackType displays shared items from friends as well, which feeds the BackType Me product. Search BackType for a specific term (for example, the Oscars) and if logged in, you can see which of your connections shared a specific article on Twitter. The core BackType Me service displays all content shared in your social circle, and highlights the individuals who have shared it.

BackType Me could be a quick way to scan important items shared on social sites from friends in your network, and I assume we can expect more to come from BackType Labs. The team is already hinting at something called "BT.IO", which could be yet another URL shortener or something else entirely. We'll be watching them at work in the Labs when it debuts.

How To Enable Comments on Google Reader Shares In Buzz

With the recent launch of Google Buzz, shared items from Google Reader's RSS platform have become more visible and more important than ever. (TechCrunch said growth increased 35%) Those Buzz users with existing shared Reader feeds had these streams automatically connected to Buzz, enabling Buzz viewers to see your shares, and if enabled, to leave comments, once obscured in your own private network, in a public place. But those following you on Buzz don't automatically have the option to comment on your Reader items, and for some, this can be frustrating. Here's how you can help them join the conversation.

Google Reader enabled conversations back in March of 2009. As somebody who has adapted to a distributed multi-locational world of conversations, I have optimized my activity to embrace the conversations in this platform. In the last year, I have been enabling connections to comment on my Reader shares, and as a result, the conversations grew dramatically.

An Active Google Reader Item in Buzz, With Comments

But the integration, to date anyway, has required some effort on my part. As new followers added my feed to their reading list, I have had to give permissions to these followers to comment on my items, by adding them to a folder, which I called "Friends". This work, a few followers a day, has paid off in a big way, as I have enjoyed fantastic conversations in my Reader, and now, this group can participate with me in Buzz.

Many of you are probably seeing more followers from Buzz into your Google Reader world than you ever had before. Now, it is more critical than ever to move these folks into a folder who can comment on your items, or they will be met with errors, locking them out of your conversation.

So here's how you fix it:

1. Log into Google Reader at http://www.google.com/reader

2. On the left side, click "Sharing settings". (Shortcut here)

3. Where it says "Who can see your shared items?", there is an item which says "Who can comment on your shared items?". Those items that have checkboxes are enabled.

My Sharing Settings and Connected "Friends" to Comment on My Items

4. Click "people are following you", and from there, you can add individuals to folders.

Adding a New Individual To a Group for Commenting

5. Repeat until you're done.

Note How All My Contacts Are In Groups for Commenting

As new followers come in, even if you choose not to follow them back, you should add them to a folder that can comment on your items. With Buzz drawing ever more attention to your Reader shares, and Reader shares being a big part of the content there, it makes sense to extend the conversation there. If this seems complicated, note it is due to a policy of having "private" conversations in Reader from the last year, and adapting this policy to a new public place. Until Google Reader enables fully public conversations on all shared feeds, this will be how you can make your feed an active place.

You can find my Reader shares here: http://www.google.com/reader/shared/louisgray. We can get connected on Buzz here: http://www.google.com/profiles/louisgray.

Blippy Surfacing Popular Purchases to Increase Engagement

A few weeks ago, when I first started using Blippy, the site that tracks my purchases offline and online, I said it simply proved how boring I am. Aiming to not itself become boring, as exciting as reading old receipts as popular funnyman Stephen Colbert recently called it, the site recently introduced two new features that will highlight user activity and popular purchased items, bringing discussions to the top.

For fellow FriendFeed veterans, Blippy's move is much like increasing the visibility of active discussions on the site through "best of day". It also mirrors the recent move by Facebook to highlight popular entries from you and your friends in the newsfeed.

Lively Chatter in My Blippy Stream Surfaces Active Purchases

While previously, activity on your Blippy stream would move chronologically out of the main view as you made more purchases, active threads can now be found in a section Blippy calls "Lively Chatter". Also, you can check "Popular Purchases" from everyone on the site, leveraging the increasingly popular standard of "likes" and comments.

One Active Discussion on Blippy

The more people you follow on Blippy, the more likely it is that you will see comments and likes in your stream. These are highlighted in "Recent Activities". Clicking on "Lively Chatter" shows items that have gained comments (including comments from yourself), letting you see conversations about the movies and music and apps that you are buying.

Another Active Discussion on Blippy about Siri

For now, Philip Kaplan (aka Pud), creator of the site, is the most frequent commentor in my feed, which comes as no surprise, but this may change as people grow more accustomed to making the site more of a two-way platform, instead of just simply importing.

While some look at Blippy as a perfect example of oversharing or our own willingness to put personal data on the Web, I see it as a logical extension to our recommending and telling people what we "like". Pud, curious about the series "Breaking Bad", which popped up in Mike Arrington's stream, even had the show gifted to him due to his curiousity. I expect to see many more similar actions driven directly from activity on the site.

How I Aimed to Do Better On the Web in 2009

As 2009 loomed, near the end of 2008, I took a look back at how I was utilizing the Web and set for myself some direct goals, not necessarily number-oriented, but measurable nonetheless. As I illustrated in 10 Things I Wish I Would Do Better On the Web Come 2009, I wanted to make a concerted effort to interact with readers on the site (and on other blogs), and be more active away from home, participating in events, panels, podcasts, and the like. (Note Steven Hodson's reaction to this list as well)

With the goal of keeping myself accountable, here's the year's goals revisited, and summarily rated with a success or failure.

1) Make More Comments on Original Blog Posts

Success: Although a great number of comments continue to remain on FriendFeed and Facebook, or Google Reader, I made a concerted effort to leave comments in reaction to posts for blogs big and small this year, be it the individual Posterous or Tumblr account, or a large blog network, such as TechCrunch or GigaOM. I don't think I will ever fully do as good a job here as I would like, but I was certainly aware of my activity in 2009.

2) Respond to More Comments on louisgray.com

Success: Disqus makes this process extremely easy, letting me respond to comments that come to the blog via e-mail, or in rapid fire with their simple user interface. On "hot" blog topics, I made sure to respond to a good number of thought-provoking readers, and "walk down the line" to add my views. As with the above, this too could be improved, but I believe I was better at this in 2009 than in 2008.

3) Be More Interactive On Twitter

Success: I am still not as huge a Twitter fan as many people. I continue to use Twitter more for links than conversation. But I also wanted to use the service to help promote the #BlameDrewsCancer phenomenon, and have been very active in responding to @Replies. I try not to use the site as a status update service all too often, but this became more than just a repository for "New Blog Post" in 2009.

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

Failure: I believe I merely exchanged some sites for others here. I continue to spend a lot of time on Google Reader and FriendFeed (no surprise to most of you). While in 2008 I spent a bit of time on Socialmedian and Strands, I removed myself from those sites for the most part in 2009, and replaced them with more use of Facebook, plus the addition of Ecademy and Simler. (which have some FriendFeed-like elements)

The leverage of RSS continues to keep me on Reader more than in visiting many different downstream sites, and I still am visiting non-tech at a bare minimum.

5) Have More Time for In-Depth Reviews

Success: In addition to a great number of in depth reviews of new iPhone applications, I also started using YouTube to help describe some services, including Lazyfeed and my6sense. In terms of other Web services, I have tried to make sure when covering a site that I have walked through it and included a good number of screenshots or explanatory items to provide more background, even if it means I am not first to publish.

6) Follow Up On Sites and Services After Their Launch

Partial Success: Following up on all sites and giving equal time is practically impossible. But for every site I discussed only once, there were many more, such as Brizzly, Lazyfeed, Simler and others that saw multiple pieces of coverage that included updates on the product and company.

7) Attend More Industry Conferences and Panels

Success: 2009 saw me attend BlogWorld Expo for the second straight year. In addition, I attended SXSW in Austin, LeWeb, multiple TechCrunch CrunchUps, and had other speaking opportunities.

8) Participate More Visiblity on Conferences and Panels

Success: Adding on to the above, I gained the opportunity in 2009 to branch out a bit, leading a panel on Twitter applications at LeWeb, speaking on content aggregation at SXSW, speaking on realtime at BlogWorld, on information overload at the Inbound Marketing Summit, the death of advertising with the SFAMA, and other opportunities. I aimed to say yes to as many as I could, travel and expenses willing. 2010 should continue the trend.

9) Be More Active on Podcasts, Videoconferencing

Partial Success: 2009 did not feature the regular podcasts that were attempted in 2008 with the ReadBurner Weekly and Elite Tech News podcasts being shuttered. I did participate in FFundercats a few times, joined Leo Laporte for a holiday This Week In Tech, and Steven Hodson for another, but this was less than I had anticipated.

However, in addition to the group podcasts, I started using Cinch a lot, letting me send off single person podcasts from the iPhone, or 1-1 interviews, as were done at LeWeb.

10) Highlight More Bloggers and Entrepreneurs

Failure: As in 2008, I continued the highlighting of five new bloggers and ten new Friendfeeders each month through the first half of the year. But the purchasing of FriendFeed by Facebook in August pushed this plan askew, making me openly wonder if it made sense to continue that practice. I continue to seek out new content and highlight it through Google Reader shared items and other places, but could improve.

By setting these goals at the end of last year, they were somewhat in the back of my head as I made plans and actions through 2009. I tried not to set an arbitrary number-based goal that would make things seem like a chore, but did want to do the right thing. As you can see, many of these goals, especially in regards to events, were much stronger in 2009 than 2008. I just thought it made sense to report back to you.

BackType Feeds Partners Faster, Thanks to PubSubHubbub

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.

Proposed Salmon Protocol Aims To Unify Conversations on the Web

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 Blog's Place In A World of Microblogging: Not Dead Yet!

Even as the microblogging space seems to be white hot these days, the world of longer-form blogging is still seeing impressive growth, with all major blogging platforms showing greater than 20 to 40 percent growth year over year, and record users, blogs and total readers, according to Compete.com data and a presentation from Google's Rick Klau, product manager for Blogger, who spoke at Blog World Expo this afternoon. Rick reported that his platform, Blogger, which I use, is now seeing nearly 300,000 words per minute, scaling to 417 million words per month, from more than 10 million content creators.

Yet, despite this high usage, many have challenged the platform, saying "blogging is dead". There are more than 360,000 results on Google saying that "blogging is dead", with many high profile articles saying that disparate social networks like Facebook, FriendFeed and Twitter should be where people's attention are. But Rick said that the rise of microblogging didn't necessarily come at the expense of traditional blogging. In fact, he said these third party sites actually served to drive even more attention and traffic to the core blog content.

"Microblogs are complementary, not competitive," Rick said. "It is a driver of attention and engagement back to the blog."

For Rick, who has run his own personal blog (at tins.rklau.com) and has been active since 2001, he reported that Twitter has become the highest traffic generator for his site outside of search, and in that list, so also are Facebook and FriendFeed. He suggested rather than trying to fight against the flow on microblogging, to embrace it, and make sure your content is available to these disparate networks, while remembering to engage where it lands.

"The blog tends to be visited by people interested in what you are saying, and the people on Twitter and Facebook are interested in you, and by proxy, what you are saying," he said. "I happen to believe that based on what I have seen with my blog for eight years, people are comfortable communicating in the environment they have chosen. If I force the conversation back to the blog, I will lose the audience who have the eagerness to engage, comfortable where they live."

Rick suggested that if you are a Facebook user, to pull your blog content into Facebook, making it available to this new audience, who may leave comments much different than those which are native to your site. He also recommended that you utilize tools like bit.ly to track statistics and click-throughs to your site from those links you send through Twitter, to help you understand how much the microblogs are impacting your own blog.

Given his background at Google, Rick made it clear that the company's data-driven nature forced decisions, and the company continues to see serious growth in traditional blogs.

"There are very few questions that get asked at Google when I don't have the data to back up an answer," Rick said. "You don't get many opportunities to say "I feel" or "it seems" at Google."

But in his experience, Rick suggested that bloggers not get locked into writing posts for specific statistics, including page views. He said that as you are a multi-faceted person, you should be confident writing about more than just one thing, so one should feel comfortable covering more than just the single topic.

"Don't become a slave to the focus of your blog at the expense of having fun.You can be passionate about a wide variety of subjects," he added.

Blogging and micro-blogging are not a zero-sum game, but can be complimentary. Sending blog content to downstream networks makes that content available to those connections who are more comfortable in their own environment. As I have mentioned many times, your blog is your brand - which Rick echoed by saying that on your blog, you control every pixel, and therefore, the end user experience.

Bloggers need to adapt to the new world, but aren't antiquated in this new world. It makes sense to participate wherever the content lands and wherever your readers are, without pushing to centralize the conversation on your site, but there is no substitute for long-form conversations and being passionate. Rick communicated a simple formula: "Content + Passion + Engagement". And that will make the blog go, even in a world of change.

Why And Where We Share: Distributing Quality With Impact, Intent

Regardless of whether you first came in contact with my content here, or through other streams, you know that the vast majority of my online life has to do with the creation, filtering and distribution of information. In addition to authoring new stories here on the blog, I try to be an active and avid consumer of RSS feeds, and updates from social networks including FriendFeed, Ecademy, Socialmedian, Twitter and Facebook. In turn, I make a very serious attempt to redistribute the best content of all that I see back out to these same networks. Even if the volume of data I am taking in and pushing back out is high, it is certainly not random. Every time I hit a "share" button, or I hit "post", it is calculated. I thought it might be a good idea to discuss this a bit more.

First, some statistics.


20,000 Items Isn't That Many If Divided In Smaller Chunks

In the last 30 days, according to Google Reader, from the 703 subscriptions I follow, I read 20,090 items and shared 766 items. This means that on an average day, I am taking in 700 to 900 items (less on weekends) and sharing about 25 to 30 items.

This data, for the last 30 days, shows 3.8% of all items get shared, or just under 1 in every 25 posts. And while it may seem that 703 subscriptions is a lot, it is, in my opinion, a very healthy segment of the tech Web. If subscriptions that I follow go too long without relevant data worth sharing, I do remove them from my feeds, while also always being on the lookout for new sources. So you can consider my shares to be the top 4 percent of what I think is the top 20 percent of tech news, making the result greater still.

Second, the flow.

When I hit "share" in Google Reader, a few things happen.

1. The item is added to my shared link blog.
   
2. The item is available for comments within Google Reader for approved contacts.
   
3. The items are shared on my FriendFeed, Facebook and Socialmedian.
   
4. The items are sent to the @lgshareditems account on Twitter.

One button hits as many as five networks - so yes, there is impact. I am cognizant that if I share too many items overall, or share too many off-topic items, it will harm the quality of my downstream feeds, and people will either stop engaging or unsubscribe.

 On Twitter, Brett Kelly Noticed A Bump in Engagement
But there's more to sharing than Google Reader, as you know. Sharing can also be done through comments and likes on FriendFeed, which bump a story back to the top of the feed, and expose it to other people. The greater your following, the greater the potential for downstream impact, meaning if you have an active account, then it's possible to look back on your activity and see others taking action on those items - much like the wake of a speedboat on a lake, as your zipping along leaves ripples behind. The retweeting phenomenon on Twitter has been well documented. Also, I share the bookmarks I make on Delicious to the same social networks - FriendFeed, Facebook and Twitter. One save hits four places. I wouldn't take so much effort to get the flow right if I didn't know that it had impact. One of the pleasing byproducts of being consistent and focused is that content creators say they get a traffic or visibility boost from my shares. My goal is to reward good writing, reporting and quality, and to also reward those who have opted into the streams, that they receive quality content.

   Holden Page Saw His RSS Numbers Spike

So how do I decide?

1) I Share Items On Topics Relevant to the Downstream Audience

The first filter on whether a story gets shared is if it is on a topic I assume my readers would find interesting. Even if I may be interested in baseball, humor, politics or food entries, they don't get shared into the downstream feeds because the readers are looking for news on technology. Most specifically, coverage of new startups, Silicon Valley companies, social media and networking tools, RSS, business and statistics data.


2) I Share Originating Sources Where Possible, Not the Echo

If a company like Apple, Google, Digg, Facebook, or Twitter makes a new entry, it is no doubt going to be respun by dozens of downstream tech writers. If I see this happening, I will find the original unfiltered post and share that to bring their message directly.


3) I Share Items That Are the First to Report News Or Have A Unique Angle

In the tech blogosphere, it is not too uncommon for many different sites to talk about the same story - especially if it is about one of the most-popular companies. In the event of massive duplication, I try to share the first of the respected sites that gets the story right and done well. Because of this "echo chamber", I am extra focused on finding new stories from people who are going against the grain - covering new companies that don't usually get a lot of ink, or are thinking about the day's news in a different way. I also am happy to reward sites that get unique Q&As or interviews with tech leaders, or are the first to pull down data from the SEC around funding or M&A activity - passing on true journalism rather than opinion.


4) I Share Items That Targeted Quality Over Speed

It is easy to tell when a blog post was quickly slapped together to be first out the door, or just to hit a post quota (a common issue at multi-author sites that are ad-driven). As soon as I can ascertain that a post is on topic, has an interesting angle and has been thoroughly researched, it is a pleasure to send it downstream. This is even more true when a more obscure blog acts in a mature way and deserves to be highlighted.


5) I Avoid Sharing Items That Are Built for Controversy

As I have tried to do here, I aim to keep my downstream feeds argument and rhetoric free, wherever possible. If headlines and photos and angles on stories are overwrought for the sake of driving debate, controversy or nonsense, they are skipped. I do not want to reward bad behavior.

In Conclusion:

I talk a lot about sharing and data flow on this blog, because I recognize the new world of blogging goes beyond these pages. Today's best bloggers are participating in the downstream networks, both as content creators and as information filters. It takes effort to be in the first wave of filtering, to try and separate the wheat from the chaff, and drive quality to other networks, but it is very rewarding to know it provides value. Over time, I look forward to finding even better ways to filter, organize and display third party content that has passed through me first.

I Don't Want To Hear About Distributed Conversations Any More

This morning, Google introduced a feature called SideWiki for Google Toolbar users that lets people add comments and annotations to Web sites. This is not a new approach, and it has been tried with varying lacks of success in the past, as most people without an agenda don't want to spend time marking up third party Web pages. But as predictable as rain, we again see people railing that there is potential for this service to take even more control away from bloggers and site administrators in terms of how their content is positioned, or where the conversations should take place.

Led by Jeff Jarvis, who simply said "Danger" and echoed by others, including Steven Hodson of the Inquisitr, who called it "a bad idea - very bad", the same stories I thought we had beaten into the ground almost 18 months ago in the Shyftr debacle are coming back - even after more than a year of a greater level of distributed conversations, as comments are now strewn all over the Web - not centralized on the originating blog.

Jarvis says: "Google is trying to take interactivity away from the source and centralize it," and adds "It takes comments away from my blog and puts them on Google. That sets up Google in channel conflict vs me. It robs my site of much of its value."

In parallel, Hodson says: " Sidewiki is nothing short of an attempt by Google to take control of the conversations that happen on blogs... It takes away one of the most important parts of a blog – the conversation – and locks it on the Google."

Here we go again.

Let's stop kidding ourselves. The battle for control over conversations and the silo of discussions is done. Any blogger who believes that they can control the conversations and prevent discussions in far-flung social networks is deluding themselves. And yet, every few months, a new innovation, be it comments in Google Reader, or something like this, freaks the old guard out.

Jeff and Steven's comments are mirrored by Josh Schnell, who in a guest post for Tamar Weinberg on Techipedia cries out that Content Aggregators are Killing Content Creators.

Here's the reality: Conversations have moved to where the reader wants them to be - and the best content creators shouldn't care if they get to have conversations on their content in any of these networks. The best content creators and the best Web brands shouldn't care about what people may say on their SideWiki, any more than they should panic over reviews that happen on Amazon's Marketplace or in the iTunes store. People are entitled to their opinions and their commentary, and any further efforts to try and force people to have these conversations in a single place should be extinguished.

In April of 2008, I once asked, "Should Fractured Feed Reader Comments Raise Blog Owners' Ire?" and apparently, some people continue to be ticked. But we need to evolve. That's why there are new services like Echo, who famously declared the death of comments and the new version of Disqus, which also aims to pull in reactions in real-time.

Mark Hopkins of the SiliconAngle sees beyond the scare tactics and recognizes that SideWiki is much more and not just about "stealing conversations". He says:

"The fact is that in the golden age of the social web, conversations will spring up more and more places outside your silo, with or without you. You can work to leverage them or you can get upset."

Congratulations, Mark, I'm proud of you. Now, it would be fantastic if more people would evolve and move forward instead of crying foul about the way it used to be.

Feedly's RSS-Powered Start Page Includes Reader Conversations

As I've mentioned a few times on the blog, the conversations in Google Reader are playing an ever-increasing role in my information consumption workflow. The RSS reader's enhancements have not been lost on the makers of Feedly, who have been working on a magazine-like start page for the better part of a year, gaining loyal users who appreciate its enhanced interface for subscriptions. This weekend, the company added support for friends and comments that you have in Google Reader, meaning you are not missing the conversation by using Feedly instead.

As introduced back in June of 2008 (See: Feedly Brings New Social Experience to Start Page, Leveraging RSS), Feedly operates as a start page or magazine hybrid, consisting of a cover page, a digest, the latest information, and now, "friends" and "comments".


Comments in Google Reader Shares Display in Feedly


Items that are "Liked" In Google Reader are Highlighted in Feedly

Selecting "friends" shows you items recently liked and shared by your contacts, while "comments" exposes the conversations taking place within shared items on Google Reader from your friends. While not every single share spawns a conversation, many of them are, including those on my shared items feed, where I have frequently seen items gain more comments than the original blog post itself of late.

Feedly has also done more than clone Google Reader's utility. They have interestingly added a tool called "Karma", which, if you enter your Twitter ID, will tap into bit.ly, seeing how many clicks a tweet you posted received, as well as how many retweets. It's a good way to see if your activity on that social network is gaining a following.


You Can Gauge Your Twitter "Karma" In Feedly
You can find Feedly at http://www.feedly.com/. For now, the service relies on Firefox, but we've been promised support for Chrome, and maybe other interfaces, is coming.

Disqus Launches Version 3 Of Comments, Adds Profiles

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.

Conversations on Google Reader Shared Items Are Booming

For the world's leading RSS reader, integrating social functions hasn't always been drop-dead simple and easy. With each new addition, be it the recent "Send To" features, the addition of "likes", or the ability to selectively enable friends to make comments on your shared items, the service needs to scale in a way that has brought many other Web-based feed readers to its knees - compounded by Google Reader's accelerating user base. And while the company works to make sharing and engaging simpler, I am already seeing a rapid rise in conversations within Google Reader, both on my own posts, and on those from others I share. Recently, the total number of comments on some posts has even eclipsed those natively here on my site, or on FriendFeed, Facebook or anywhere else.


Almost 600 people can comment on my Reader shares.
Since starting my shared items link blog in Google Reader a few years ago, I've passed along almost 10,000 links (a point I may pass by the end of the month). I recognize my pace of sharing between 20 and 30 items a day is on the high end, but these selections represent the top 4 to 5% of all articles I see online, with the intent of passing on only the best to those who consume the shares downstream. I've even had some people say they have unsubscribed from reading feeds directly, trusting me to be a human filter. That's a little daunting, but a task I can take.

You might remember that back in March, Google turned on comments on these shared items. Though activity was initially slow, I have seen increased velocity, especially after reorganizing my contacts.

As Google Reader does not have public comments on shared items that are visible to everyone, they have taken the middle road - showing these comments to those who are also subscribed to the shares, and only enabling those people to comment who have been added to a specific group by the sharer. After several hundred people had signed up to follow my shares, and I was seeing only a little activity, I realized the problem was mine, so I took some time to organize all my contacts, and enable everyone who follows with the ability to comment, just like in FriendFeed or Facebook. This part is critical, so if you do have a lot of people following your shares, go to your sharing settings in reader, and make sure that they are in a folder that has access.


Each of My Friends Is In a Group that Has Access to Commenting


This Article On Lazyfeed saw Dozens of Comments In Google Reader
With that change, people who may previously have been watching the shares go by, but couldn't comment, now can - and the results have been very interesting. Some of the more popular threads on shares from me have seen on the order of dozens of comments, even when the original post may only have shown a handful on the original blog.


Another Popular Topic of Discussion Within the Reader Shares
While a few years ago, this could have been considered the end of the world by some bloggers, the social Web has grown to understand that distributed conversations are taking place. By Google Reader enabling conversations to happen through their application, readers can act on the news immediately, without having to open a new window and participate there. It's also had me rethinking whether I should be self-sharing, in effect sharing my own posts when they get into Reader. I've personally tried to share only a subset of what I consider the best, but now that I have seen people engage right from within the app, it makes me think I should just share them all and enable the comments to take place where my readers are comfortable.

Now, every time I log into Google Reader, not only do I see new feed items to read, but I see new follower requests looking to see the shared link blog - and also, in bold, a "Comment View" which takes me to see all the comments, not just on items that I have shared, but on items shared by people whose shares that I follow. Google Reader, in a matter of months, has become a very serious part of the conversation. In light of the uncertainty around FriendFeed and how that company will integrate with Facebook, I am betting that some people are looking back at their RSS reader for information consumption and now, social discussion.

So go ahead, comment on my items in Google Reader. I don't need all the comments here. To find my shared items, head to: http://www.google.com/reader/shared/louisgray, and let's get connected.

Google Reader "Likes" Find the More Shy Blog Readers

Since Google Reader introduced new social aspects to their popular RSS reader last Wednesday, there have been a number of reactions to the additions - most specifically around their introduction of a "like" feature, enabling readers to essentially give a "thumbs up" to an article, as they can on FriendFeed, Facebook, Socialmedian and other networks. But those people who are claiming the exposed likes are cluttering the interface are missing the point completely. The likes functionality not only is a lightweight way to flag a story of interest, but it's a tremendous way to help blog authors and readers find others who may have been keeping a lower profile - those who don't also blog and link your way, and those who don't visit the site to leave comments.

Every single blog post that flows through Google Reader now has the option to be shared or liked. And if a post is liked by somebody, Google Reader shows how many people have liked it across the network. Clicking on the number, such as "4 people liked this" exposes who liked it and a quick mouse over any of the names presents you with a short summary from their Google Profile. So not only can I take pleasure in the fact that people I already know are reading and liking some of the same articles I am, but I am finding new people who share similar interests, and finally cracking the mystery of who actually reads my blog.

I didn't know Hannah read my blog!

Jeff's a local guy - sounds cool...

And Kris knows Digital Syndication and RSS! Awesome.
It's well known that a small percentage of content consumers take action on the content, aside from passively reading it. And as the social Web has evolved, the options to respond to posts have diversified. In the last few years specifically, we have seen a reduction in linking from blogs to other blogs, and a move away from comments on the initial site and more to aggregation services like FriendFeed and Facebook, or even away from comments altogether, instead to ReTweeting - essentially the act of forwarding links to your social connections on Twitter.


Google Reader Is Seeing a Boom In Connections Over the Last Week
The comment has also evolved to include sharing and liking. I act as an information filter to the hundreds of people who read my shared items blog and in turn hundreds of people's shared items blog come my way. And following FriendFeed's lead, as Rob Diana pointed out, the advent of likes makes flagging an article as simple as clicking the "like" option, a move Google Reader has now followed. This lightweight option means that the quiet multitude of readers who to date has not chosen to leave me a comment on the blog just might find a like more palatable - helping me learn who they are, and, assuming their Google Profile is complete, find out where else they are active.

If the argument against likes is simply an issue with the user interface, that's fine. UI is relatively "easy" to alter and improve. But if the argument is to eliminate this new way of interacting with content, then that is certainly a losing battle. You cannot force readers to do what you want them to on your terms, and the more flexible programs are in terms of letting content consumers take action, the more likely it is that more of them will. I am enjoying checking out the likes on my Google Reader items and finding new people I really should know better - even if they are shy.