Places

You are currently browsing the archive for the Places category.

In his comment to my last post about the sale of WQXR to WNYC (and in his own blog post here), Sean Reiser makes an important point:

One of the unique things about the QXR was it’s relationship with the Times. The Times owned QXR before the FCC regulations prohibiting newspapers ownership of a radio station were enacted. Because of this relationship, QXR’s newsroom was located in the NY Times building and news gathering resources were shared. In a precursor to newspaper reporters doing podcasts, Times columnists and arts reporters would often appear on the air doing segments.

It’s true. The Times selling WQXR seems a bit like the New Yorker dropping poetry, or GE (née RCA) closing the Rainbow Room. (Which has already happened… how many times?) To cultured veteran New Yorkers, the Times selling WQXR seems more like a partial lobotomy than a heavy heirloom being thrown off a sinking ship.

For much of the history of both, great newspapers owned great radio stations. The Times had WQXR. The Chicago Tribune had (and still has) WGN (yes, “World’s Greatest Newspaper”). The Washington Post had WTOP. (In fact, the Post got back into the radio game with Washington Post Radio, on WTOP’s legacy 50,000-watt signal at 1500 AM. That lasted from 2006-2008.). Trust me, the list is long.

The problem is, both newspapers and radio stations are suffering. Most newspapers are partially (or, in a few cases — such as this one — totally) lobotomized versions of their former selves. Commercial radio’s golden age passed decades ago. WQXR, its beloved classical format, and its staff, have been on life support for years. Most other cities have lost their legacy commercial classical stations (e.g. WFMR in Milwaukee), or lucked out to various degrees when the call letters and formats were saved by moving to lesser signals, sometimes on the market’s outskirts (e.g. WCRB in Boston). In most of the best cases classical formats were saved by moving to noncommercial channels and becomimg public radio stations. In Los Angeles, KUSC took over for KFAC (grabbing the latter’s record library) and KOGO/K-Mozart. In Raleigh, WCPE took over for WUNC and WDBS. In Washington, WETA took over for WGMS. Not all of these moves were pretty, but all of them kept classical music alive on their cities’ FM bands.

In some cases, however, “saved’ is an understatement. KUSC, for example, has a bigger signal footprint and far more to offer, than KFAC and its commercial successors did. In addition to a first-rate signal in Los Angeles, KUSC is carried on full-size stations in Palm Springs, Thousand Oaks, Santa Barbara and San Luis Obispo — giving it stong coverage of more population than any other station in Los Angeles, including the city’s substantial AM stations. KUSC also runs HD programs on the same channels, has an excellent live stream on the Web, and is highly involved in Southern California’s cultural life.

I bring that up because the substantial advantages of public radio over commercial radio — especially for classical music — are largely ignored amidst all the hand-wringing (thick with completely wrong assumptions) by those who lament the loss  — or threatened loss — of a cultural landmark such as WQXR. So I thought I’d list some of the advantages of public radio in the classical music game.

  1. No commercials. Sure, public radio has its pitches for funding, but those tend to be during fund drives rather than between every music set.
  2. More room for coverage growth. The rules for signals in the noncommercial end of the band (from 88 to 92) are far more flexible than those in the commercial band. And noncommercial signals in the commercial band (such as WQXR’s new one at 105.9) can much more easily be augmented by translators at the fringes of their coverage areas — and beyond. Commercial stations can only use translators within their coverage areas. Noncommercial stations can stick them anywhere in the whole country. If WNYC wants to be aggressive about it, you might end up hearing WQXR in Maine and Montana. (And you can bet it’ll be on the Public Radio Player, meaning you can get it wherever there’s a cell signal.)
  3. Life in a buyer’s market. Noncommercial radio stations are taking advantage of bargain prices for commercial stations. That’s what KUSC did when it bought what’s now KESC on 99.7FM in San Luis Obispo. It’s what KCLU did when it bought 1340AM in Santa Barbara.
  4. Creative and resourceful engineering. While commercial radio continues to cheap out while advertising revenues slump away, noncommercial radio is pioneering all over the place. They’re doing it with HD Radio, with webcasting (including multiple streams for many stations), with boosters and translators, with RDS — to name just a few. This is why I have no doubt that WNYC will expand WQXR’s reach even if they can’t crank up the power on the Empire State Building transmitter.
  5. Direct Listener Involvement. Commercial radio has had a huge disadvantage for the duration: its customers and its consumers are different populations. As businesses, commercial radio stations are primarily accountable to advertisers, not to listeners. Public radio is directly accoutable to its listeners, because those are also its customers. As public stations make greater use of the Web, and of the growing roster of tools available for listener engagement (including tools on the listeners’ side, such as those we are developing at ProjectVRM), this advantage over commercial radio will only grow. This means WQXR’s listeners have more more opportunity to contribute positively to the station’s growth than they ever had when it was a commercial station. (Or if, like WCRB, it lived on as a lesser commercial station.) So, if you’re a loyal WQXR listener, send a few bucks to WNYC. Tell them thanks for saving the station, and tell them what you’d like them to do with the station as well.

