Mike O’Connor

I just posted a story over at the St Paul Broadband Committee site about my belief that a lot of the municipal WiFi networks don’t seem to be grounded in financial reality.

Here’s a link to the article and here’s a link to the muni-WiFi financial model I built to go with it.

Here’s the deal — let’s get these models out of the hands of the VooDoo consulting expert type people and into the hands of the people. “Open source financial modeling” if you will. Let’s beat on this model — or write a new one if this one is hopeless — and get to the point where we ALL understand the economics that underpin these projects.

That way, we can either rejoice in bridging the digital divide, solving the problems of the world and putting a chicken in every pot (as advocates claim) or we can avoid the mess that comes with yet another technology project that over-promises and under-delivers.

What say you? Let’s have at it.

Sure, they’ve been around forever. Sure, most of you probably already know about this site. But just in case you don’t, here’s a pointer to GetHuman.com — a great site if you’re trying to get to a human-being customer-service type person.

Marcie was trying to find the path through Northwest Airline’s patented “Voice Prompts From Hell” system to book a seat for me on an existing reservation. She finally gave up. I remembered reading about GetHuman somewhere, Googled it, looked up NWA and tried it out. Tarnation! Worked perfectly.

I’m sold. It’s even got the incredibly-secret path to Amazon customer-service reps!

Huh. Full-circle time. I’ve been working on the St Paul Broadband Advisory Committee for the last few months and put up a web page to help us do our work. Click on that link to check it out.

Better yet, register for the site and help us out!

This is the scratchpad I’m going to use to keep notes to myself as I migrate Sex and Podcasting from Xoops to Word Press on my IIS server (Win2003). This is extreme geekness, not good reading unless you’re trying to do the same thing.

Read on for the geek stuff… [read more…]

I've been puzzling about the problem that BlogTorrant solves for quite a while.

Namely — how can I make it easy to put BitTorrant versions of big files (like my Sex and Podcasting podcasts) up on my sites.

These sites of mine are built on Xoops, a very nifty, very flexible open-source content management system that can do all kinda cool stuff. But blogging isn't it's strong suit — not terrible, but it's a little clunky at things like track-backs, RSS, etc.

I solved the “how do I do enclosures?” problem by using FeedBurner to generate the RSS feeds that you're seeing — one of the nice things about that system is way it auto-magically does all the enclosure stuff for podcasting.

This BlogTorrant gizmo looks like it might be the add-on that will make it easy to do BitTorrants in the Xoops environment — I will do some tinkering and update this post with a cookbook if things work out.

Ah. A completely satisfactory geek experience. Now that I've rassled most of the basic podcasting stuff into shape, I wanted to move on to doing interviews and conference calls and recording them — Ralph pointed out that Skype was the way to go.

Doug Kaye (the maestro of IT Conversations) put together this definitive post on how to record Skype calls. There are other ways, but this is definitely the industrial-strength approach.

I'm going to start doing “conversation” podcasts, but before that I'm going to use this to record an interview for a consulting project I'm working on — tomorrow. I have a little rant n'record that's going up on Sex and Podcasting about how you could use podcasting as an organizing tool for work (the show will go up in a day or two).

Safe Haven's not getting much attention these days because I'm still getting my sea legs with the podcasting stuff. Sex and Podcasting is gonna be getting a new post a day, at least for the next week.

But I ran into a cool thought while listening to The Gilmore Gang yesterday (what happened to them by the way — a great series of podcasts that seem to have trickled off to nothing back in February).

Here's the idea — why not use RSS on a manufacturing shop floor to let machines and work-centers tell each other (and us) what they're up to. Machines could “subscribe” to upstream machines, and “publish” for downstream machines and let each other know what's going on — feeds could talk about what came into (and left) the machine/work-center.

I spoze this could be expanded to anything that has stuff moving through stages — paperwork processes, hospitals, etc. All kinds of real-time applications come to mind.

