Katrina’s real name: global warming

Katrina’s real name: global warming:
Xeni Jardin:
Snip from Boston Globe story by Ross Gelbspan:

Although Katrina began as a relatively small hurricane that glanced off south Florida, it was supercharged with extraordinary intensity by the relatively blistering sea surface temperatures in the Gulf of Mexico. The consequences are as heartbreaking as they are terrifying.

Unfortunately, very few people in America know the real name of Hurricane Katrina because the coal and oil industries have spent millions of dollars to keep the public in doubt about the issue.

The reason is simple: To allow the climate to stabilize requires humanity to cut its use of coal and oil by 70 percent. That, of course, threatens the survival of one of the largest commercial enterprises in history.

In 1995, public utility hearings in Minnesota found that the coal industry had paid more than $1 million to four scientists who were public dissenters on global warming. And ExxonMobil has spent more than $13 million since 1998 on an anti-global warming public relations and lobbying campaign. In 2000, big oil and big coal scored their biggest electoral victory yet when President George W. Bush was elected president — and subsequently took suggestions from the industry for his climate and energy policies.

As the pace of climate change accelerates, many researchers fear we have already entered a period of irreversible runaway climate change.

Against this background, the ignorance of the American public about global warming stands out as an indictment of the US media.

Link (thanks, Bruce Sterling)

A related item, from a 2001 National Geographic story:

[T]he North Atlantic, Caribbean, and Gulf of Mexico regions can expect increased hurricane activity in the next 10 to 40 years. The number of major hurricanes has more than doubled in the last six years. The increase is part of a long-term climate shift that is likely to persist for several decades (…)

Link (Thanks, Ole Eichhorn)

AppleCare

It’s been almost a year since I got my PowerBook, so I went and bought the AppleCare. I’ll probably keep this computer until the second generation x86 PB’s come out, which should probably be at least 1 to 2 years from now.

I’m going to max out the RAM to 2GB, coz this machine actually feels kindda slow the way I use it. I guess Photoshop CS needs more than 768MB. ๐Ÿ™‚

condo

Tonight I signed a lease for a condo, I brought Sherry and Fee-Fee with me, this place is brand new, I liked it when I first saw it last Saturday, and Sherry loved it too. Moving in on the weekend of 9/17. ๐Ÿ™‚

It’s located near Rivermark, a new development in Santa Clara. It’s about 3 miles from Atheros‘ office, I might get a Vespa to drive to work…. I’ve always wanted one… ๐Ÿ™‚

the connection at my hotel Part 2

The Internet connection here didn’t improve much even at after midnight, so it wasn’t the peak hour traffic that was a problem… I called LodgeNet and the guy had no clue and told me he would work on it. I was tired anyway so I went to sleep. Woke up this morning , same thing. Called them again, and I connected my PowerBook to the ethernet directly just so he could ping it. Turn out the Airport Express was the problem. So I thanked him and opened up Airport Admin Util, and I noticed the Airport Express itself has a 10.10 IP address, the hotel DHCP server also assigns 10.10 address, so that didn’t look right. So I pretty much enabled the Distribute IP addresses feature in the Airport Express, which basically turns on its DHCP server, and I had it distribute 198.168 address… rebooted the Airport Express and wala, fast Internet connection again! ๐Ÿ™‚

The hotel must’ve changed something yesterday, as the previous Airport Express configuration worked before, and I’ve been here for more than 10 days. hmm…

the connection at my hotel

The connection at my hotel is insanely slow at peak hours, like right now, 20:00 PST… Crazy packet loss… ๐Ÿ™
[PowerBert:~] ayn% ping www.google.com
PING www.l.google.com (64.233.179.104): 56 data bytes
64 bytes from 64.233.179.104: icmp_seq=0 ttl=240 time=136.066 ms
64 bytes from 64.233.179.104: icmp_seq=2 ttl=240 time=1929.158 ms
64 bytes from 64.233.179.104: icmp_seq=3 ttl=240 time=929.055 ms
64 bytes from 64.233.179.104: icmp_seq=4 ttl=240 time=140.096 ms
64 bytes from 64.233.179.104: icmp_seq=5 ttl=240 time=1066.102 ms
64 bytes from 64.233.179.104: icmp_seq=9 ttl=240 time=9098.939 ms
64 bytes from 64.233.179.104: icmp_seq=10 ttl=240 time=8099.114 ms

I think I’m gonna watch my NetFlix DVDs instead, I can’t stand slow Internet connection.
Continue reading →

Venture Chronicles by Jeff Nolan: Other Shoe on Google Talk

Venture Chronicles by Jeff Nolan: Other Shoe on Google Talk

Of course Jeff Nolan was right, but the thing is, there are already Jabber/XMPP transports that work with AIM/ICQ, MSN, and Yahoo. I’ve used Jabber for years and they work just fine. You do need an account on all the other services to talk to your friends. But Google might add features in their client on top of the regular XML-based Jabber, so you can convince your friends to use their chat client, and then after a while they might very well switch to using Google if the voice (or video, or whatever) feature only works there.

The problem with Jabber is that it was never easy to use, and it was never very stable. To register my Jabber account on my friend Dan‘s server I had to telnet to a certain port at the server and type in XML code (now most clients support registrations). jabberd, the Jabber server, was sorta a hack, and seems like nobody cared enough to maintain it. The MSN and Yahoo transports were also not maintained. With Microsoft and Yahoo trying to block other clients from using their services every other day, they didn’t work half of the times. This was true until very recently, I’m not sure what happened, maybe Dan installed newer versions of the server and transports. Jabber has worked flawlessly for the last several months.

Also, if you domain name doesn’t resolve to your Jabber server, you’re pretty much screwed. And I wanted to have [email protected] instead of ayn@jabber.mydomainname.com. I had the vision that Jabber will eventually replace all the IMs and it would work more like emails, with distributed servers that handle IMs. The Jabber specs supports _jabber._tcp SRV DNS records, so in theory if I include a line in my DNS entry to indicate to where Jabber TCP traffic should go (sort of like the MX entries), it should work. But I don’t think it ever did, last time I tried was 3 years ago though, so this might not be true now.

Google, once again, took an existing technology, vastly improved it (I’m sure they rewrote most of jabberd), added features to it (voice), and rolled it out as a brand new service. Probably 90% of the Google Talk users had not heard of Jabber before. This is pretty cool.