I could add more points (and maybe I will later), but that should suffice for now. I need to crash and then get up early for a quick round trip to northern Vermont this morning. Meanwhile, hope that helps.

Tags: , , , , , , , , , , , , , , , , , , , , , ,

nick_givotovsky

I remember talking to Nick Givotovsky the first time* at an early Internet Identity Workshop, when he pulled me aside to share some ideas, and immediately stripped my gears. The guy was as smart as they come, and articulate to an extreme equaled by few. I had to stop him every few sentences to get him to dumb it down a bit, or at least to let me catch up. Many conversations followed, in many settings. Every encounter with Nick was engaging and mind-sharpening.

We became friends, or as close as people get when they’re mutually engaged in too many projects while enjoying each other’s company, minds and hearts. I called him “Nicky G.”

Best I can recall, Nick came to nearly every IIW, plus workshops on VRM, networking and much more. He always contributed, always brought a warm smile and good sense of humor. He was serious, but didn’t take himself too seriously. A rare combination. Also notable was Nick’s mode of engagement. He was always original, often challenging, but never hostile or obstructive. And his mind was always open, always curious, always ready to step up and participate.

As I recall, the last I saw Nick was at the IIW this past May. He left a bit early to get back to his farm in Cornwall, Connecticut. I remember him talking about this old tractor he had, and how much he enjoyed operating it. He died this last Friday after falling off (what I assume is) that tractor. More of the story is here and here. (I share those links there for the record, but they are not pleasant reading.)

Nick’s last post on one of the many lists in which he participated told the story of his older brother’s death. “I think he did it astonishingly ‘right’, if such a thing can be said of dying,” Nick wrote.

Alas, Nick could hardly have died more wrong, and at just 44 years young. He leaves his wife, two kids, and many shocked and saddened friends.


*On 28 June 2020, this piece by Steve Larsen, about what in retrospect I believe was the most seminal gathering in the history of the Internet as we’ve come to know it since, revealed to me that Nick and I were both at there (in 1996), and I actually knew Nick from way back then.

Tags: , , ,

To their credit, fixing my problem has become a higher priority with Cox. A senior guy came out today, confirmed the problem (intermittent high latencies and packet losses), made some changes that adjusted voltages at the modem, and found by tracing the coax from our house to the new pole behind it that the guys who installed the pole nearly severed the coax when they did it. So he replaced that part of the line and brought the whole pole situation up closer to spec… for a few minutes.

Alas, the problem is still there. The engineer from Cox duplicated the problem on his own laptop, so he told me the ball is still in Cox’s court.

At its worst the problem is so bad, in fact, that this was as far as I got with my last ping test:

PING google.com (74.125.67.100): 56 data bytes
64 bytes from 74.125.67.100: icmp_seq=2 ttl=56 time=101.462 ms
^C
— google.com ping statistics —
9 packets transmitted, 1 packets received, 88% packet loss

The guy from Cox said my plight had been escalated, and has the attention of higher-up engineers there. He also said they’d come out to continue trouble-shooting the problem. “Probably by Thursday.”

We’ve had the problem  since June 17.

Meanwhile, I’m connecting to the Net and posting this through my Sprint datacard, just like I did last week in Maryland. Same results: good connections, adequate speeds and awful latencies:

dsearls2$ ping harvard.edu
PING harvard.edu (128.103.60.28): 56 data bytes
64 bytes from 128.103.60.28: icmp_seq=0 ttl=235 time=1395.515 ms
64 bytes from 128.103.60.28: icmp_seq=1 ttl=235 time=750.396 ms
64 bytes from 128.103.60.28: icmp_seq=2 ttl=235 time=295.272 ms
64 bytes from 128.103.60.28: icmp_seq=3 ttl=235 time=823.698 ms
64 bytes from 128.103.60.28: icmp_seq=4 ttl=235 time=1404.692 ms
64 bytes from 128.103.60.28: icmp_seq=5 ttl=235 time=1360.761 ms
64 bytes from 128.103.60.28: icmp_seq=6 ttl=235 time=803.610 ms
64 bytes from 128.103.60.28: icmp_seq=7 ttl=235 time=446.081 ms
64 bytes from 128.103.60.28: icmp_seq=8 ttl=235 time=554.643 ms
64 bytes from 128.103.60.28: icmp_seq=9 ttl=235 time=425.423 ms
^C
— harvard.edu ping statistics —
12 packets transmitted, 10 packets received, 16% packet loss

For work such as this blog post, which seems to require lots of dialog between my browser and WordPress at the server, the latencies are exasperating, because there’s so much dialog between server and client. I watch the browser status bar say “Connecting to blogs.law.harvard.edu…”, “Waiting for blogs.law.harvard.edu…” and “Transferring from blogs.law.harvard.edu…” over and over and over for a minute or more, every time I click on a button (such as “save draft” or “publish”).

So don’t expect to read much here until we finally get over this hump. Which has been in front of me since 17 June. Meanwhile I’m hoping to get back to editing in .opml soon, which should make things faster.

But I’ll need real connectivity soon, and I can only get that from Cox. (Don’t tell me about Verizon. They’re great back at my place in Boston, where I have FiOS; but here in Santa Barbara I’m too far from their central office to get more than mimimal-speed ADSL.)

The good thing is, Cox knows the problem is one they still have to solve, and they seem serious about fixing it. Eventually.

Meanwhile, for interested Cox folks, here’s how pings to Google currently go:

dsearls2$ ping google.com
PING google.com (74.125.127.100): 56 data bytes
64 bytes from 74.125.127.100: icmp_seq=0 ttl=45 time=110.803 ms
64 bytes from 74.125.127.100: icmp_seq=1 ttl=45 time=164.317 ms
64 bytes from 74.125.127.100: icmp_seq=2 ttl=45 time=204.076 ms
64 bytes from 74.125.127.100: icmp_seq=3 ttl=45 time=259.795 ms
64 bytes from 74.125.127.100: icmp_seq=4 ttl=45 time=397.490 ms
64 bytes from 74.125.127.100: icmp_seq=5 ttl=45 time=581.123 ms
64 bytes from 74.125.127.100: icmp_seq=6 ttl=45 time=506.292 ms
64 bytes from 74.125.127.100: icmp_seq=7 ttl=45 time=128.939 ms
64 bytes from 74.125.127.100: icmp_seq=8 ttl=45 time=328.000 ms
64 bytes from 74.125.127.100: icmp_seq=9 ttl=45 time=160.761 ms
64 bytes from 74.125.127.100: icmp_seq=10 ttl=45 time=176.398 ms
64 bytes from 74.125.127.100: icmp_seq=11 ttl=45 time=187.511 ms
64 bytes from 74.125.127.100: icmp_seq=12 ttl=45 time=188.291 ms
64 bytes from 74.125.127.100: icmp_seq=13 ttl=45 time=347.966 ms
64 bytes from 74.125.127.100: icmp_seq=14 ttl=45 time=285.017 ms
64 bytes from 74.125.127.100: icmp_seq=15 ttl=45 time=389.641 ms
64 bytes from 74.125.127.100: icmp_seq=16 ttl=45 time=399.993 ms
64 bytes from 74.125.127.100: icmp_seq=17 ttl=45 time=113.803 ms
64 bytes from 74.125.127.100: icmp_seq=18 ttl=45 time=153.111 ms
64 bytes from 74.125.127.100: icmp_seq=19 ttl=45 time=147.549 ms
64 bytes from 74.125.127.100: icmp_seq=20 ttl=45 time=198.597 ms
^C
— google.com ping statistics —
21 packets transmitted, 21 packets received, 0% packet loss

