ChumpBot

(originally posted at bigbadgeek.com)

I found this tasty Google-culture morsel from the #joiito chump bot. It sits in the chan, listens for URLs and blogs them for later perusal via XML feed.

Apparently the bot also allows IRC users in the channel to post comments on the link which are reflected on the blog. Neat.

RSS Feeds A'Comin'

(originally posted at bigbadgeek.com)

Tonight I headed over to DailyRotation and picked up the rest of the news feeds I'd been missing since I switched to using NetNewsWire Lite as my aggregator.

They're organized into the following categories: Apple, Development, Devices, Group Blogs, Personal Blogs, Technology News. I've got 70 feeds total for my own futuristic Personal Newspaper.

I figure eventually I'll head over to BlogRolling and sign up for an account. I'll split my Personal Blog list up into people I actually know and the online personalities I merely keep tabs on.

In other news, I heard from Nora today and she's back in NYC and getting ready for school - which is a relief. Also; Friendster mysteriously started working with Safari today. I haven't gotten an email back from the team, but I suppose whatever was broken is now fixed. Hooray!

Bug Report to Friendster

(originally posted at bigbadgeek.com)

Yesterday I finally got around to submitting a bug report to Friendster for their incompatibility with Apple's Safari browser.

It's not a difficult problem, either. The Safari browser has a security mechanism that disallows a page to automatically redirect to a page that redirects back to the first page - which, apparently, is a method that Friendster utilizes for their login script. There are certainly ways around this.

I was pleased with the quick response from the Friendster team - not quick enough to be an automatic kickback, but definitely a scripted response of some sort. Anyway, it's the thought that counts. We'll see if they get it fixed. I'm sure they'll be glad to be getting a bug report that's unrelated to their database issues for a change.

FCC Feels Bad for AOL

(originally posted at bigbadgeek.com)

Awww, merger didn't turn out to be as good as you all hoped? Here, we'll lift some of the merger restrictions for you... no hard feelings?

I see this as a mixed blessing. AOL was supposed to work towards interoperability with the other major IM networks (Yahoo!, MSN, ICQ.. err wait, they own that one) before they were allowed to implement video chat capabilities to their AIM client. That was a stipulation of the AOL/TW merger. Fact.

Now, AOL sneakily got around the video chat ban by allowing Apple to license and use their network with Apple's iChat AV client. But let's face it, Apple's hardly a market, hardly a demographic. Since it was Apple's client and not AOL's that was implementing the video conferencing feature, the FCC didn't really notice or care.

Fast-forward a few months and Apple's iChat AV is a hit, people love it, it gets rave reviews from the Wird's and C|Net's of the world, and AOL sees an opportunity to poke and prod the FCC and see if they can get the restriction dropped. "Woe is me," cries AOL, "we're losing customers because we can't get our act together." A few days later the FCC votes to drop the restriction.

Back to the mixed blessings bit - this shows what everyone knew to already be true: the FCC are a bunch of wimps. On the plus side, I'm betting that Apple will actually help AOL to implement standards-based voice and video chat to make it interoperable with Apple's iChat AV client. It would be disasterous for Apple to have its user base cut off from the rest of the AIM network for voice and video. At the same time it's an opportunity for Apple to show off how much more advanced their iChat AV client and iSight webcam really are. Win-win for Apple.

Will be interesting to see how this plays out.