One thing that would be neat is that we'd get away from the huge central database notion and so adding a workcenter, or rearranging them, would be easy. Simply a matter of changing who subscribed to what. Sortof an object-oriented model that us regular people could understand…

It could be really visual too — lots of cool UI possibilities there. Not to mention fitting in better with the notion of lean manufacturing, and visual management.

Now, back to podcasting.

I’m late into the game — podcasting’s 5 months old, but I’m there now.

This blog has been neglected for the last couple weeks while I’ve been getting things pulled together, but I’m there now and this is an entry to record what I’ve learned. It’s going to be another really long one, so I’ll put topic headers and keywords (for Google) “above the fold” and leave the gory details for the “read more” section…

Sex and Podcasting — what it’s about, why I’m doing it, why I transmogrified Lorenzo’s “Sex and Broadcasting” book title into my site’s name, plus some of the interesting current developments in the podcast world like Adam Curry’s Podshow.com.

Licensing — I’m going to play RIAA licensed music. At least I think so… This section is where I’ll explore the differences between ASCAP/BMI performance rights licenses, Harry Fox Agency mechanical rights licenses and SoundExchange federal copyright licenses and how I’ve decided to proceed — the short version is; I’ve got a BMI license for the performance rights, and will work with Harry Fox on mechanical rights when they decide what to do.

Equipment — hardware/software plus construction. I got a couple cool new toys — some nice mics plus a really neat Marantz PMD660 digital recorder (which i wound up getting in preference to the Edirol R1).

To learn more… [read more…]

Steve and Ralph and I had a little chat in the “comments” section of the video-conferencing post that went up a few weeks back, which got me thinking this morning…

Since I imagine most of the folks who are reading this blog are Beer Gang members-in-good-standing, I was wondering if you'd be interested in having a conferencing area on the site so you could talk to each other directly. It's easy (a couple mouse-clicks) to put up, if you think it's a good idea.

One of the dreams I’ve always had (from reading too much science fiction, no doubt) is to be able to do point to point video phone calls with folks. I was an early fan of ICQ — which back in the olden days was one of the very first video-calling applications.

I’ve always been disappointed with the results. The early cameras were crummy, bandwidth limitations resulted in choppy pictures with huge latency and the sound-portion of the call was always a nightmare.

It had been a few years since I’d messed around with the stuff, so when my buddy Bill Coleman asked, I took the opportunity to do a geek project and see how things work these days. This is a “notes to myself” post in case I have to retrace my steps some day.

The big breakthrough was to use Skype for the audio portion of the call. It’s pretty easy to get the video portion of the call up and running with MSN Messenger (and presumably AIM and Yahoo Messenger as well). But getting the audio to work has always been way too hard for me to suggest to “normal people” because of all the firewall and routing issues. Skype neatly solves that problem and we judged our Saturday Geek project “pretty cool” and a big success.

Good things

- It’s pretty cheap. For Bill and me, who both already have broadband Internet access and computers and like that, the only out of pocket cost is the $50 we spent on our spiffy little Logitech cameras. The instant-messaging client (MSN Messenger is what we used) and Skype are both free.

- Quality is good — especially the audio. Skype has got the kinks worked out of their stuff, so the audio portion of the call was smooth as silk. And the video works pretty darn good too. A little fiddling (mostly with the video “size” setting once the video portion was up) and we got the audio and video latency (geek talk for “delay”) pretty well lined up with each other so the lips moved when the sound arrived.

- It’s pretty easy, and thus a rewarding project and a lot more fun than all this stuff used to be.

- It will work for people at work. That’s a really big deal for Bill, because he wants to use this to keep in touch with his clients, who tend to be scattered all over the landscape. See the Cookbook for the tech details, but I think this rig will work with no firewall changes (except for the firewall on your PC) and thus won’t give security-people heartburn.

“Read more” to get to the Video Cookbook… [read more…]

Julio’s been writing about podcasting for (seemingly) ever — and i didn’t read any of the posts until today when he pointed folks at this great 4 Minutes About Podcasting movie.

NOW I get it!