And here’s how they go to the nearest Cox gateway:

ping 68.6.66.1
PING 68.6.66.1 (68.6.66.1): 56 data bytes
64 bytes from 68.6.66.1: icmp_seq=0 ttl=239 time=676.134 ms
64 bytes from 68.6.66.1: icmp_seq=1 ttl=239 time=263.575 ms
64 bytes from 68.6.66.1: icmp_seq=2 ttl=239 time=429.944 ms
64 bytes from 68.6.66.1: icmp_seq=3 ttl=239 time=470.586 ms
64 bytes from 68.6.66.1: icmp_seq=4 ttl=239 time=473.553 ms
64 bytes from 68.6.66.1: icmp_seq=5 ttl=239 time=416.172 ms
64 bytes from 68.6.66.1: icmp_seq=6 ttl=239 time=489.699 ms
64 bytes from 68.6.66.1: icmp_seq=7 ttl=239 time=471.640 ms
64 bytes from 68.6.66.1: icmp_seq=8 ttl=239 time=349.825 ms
64 bytes from 68.6.66.1: icmp_seq=9 ttl=239 time=588.051 ms
64 bytes from 68.6.66.1: icmp_seq=10 ttl=239 time=606.703 ms
64 bytes from 68.6.66.1: icmp_seq=11 ttl=239 time=573.560 ms
64 bytes from 68.6.66.1: icmp_seq=12 ttl=239 time=454.920 ms
64 bytes from 68.6.66.1: icmp_seq=13 ttl=239 time=259.428 ms
^C
— 68.6.66.1 ping statistics —
14 packets transmitted, 14 packets received, 0% packet loss

And here is a traceroute to the same gateway:

traceroute to 68.6.66.1 (68.6.66.1), 64 hops max, 40 byte packets
1  10.0.2.1 (10.0.2.1)  2.376 ms  0.699 ms  0.711 ms
2  68.28.49.69 (68.28.49.69)  109.610 ms  78.637 ms  73.791 ms
3  68.28.49.91 (68.28.49.91)  84.093 ms  161.432 ms  84.844 ms
4  68.28.51.54 (68.28.51.54)  187.814 ms  166.084 ms  181.780 ms
5  68.28.55.1 (68.28.55.1)  126.050 ms  100.136 ms  239.987 ms
6  68.28.55.16 (68.28.55.16)  80.512 ms  147.347 ms  373.152 ms
7  68.28.53.69 (68.28.53.69)  121.593 ms  265.198 ms  323.666 ms
8  sl-gw10-bur-1-0-0.sprintlink.net (144.223.255.17)  331.535 ms  346.841 ms  279.394 ms
9  sl-bb20-bur-10-0-0.sprintlink.net (144.232.0.66)  397.594 ms  542.053 ms  546.655 ms
10  sl-crs1-ana-0-1-3-1.sprintlink.net (144.232.24.231)  986.040 ms  451.456 ms  630.898 ms
11  sl-st21-la-0-0-0.sprintlink.net (144.232.20.206)  726.689 ms  452.451 ms  235.828 ms
12  144.232.18.198 (144.232.18.198)  194.067 ms  295.496 ms  99.809 ms
13  64.209.108.70 (64.209.108.70)  262.008 ms  93.663 ms  114.594 ms
14  68.1.2.127 (68.1.2.127)  145.956 ms  123.435 ms  345.784 ms
15  ip68-6-66-1.sb.sd.cox.net (68.6.66.1)  346.696 ms  654.332 ms  406.933 ms

Draw (or re-draw) your own conclusions.

Maybe somebody out there in geekland can see the problem and help offer a solution. Thanks.

Tags: , , , , ,

One of the best things about living in (or just following) Santa Barbara is reading Nick Welsh’s Angry Poodle Barbeque column each week in the Independent — one of the best free newsweeklies anywhere. This week’s column, El Corazón del Perro, is a classic. One sample:

For those of us without the heart to pursue our own dream, or even the imagination to have one, Jackson provides cold reassurance. If someone so rich, so famous, and so hugely adored could wind up so agonizingly wretched, maybe the moral of the story is that one’s bliss was never meant to be followed.

