Need someone to lead product management at your software company? I build high-craft software and the teams that build it. I'm looking for my next opportunity. Check out my resume and get in touch.

This is the blog of Adam Kalsey. Unusual depth and complexity. Rich, full body with a hint of nutty earthiness.

Content Republication

Freshness Warning
This blog post is over 18 years old. It's possible that the information you read below isn't current and the links no longer work.

I’m trying to decide how I feel about this. There’s several sites that are pulling my feed and republishing my content. Most of the time they’re doing it with attribution, as Technology Voices is. Sometimes not. Generally, they’re wrapping my content (and that of others) in advertising. Never have they sought permission.

Almost two years ago I explored this same problem when someone asked for Bloglines to stop tracking their feed.

The question is where do we draw the line? Is reading the feed in a reader like FeedDemon a commercial use? I had to buy a copy. What about an aggregated list of posts on a site? Mt-Plugins.org used to have the latest posts from a number of plugin authors (including me) on their site. Would this be an acceptable use? Syndic8 publishes a list of random feed items as RSS. Is that okay? Would your answer change if Syndic8 started selling ads in that feed? There are a number of services that will send you feed contents by email. If I subscribed to [a] feed with such a service and had those emails go to my Gmail address, is that a commercial use of his content and who is responsible for it?

I could move to partial posts, but that’s going to damage me as much as it damages content republishers.

I see RSS as a way to build mindshare. It’s a way to make my site more popular, thus improving my authority and increasing the amount of display advertising I can sell. Because I publish the full content of every blog post for free with no ads attached, I make money. My content is read by others. It’s quoted, excerpted, linked to, and remixed. That makes my blog more popular and results in more visitors, often to old archived pages. This October I had 75,000 unique visitors per day to a five-year-old blog post about jack-o-lanterns. This wouldn’t have happened if I my blog was an obscure site. RSS is the reason that I’m not an obscure site.

I could go to republishers and ask them to remove my feed. But is that what I really want? Because of them, my words are reaching a new audience. On the other hand, it feels like they’re stealing my work.

What are my other options? I could try and add advertising to my feed in a way that only shows up on republisher sites. It shouldn’t be that hard to do. Just add the JavaScript code of an Adsense block to my feed. Feed readers strip Javascript and wouldn’t show it. I’m betting that these scrape sites would allow the Javascipt and thus my ads would show.

I could use that same idea to be a bit more malicious. I could insert an XSS attack into my feed. A small amount of script could spawn new windows, click links, or rewrite much of the page. If I were to insert a bit of script that found an clicked an AdSense link on the page, there would be 100% click through on their ads. That would probably make Google suspicious enough to kick their account. I could even ensure that anyone viewing the entry would be redirected to the original blog entry on my site. And these attacks wouldn’t affect feed readers.

There’s a number of feed readers that have public views—lots of people have public Gregarius installations, and Rojo has copies of my feed—but those somehow feel different than a company simply republishing my entire feed.

When a feed reader republishes my content, it’s because person who reads my feed decided to add it to that reader. The public republication of the feed is a byproduct of that. The nature of feed readers means that there are prominent links to the original and the attribution is very clear.

When a site like Technology Voices republishes my feed, the articles that appear there look and feel more like a magazine. The attribution and link to my blog are part of a byline. Bylines tend to be overlooked when people are reading articles on the web. There’s a bevy of "bookmark this" links to various bookmarking and social news tools—all of which point to the article on Technology Voices instead of on my site. There’s comments and inbound link counts—again all on the Technology Voices site instead of pointing to those facilities on my blog.

The copyright statement in my feed reads (emphasis added), "Copyright 2006 Adam Kalsey. Permission granted for non-commercial use. Republication is prohibited." That statement in the feed is not likely ever actually read by content republishers or anyone else for that matter. Tools that consume feeds rarely show anything but feed title, description, and the feed items.

Even if the feed republishers bothered to read my copyright statement and abide by it, I’m starting to wonder if that’s something I want. If the value of my feed is that I am widely read, then pushing my content out to the edge is likely to increase that value. Where do I draw the line?

The more I think about the problem, the more I’ve come to realize what part of republishing is bothering me. The sites that I don’t like are the ones that make my content look like their own. To the casual observer, it appears that I’m a columnist for Technology Voices. If you’re building a content aggregator, this is what you need to avoid. It needs to be clear and obvious that the content is pulled in from elsewhere. If you want my words looking like a column on your site, then you need to pay me for them.

The solution I’ll try for a bit is to insert some script that shows an ad and a prominent link back to my site. I’ll implement it in such a way that feed readers won’t show it but most republishers will.

Recently Written

Think Systems, not Symptoms
Dec 15: Piecemeal process creation frustrates teams and slows work. Stop patching problems and start solving systems. Adopting a systems thinking approach helps you design processes that are efficient, aligned with goals, and truly add value.
Your Policies Aren’t Your Culture
Dec 13: Policies guide behavior, but culture is the lived norms and values of your team. Policies reflect culture -- they don’t define it. Netflix’s parental leave shift didn’t change its culture of freedom and responsibility. It clarified how to live it.
Lighten Your Process Burden
Dec 7: Everyone hates oppressive processes, but somehow we keep managing to create them.
Product Add-Ons Are An Expansion Myth
Dec 1: Add-ons can enhance your product’s appeal but won’t drive significant market growth. To expand your customer base, focus on developing standalone products.
Protecting your Product Soul when the Same Product meets New People.
Nov 23: Expand into new markets while preserving your product’s core value. Discover how to adapt and grow without losing your product’s soul.
Building the Next Big Thing: A Framework for Your Second Product
Nov 19: You need a first product sooner than you think. Here's a framework for helping you identify a winner.
A Framework for Scaling product teams
Oct 9: The people, processes, and systems that make up a product organization change radically as you go through the stages of a company. This framework will guide that scaling.
My Networked Webcam Setup
Sep 25: A writeup of my network-powered conference call camera setup.

Older...

What I'm Reading