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

Blogging

Why's it called Syndication?

Joffrey Koliante asked…

I keep asking myself what does “syndicate” mean. I would say that Syndicators are systems that make any content available as an XML feed. When syndicators syndicate content, this is called syndication.

Right ?

So why do so many blogs, especially Movable Type powered ones, write “Syndicate this site” rather than “Aggregate this site?”

The short answer is: because the original use for XML content feeds was truly syndication and the term stuck.

RSS was first used by Netscape in their My Netscape portal. Content providers would syndicate their headlines to Netscape using RSS, a file format that they invented. The acronym meant “Rich Site Summary.” When RSS began being used by individuals to grab content from multiple locations for display in an aggregator, the term “Rich Site Summary started to become less and less accurate. Much of the content was not summaries at all, but rather the content in its entirety. So a new meaning for the acronym was invented: “Really Simple Syndication.”

If you want the long answer instead of my oversimplification of the history of RSS, poke around the Web looking for information about Dave Winer, Netscape, and the different versions of RSS: 0.91, 0.92, 1.0 and 2.0.

One of the meanings of syndication is the distribution of content to multiple locations for simultaneous publication. So in that sense, syndication is a good term for what is occurring. However, the act of consuming the content (what the end users are doing when they “syndicate this site”) is not technically syndication.

While “aggregate this site” is probably a better description, “syndicate” is in common use and probably won’t go away anytime soon. But I’d argue that neither term is very good if you want mainstream Internet users to pick up on content feeds.

Recently Written

Your OKR Cascade is Breaking Your Strategy
Aug 1: Most companies cascade OKRs down their org chart thinking it creates alignment. Instead, it fragments strategy and marginalizes supporting teams. Here's what works better than the waterfall approach.
Your Prioritization Problem Is a Strategy Problem
Jul 23: Most teams struggle with prioritization because they're trying to optimize for everything at once. The real problem isn't having too many options—it's not having a clear strategy to choose between them. Without strategy, every decision feels equally important. With strategy, most decisions become obvious.
Behind schedule
Jul 21: Your team is 6 weeks late and still missing features. The solution isn't working harder—it's accepting that your deadlines were fake all along. Ship what you have. Cut ruthlessly. Stop letting "one more day" turn into one more month.
VC’s Future Lies In Building Winners
Jun 21: AI and megafunds are about to kill the traditional venture model, forcing smaller VCs to stop hunting for hidden gems and start rolling up their sleeves to fix broken companies instead.
Should individual people have OKRs?
May 14: A good OKR describes and measures an outcome, but it can be challenging to create an outcome-focused OKR for an individual.
10 OKR traps and how to avoid them
May 8: I’ve helped lots of teams implement OKRs or fix a broken OKR process. Here are the 10 most common problems I see, and what to do instead.
AI is Smart, But Wisdom Requires Judgement
May 3: AI can process data at lightning speed, but wisdom comes from human judgment—picking the best imperfect option when facts alone don’t point the way.
Decoding Product Leadership Titles
Mar 18: Not all product leadership titles mean what they sound like. ‘Head of Product’ can mean anything from a senior PM to a true VP. Here’s how to tell the difference.

Older...

What I'm Reading