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.

News and Commentary

AOL IM BS

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

washingtonpost.com | Instant Messaging: Tear Down the Walls: "[AOL] consistently says [third-party AIM client] applications compromise the security of AOL’s own network by storing users' screen names and passwords beyond AOL’s control. That, however, doesn’t explain why the company still allows users of the long-defunct program Claris Emailer to retrieve their AOL mail remotely. Nor has AOL blocked every third-party IM program: Users of Odigo Inc.’s software have been able to access AOL’s network."

AOL also has two different IM proptocols. One is called OSCAR and is the one that the official AIM clients use. The other is TOC and is the protocol that AIM has opened up to allow FCC-mandated interoperability.

Clients that use the TOC protocol store the AOL screen name and password just like those that use OSCAR, but I don’t hear AOL saying that is a security risk. In fact, they designed it that way.

So why don’t third-party clients use TOC instead of butting heads with AOL over OSCAR? TOC is outdated and bug-ridden. It doesn’t support newer instant messaging features like file transfer, or even basic features like online status.

AOL doesn’t want third party apps connecting to AIM for a simple reason. If I can communicate with my AIM contacts without using AOL software, there is one less reason to use AOL. And there is one less thing that the vast AOL-TW empire has control over.

So next time you hear people discussing a company with dominant market share that is using predatory practices to prop up market share for another software package and squash competition, remember that they might not be talking about Microsoft.

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