Adam Kalsey

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

18 Feb 2002

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

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