One year later, still no Mac OS X Safari support

Again, I appreciate your response. Over the years, SIMBL and APE have been controversial in the Mac community, so I've avoided installing them. But I do use a product called 1Password from Agile Web Solutions that has a similar InputManager-based extension, and it usually works well - at least until Apple upgrades Safari and breaks it. In the worst-case scenario, an out-of-sync InputManager extension can cause Safari to crash at launch, but lately the IM developers are doing a better job of checking Safari's version and unloading gracefully if the versions are incompatible.

I see some recent reports of the MIME-association problems you mentioned for WebKit plug-ins, but all of the popular plug-ins for things like Flash and Silverlight still seem to work for their MIME types. And it's my impression that WebKit plugins can interact with JS to modify the DOM for things like web content overlays, but I don't know enough about the Azigo reminder window to know if that is the right way.

A friend who is developing a Cocoa app with embedded WebViews mentioned recently that there was a problem for developers where extensions failed to load or execute in debug mode, and the solution was to turn off debugging.

Of course, the typical Safari user doesn't care about the details of the internal plumbing. We just want to use our preferred browser with systems like Azigo. The suggestion to "upgrade to Firefox" doesn't sit well with many of us. Obviously, it's an attempt to spin the problem. Instead, the developers can upgrade their Apple developer account and work with their engineers to find a proper long-term solution. In this case, it is a justifiable expense.

The bottom line is that Azigo has to work with Safari, or it will fail to become the industry's preferred identity solution. I'll sign off for now, with the hope that Azigo will be working on Safari in the near future. Thanks again for listening.