This, however, isn’t just another knock on the late Jacko. It’s a column about afterdeath effects in Santa Barbara County, which was home to Jackson through his Neverland years:

This past Tuesday, a coterie of key county executives from law enforcement, public works, fire protection, public health, planning, emergency response, and communications spent the better part of the day shuttling from one emergency meeting to the next, trying to figure out what was real and what to do about it. No less than five employees of the Sheriff’s Department spent their day fielding calls from media outlets around the world. Associated Press dispatched a reporter to stake out the County Administration Building all day. By 7 p.m., Tuesday, no actual communication had taken place between county government and the Jackson camp. Instead, Sheriff’s officials relied upon contacts they have with the L.A. County Sheriff’s Department for whatever vague rumors and rumblings they could get. Somehow through this opaque and osmotic chain of communication, county officials are hoping to persuade the Jackson clan to call it off, if in fact it was they who started something in the first place.

Some in the Sheriff’s Department expressed confidence that the whole thing has been an exceptionally expensive and elaborate fire drill. Personally, I like the idea that the whole thing is a big fake-out, an angry practical joke on the county that prosecuted Jackson. When Paul McCartney’s former wife, Linda McCartney, died several years ago, I remember how rumors were strategically planted that she died in Santa Barbara County. In fact, she did not. The County Coroner complained he spent so much time fielding media calls that he couldn’t get any work done. Cadavers, he said, were piling up in his coolers like firewood. Ultimately, we would discover the whole thing was an elaborate dodge so that the McCartney clan could grieve unmolested by the paparazzi. But not before Santa Barbarans — ever willing to embrace the rich and famous, even if they never lived here — held a solemn and tearful candlelight vigil at the County Courthouse’s Sunken Gardens.

Some of the worries in the piece are stale now (a Neverland funeral appears unlikely), but it’s still a good read.

Tags: , , , , , , ,

The idea was to take some down time in Santa Barbara and get work done in my own nice office, with my nice comfortable chair, surrounded by space and time, with soft sea breezes blowing through.

Instead it’s been tech crash city since I got here last Thursday. (Except for getting out to the Live Oak Festival. That rocked. Also, trees, dirt and great music tend not to crash.)

First a system upgrade hosed a beloved old mail program. So far I can’t get the archives to migrate anywhere. I can still get email addressed to my searls.com and Gmail accounts, but not to my Harvard.edu account. I can send from Gmail. But balls are being dropped and lost all over the place.

Next my Internet connection through Cox got flaky. Mostly it’s bad. Details in my last post. A Cox repair guy finally came today. And, as Russ predicted, tightened everything up, tested it out, and all was fine. Dig this: I didn’t know that service had improved to 18Mb/s downstream and close to 4Mb/s upstream. It was right up there when he left, along with two-digit ping times to everything.

That was then. Soon as he left, we were back to bad. We’re at 3-digit ping times and packet losses. One other discovery: my 8-port Netgear Firewall/Router/Hub/Switch (I forget the name, which cannot be remembered — it demonstrates the opposite of branding) has Issues too. It introduces latencies and packet losses of its own when it’s in the loop. It’s out right now, not that it makes any difference. I’m back using my Sprint data card.

When I called Cox to get them to come back and finish the job, they said they’d send a senior tech on Friday afternoon. That’s two days from now. Then, in the middle of a tech support call with Apple, a Cox robot made an automated survey call. I couldn’t talk and hung up on it.

If you want to reach me, text or call. Or use a Twitter DM. Meanwhile, I’m going to take a shower and go for a long walk. Or vice versa.

Hope everybody’s enjoying Reboot. I really miss being there.

Tags: , ,

When we went looking for an apartment here a couple years ago, we had two primary considerations in addition to the usual ones: walking distance from a Red Line subway stop, and fiber-based Internet access. The latter is easy to spot if you know what to look for, starting with too many wires on the poles. After that you look for large loops among the wires. That means the wiring contains glass, which breaks if the loops are too small. The apartment we chose has other charms, but for me the best one is a choice between three high speed Internet services: Comcast, Verizon FiOS and RCN. Although Comcast comes via coaxial cable, it’s a HFC (hybrid fiber-coax) system, and competes fairly well against fiber all the way to the home. That’s what Verizon FiOS and RCN provide.