Amazing — all of the “tell your own story” ethic of community radio, combined with all the cool “build your own feed” capability of RSS feeds, which results in “radio” that’s going to show up in Google.. If you’re a community-radio type person who hasn’t messed around with podcasting, go watch that movie — and then let your imagination run wild. I’m sitting here thunderstruck, realizing what the possibilities are…

What an amazing community technology. For example; you’re an organizer of (fill in the blank), laboring away in your local community. Wouldn’t it be cool to be able to hear an occasional “show” about your cause, direct from the mouth of your inspirational mentor? If you’re an inspirational-mentor type person, wouldn’t it be great to periodically share your “show” with others?

Or, if you’re more like the typical community-radio programmer, wouldn’t it be great to reach the .0003% of the population of the planet who shares your passion about (fill in the blank)? Conversely, wouldn’t it be great to listen to shows produced by people who exactly share your tastes and views?

Mama, don’t let your babies grow up to be broadcasters. Their days of being in any way relevant are numbered.

This one totally nifty technology. Thanks Julio for pointing me at the link that finally turned the light bulb on. I’m going to add useful links “below the fold” as I explore — to see that stuff, hit the “read more” button.

Bandwidth — A puzzler

The community radio movement was all about access to limited bandwidth (in our case, noncommercial FM channels). Podcasting is going to present an interesting bandwidth problem for the person with a really popular podcast — it’s going to slurp up a lot of bandwidth to deliver a 50 mByte file to thousands (millions?) of fans that are hungry for your stuff. Looks to me like we’ll need to marry BitTorrent with podcasting pretty soon now.

I’m really interested in the “how do you do it?” part of podcasting right now, so that’s what this first collection of links reflects.

Engadget provided a great starting point on this page about podcasting.

Creating podcasts is pretty straightforward — make a radio show, but pipe it off to an MP3 file when you’re done. I was Googling for “make a podcast” and got zillions of articles about how to make digital radio shows — lots of talk about mixers, and line-inputs-to-the-computer, and like that.

What I’m interested in right now is the RSS feed part — and the very last part of that Engaget article is what tipped me over to understanding. It all revolves around the notion of an “enclosure” in an RSS feed — something that most blog-creating software doesn’t grok yet, but I bet all off them will soon.

I think for now I’ll try just editing up my own RSS feed by hand rather than trying to force-feed Xoops (the software I’m using to create this blog). I’m going to use the XML file in the Engadget article as a template, build me a little “hello world” podcast and see how I do. But not right away. First I gotta finish helping Marcie lay down flooring in the upstairs room at the farm.

This is the latest geek project — reclaiming Robert’s old PC and transmogrifying it into a personal video recorder (PVR for short) with a Hauppauge PVR 350 and SageTV software.

Sure, I could have gone out and bought a Tivo or ReplayTV for about the same (or maybe a little less) money. But I see several advantages to doing it myself;

[read more…]

The Annual O’Connor Christmas Day Christmas Party always produces a few really interesting conversations. This year I talked to an old friend (who will remain anonymous - you’ll see why in a minute) about using blogs as a way for people to talk to each other without revealing their identity.

This kind of thing has been happening on the Internet ever since the beginning, but public blog site (like Blog Spot) make it MUCH easier for “normal people” to set up an anonymous space than most of the preceding tools.

So natcherly, this morning the New York Times runs a story about an anonymous blog. Pretty darn handy. The story on the Times site is about Anonymous Lawyer, a fictional web site about life in a Big Law law-firm. A great example of an anonymous site, run on a public blog service.

In this case, eventually you find out the identity of the author of the site, but only because he allows that to happen. I imagine there are lots of blogs out there where it would be very hard to figure out the real identity of the person posting.

Another possibility would be to set up a “private group” on Yahoo Groups. That would tend to keep your posts off the search engines — a drawback to Blog Spot is that most of their blogs get sucked into the search engines (I’m not sure whether you can make a Blog Spot blog “private”).

