Recently I’ve been spending a fair amount of my work time working on WebISO (Web Initial Sign-on) and portal integration, specifically Pubcookie, which we’ve adopted as part of the NMI R3 recommendations, and uPortal [#4 in InfoWorld’s Top 100 IT Projects of 2003] integration (my preferred portal framework).

Unfortunately, previous Pubcookie integration efforts have stalled out, buton the bright side, uPortal’s security framework looks pretty adaptable…

Here’s a great quote:

Middleware is the intersection of what the Network Engineers and the Application Programmers don’t want to do.

My Treo 600 finally got in yesterday. It feels amazingly tiny (good in the hands) and the keyboard is squished, but fairly usable. More review stuff later. Interestingly enough, although it feels much smaller, it’s actually not too much smaller than my co-worker’s Treo 300. Here are the dimensions as compared to my Sidekick:

Treo and Sidekick side-by-side

Treo and Sidekick stacked up

Kevin Werbach made some observations on the size in his recent article in The Feature: The Triumph of Good Enough.

Hmm, so this is pretty interesting behavior. Been noticing that AIM’s been giving me a system message that I’m signed on in different locations instead of kicking me off when I log in from multiple systems. It doesn’t have a jabber-like presence, but instead duplexes all incoming messages. Wackiness.

Ahh: AIM: Instant Message Routing

When you are signed in more than once, messages sent to you will be
delivered to all locations. You can control which locations will
receive messages by setting your Away Message.

When signed into multiple locations:

  • Your messages will generally be delivered to all locations not set as Away (or locations that have gone Idle).
     
  • If all locations are set Away, then messages will be delivered to all locations.

Please note, that you will only receive these notifications from the screen name AOL System Msg.

Was randomly clicking through the Blogger site (finding the date created link Andy sent me a while ago) and saw suggestions on what to do when your mom finds out about your blog (also, less tongue in cheeck, how not to get fired because of your blog) in the knowledge base.

Good suggestions, but it also highlights the need for more fine grained publishing control (Towards Semi-Permeable Blogging), and (ideally), a concurrent wide adoption of some sort of federated trust infrastructure [this could help to alleviate the comment spam problem. implemented properly, this could retain privacy fairly well, pseudonymity is all that’s required])