fiber

We chose Verizon FiOS, which gives us 20Mb symmetrical service for about $60/month. The 25 feet between the Optical Network Terminal box and my router is ironically provided by old Comcast cable TV co-ax. (Hey, if Comcast wants my business, they can beat Verizon’s offering.)

My point is that we live where we do because there is competition among Internet service providers. While I think competition could be a lot better than it is, each of those three companies still offer far more than what you’ll find pretty much everywhere in the U.S. where there is little or no competition at all.

The playing field in the skies above sidewalks is not pretty. Poles draped with six kinds of wiring (in our case electrical, phone, cable, cable, fiber, fiber — I just counted) are not attractive. At the point the poles become ugly beyond endurance, I expect that the homeowners will pay to bury the services. By the grace of local regulators, all they’ll bury will be electrical service and bundles of conduit, mostly for fiber. And they won’t bury them deep, because fiber isn’t bothered by proximity to electrical currents. In the old days (which is still today in most fiber-less places), minimum separations are required between electrical, cable and phone wiring — the latter two being copper. In Santa Barbara (our perma-home), service trenching has to be the depth of a grave to maintain those separations. There’s no fiber yet offered in Santa Barbara. At our house there the only carrier to provide “high” speed is the cable company, and it’s a fraction of what we get over fiber here near Boston.

All this comes to mind after reading D.C. Court Upholds Ban on MDU Contracts: FCC prevents new exclusive contracts and nullifies existing ones, by John Eggerton in Broadcasting & Cable.  It begins, “The U.S. Court of Appeals for the D.C. Circuit Monday upheld an FCC decision banning exclusive contracts between cable companies and the owners of apartments and other multiple-dwelling units (MDU).”

The rest of the piece is framed by the long-standing antipathy between cable and telephone companies (cable lost this one), each as providers of cable TV. For example,

Not surprisingly, Verizon praised the decision. It also saw it as a win for larger issues of access to programming:

“This ruling is a big win for millions of consumers living in apartments and condominiums who want nothing more than to enjoy the full benefits of video competition,” said Michael Glover, Verizon senior VP, deputy general counsel, in a statement. “In upholding the ban on new and existing exclusive access deals, the Court’s decision also confirms the FCC’s authority to address other barriers to more meaningful competitive choice and video competition, such as the cable companies’ refusal to provide competitors with access to regional sports programming.”

Which makes sense at a time in history when TV viewing still comprises a larger wad of demand than Internet use. This will change as more and more production, distribution and consumption moves to the Internet, and as demand increases for more Internet access by more different kinds of devices — especially mobile ones.

Already a growing percentage of my own Internet use, especially on the road, uses cellular connectivity rather than wi-fi (thanks to high charges for crappy connectivity at most hotels). Sprint is my mobile Internet provider. They have my business because they do a better job of getting me what I want: an “air card” that works on Linux and Mac laptops, and not just on Windows ones). Verizon wanted to charge me for my air card (Sprint’s was free with the deal, which was also cheaper), and AT&T’s gear messed up my laptops and didn’t work very well anyway.

In both cases — home and road — there is competition.

While I can think of many reforms I’d like to see around Internet connectivity (among citizens, regulators and regulatees), anything that fosters competition in the meantime is a Good Thing.

Tags: , , , , , , , , , , , , ,

— is All A Capella, on WERS/88.9 in Boston. Listen here. Or on the Public Radio Tuner. Or on WERS own iPhone app. Or iTunes (it’s in the list called “Public”). They just started tweeting too: @allacappella889. The performances are just freaking astonishing. You’d think they were playing instruments. And harmonies tight enough to make Manhattan Transfer envious. Awesome shit. Dig. Really.

I’ve blogged about WERS before. My mind hasn’t changed. I can’t stress too strongly how good this station is. You may not like everything on there. (It would be odd if you did.) But the quality is always good, and the goods always original.

There are original stations out there too, of course. KPIG, Radio Paradise, WIOZ, KGSR…  the list goes on. I’d continue, but I have to drive.

Tags: ,

madison-at-dawn