If you have a finite group of people in the group, you could all share the same user-name and password when posting to your blog/group and thus add another layer of anonymity to the conversations.

Marcie’s blog is an example of a site where identity is consciously “managed” within narrow limits. She’s very careful not to reveal the location of our farm, because she doesn’t want people to come visiting unannounced. For a long time, you also wouldn’t have been able to get in touch with Marcie except through the blog, although we recently changed that.

So — if you’re an organizer looking for a place where identity can be masked in order to have candid discussions, consider a blog on a public server.

I'm heading into a big project, and as part of preparing for it I revisited the site I maintained while participating in the Y2k preparations for my home town of St Paul, MN.

Just about every single Y2k link on that site is busted now, although one is selling some strange kind of medical nostrum that's not likely to live up to it's claims of Improving My Life In Every Way.

But one of the links led me to the new site run by Peter de Jager. For those of you who don't remember, Peter was considered by many to be the person who first voiced the Y2k problem in terms that were compelling enough to get people off the dime. Opinions vary — some think Peter was a nutcase, sounding the alarm for a non-problem — and I agree, Peter got a little shrill at times. But I also think he's a very good thinker and did us all a great service by sticking to his guns.

I'm glad to see that Peter is still thinking, writing and active. I recommend his publications pages if you are interested in large-scale change management projects (like I am).

Here's my daily dose of rants and puzzlements. Today's revolves around the recently-announced wireless project in Philadelphia. Like lots of folks, I'm hoping they'll make it go. Like lots of folks, I can't quite figure out how they're going to make the numbers work. Here's why.

Get an envelope out, we gonna do some figuring on the back of it. Let's see here, the Philly folks say they're going to light up the whole town for free Internet access. Ok, great. Presume all the geek problems away and let's say they get it lit. Now, if they really finally run with “free” they've basically replaced all the ISPs in town. Well, maybe that's ok. After all maybe this is an amenity that cities should do, like roads and sewers and stuff. Here's where the numbers get hard…

If residential Internet access is free, then most everybody will switch to it. Some significant percentage of 1,000,000 households. First “numbers” problem — how much is upstream access for all those folks going to cost??

Get your envelope out. Let's say we give everybody up to 3 mBits (kinda like cable). And let's assume that people aren't all going to use it at the same time. That's called “oversubscription” and everybody does it - ISPs, phone companies, you name it. What oversubscription ratio? For the sake of the envelope, say 30-times. So for every megabit of upstream access, we can sell 30 mBits of “downstream” or customer access. Or 10 customers (remember? 3 mBits/customer). So for every 10 customers, we need another megabit of upstream access for those peak times (after supper).

If most of our 1,000,000 households switch to our free service, we gonna need a *lot* of upstream access. Let's say 20% of the households sign up. 200,000 customers means we have to buy 20,000 MBits of upstream access. 20 GigaBits! Wow! A T1 line is 1.5 MBits, so that would be 13,000 T1's. That a lot. Ok, Internet access is overbuilt and getting really cheap, so maybe they've got a really good deal. Maybe $10/month per MBit (that's cheaper than anything I've heard of, but hey, benefit of the doubt that's my motto…). $200,000/month for upstream. $2,400,000 a year of taxpayer money…

Once the customers have signed up for Internet, any time anything goes wrong with their computer that they can't understand, who they gonna call? The ISP, that's who. So now Philly's got to provide help-desk support for 200,000 customers. Let's say each customer calls once a year with a hard question that takes an hour to answer. 200,000 hours a year. People work 2000 hours a year, so that's 100 people answering help-desk calls at, say $50,000/year. Hmm, $5,000,000/year…

See where this is heading? I could run through all the rest of the stuff that an ISP does — network maintenance, upgrades, fixing people's connections, paying the bills, etc. Roll all that up in a ball and it looks to me like you've got at least $10-15 million/year to keep it running.

On the one hand, that's a lot of money. On the other hand, compared to losing money on ballparks and stadiums and roads and sewers and economic incentives for people to move in, maybe it's not. I'd love to see the numbers for that project.