On the same flight that started with The Cities in darkness and ended with Chicago at sunrise, my flight glided over Madison, Wisconsin, which I shot in the dawn’s early light. The shot above leads to the whole series. I need to go back and correct the botched tags on many of them. Meanwhile, locals can fill me in on what I got right and wrong.

One of these years I’d like to actually visit Madison, on the ground. Meanwhile, this will have to do.

Tags: , , , , ,

As a kid I screwed up in many ways, but none of those ways excluded a central lesson good parents start teaching as soon as kids are capable of conversation: responsibility. The word always sounds reproachful and corrective to a kid, but it matters. It says you can be depended upon to do what is expected of you — and a bit more. Civilization itself depends on that.

The Responsibility Lesson comes to mind as I read this post by Candy Beauchamp. The stand-out section:

Many of you may know that Tom just got his degree from the University of Phoenix. He went there for 3 years and finished his last class in late April. He ended up with 3.67 GPA in Business Marketing. Not too shabby. We are very proud of him and have been eagerly awaiting actually receiving his degree….

Apparently, there’s a problem. From what we can piece together, Wells Fargo – as part of the bail out – sold his student loan to the Department of Education. This means they basically stopped his loan, but didn’t tell him or anyone else. This means that the school is looking at Tom wanting him to pay them, they are basically holding his degree for ransom.

This is inexcusible.

The story goes on, and the lessons Candy and Tom take from the experience are all good ones. What’s remains screwed up, and in need of deeper understanding, is the institutionalization of responsibility-shifting, with hardly any tracks left in the sand. This is what happened in with what Kevin Phillips calls the “financialization” of the economy. When you’re one shell in a giant shell game, it’s not hard to see what’s going on; but it’s easy to ignore the whole thing, because the system is all about moving problems, long after it stops being about moving opportunities. We’re still in the problem-moving stage of This Thing, this financial mess. That’s what Wells Fargo reportedly did in this case. Others too.

Responsibility isn’t about who’s to blame. It’s about who can act, and what they can do.

My optimistic take is that we’ll wake up and smell more than blame cooking. We’ll smell the need to take responsibility for the debts and assets that we’ve taken on. And not just in the financial sector.

Or so it seems to me on a Saturday in New York. Beautiful outside. See ya later.

jesusita_google_modis10

Where most of my earlier shots in this series were of fire detection and spread across time, the one above (and in the larger linked shot, on Flickr) is of “fire radiative power”. If you look at the whole set, you can get an idea of both intensity and spread across time. Again, these are from MODIS, which is an instrument system on satellites passing more than 700km overhead. Still, it finds stuff, and dates it. That’s why this next shot is very encouraging:

jesusita_google_modis11

It will sure spread some more, but we can see the end coming. Here’s the whole photo set.

And here’s the latest update on exactly what burned (addresses and all) from Matt Kettmann (Contact), Sam Kornell , Chris Meagher (Contact), Ben Preston (Contact), Ethan Stewart (Contact) of the Independent.

They also issue a caution:

The bad news is that the fire still threatens parts of Goleta to the west, the Painted Cave community to the north, and, to the east, parts of Santa Barbara and Montecito, where the evacuation order was just extended once again.

Those Indy folks did — and are still doing — an outstanding job, deserving of whatever rewards are coming their way. Great work by everybody else reporting on the fire as well. Kudos all around.

And great work, of course, by the firefighters. They saved the city. If you’ve ever seen a fire this big and threatening (for example, Oakland, which I did see, and which took out more than 3500 homes), you know how hard it is to stop. Around 80 homes were lost in this one. It could have been many more. If Cheltenham, or the Riviera, had gone up, and the sundowner winds kept blowing, it’s not hard to imagine losing the whole city, since the rain of flaming debris would have caused a true firestorm. From the same Indy report:

“The firefighters must have sat in every single backyard and held it off. The fire reached literally the backyards of every single one of them, but I didn’t see a single house burned up there.”

The mountains won’t be as pretty for a couple of years. But the city will also be safer. That’s the upside. 2:54pm Pacific

Here is a great map that shows all three fires in the last year, as well as good information about the ongoing Jesusita Fire.

Tags: , , , , , , , ,

« Older entries § Newer entries »