Scripting News

Sorry I still hate Comcast

Wed, 02 Sep 2009 16:05:21 GMT

Hate is a word I've tried to wipe from my vocabulary, along with need. You don't really need more than air, food, water, a warm place to sleep, basic medical care. There are lots of things that are nice to have, like hugs and kisses and great sound systems and business-class-or-better. But needs are pretty basic things.

Hate? People throw that word around far too casually. The other day a rep of SXSW said that I had hated on them because I suggested they were taking money to keep me off the speakers list since 1998 or so. I had asked many times why I couldn't get in, and was met with a stone wall. So like all human beings, my mind filled in the blanks. I asked to be enlightened, if it wasn't a payoff, what was it? I offered to run a retraction if they would tell me the real reason. Stone wall again. Oh well. I don't hate them. The word I would use to describe my feeling about SXSW is frustrated.

But Comcast? I think that's the real thing. I'll tell you why.

Love and hate have a mathematical relationship:

hate = love + betrayed

I would love to have Comcast service, but I would never sign up for it again unless they apologized for the treating me so badly. And while most companies apologize when they screw up, I have a feeling that Comcast thinks I should apologize to them. And that ain't never going to happen.

Why write about this today? Well they're getting a lot of kudos because they try to fix their fuckups with reps who use Twitter to find unhappy customers. When I got fired as a Comcast customer, I was in contact with their Twitter caretakers. Not only couldn't they stop the Comcast machine from chewing me up and spitting me out, they had the gall to say they liked me while they were doing it! Now that's really asking for the hate.

Imagine a girlfriend dumping you, hard, and while she's doing it saying she likes you. Well fuck that shit bitch. <-- There's the hate.

But their service is much faster than my AT&T DSL. I pay my bills, in full and on time (as I did with Comcast), and they don't have Twitter accounts. They never cut me off (knock wood), and I never have to talk to a Twitter rep who likes me. Maybe I'm weird but that's kind of how I like to do business.

Learning from the fire of 1991

Wed, 02 Sep 2009 14:45:39 GMT

Fires are on the minds of Californians, esp ones who live in the hills, like the ones in Berkeley and Oakland.

In 1991 these hills burned. I watched the fire, safely, from a friends' deck on Potrero Hill. It seemed far away, but now I live here.

In the RTN podcast on Monday I asked Doc Searls if we could learn from the fires in Southern California.

Today, on InBerkeley, I ask if there are any old-timers who were here during the fire of 1991 who would share what they learned.

rssCloud meetup at UC Berkeley, Sept 9

Tue, 01 Sep 2009 00:20:36 GMT

The first rssCloud meetup in NYC in July was a great success.

Now we're ready for rssCloud Meetup 2.0, on Wednedsay September 9, 7-9PM at 110 South Hall on the UC-Berkeley campus. South Hall is the gothic brick building in the center of the UC Berkeley campus, just across from the iconic clock tower.

It's a 15-minute walk from the downtown BART station.

The meetup is open to all, but primarily for developers. The goal is to bootstrap the loosely-coupled 140 character message network. One that's open on all sides, so anyone can add an aggregator, cloud server or authoring tool, yet still have the feel of a centralized system. There may be tradeoffs, but the benefits of not having a company at the center of the network should create great opportunities for news organizations, innovative developers, designers, businesses, and users everywhere. Twitter is great, but we want something that works better for all of us.

We hope to see one or more new implementations come online before or at the meetup.

The way it'll work is: 1. I'll talk for 20-25 minutes, review the walkthrough, technology, philosophy, then briefly answer questions. 2. We'll go around the room and people will say what they're doing, and what kinds of help they could use. 3. Then an open discussion, and we adjourn.

There will be free wifi, but if it's like the NYC meetup you won't need it. This is a complex and interesting topic that seems to hold people's attention. But it's California and you never know, so bring your laptop, just in case.

If you know you're going to be there, please post a comment on this blog post.

Thanks to the UC Berkeley School of Information for generously offering to host this event.

Wanted: A simple DNS app for Mac or Windows

Sun, 30 Aug 2009 17:24:43 GMT

In the early-mid-90s there was a Mac desktop app that was a Domain Name Server. Here's how you'd set it up.

1. Put it in your Startup Items folder so it would launch at startup.

2. When it booted a window opens with a list of all the domains it was managing. Of course initially it was empty. You could click on the name of any of them to edit the settings in a dialog. There was a place to edit the name of the domain. A place to add an A record or a CNAME. (In other words it works more or less the same as any web app we use to manage DNS.)

3. An Add button at the bottom of the window. Click it and a dialog like the one in #2 would appear, except all the fields would be blank.

4. There was a text file that also configured the server, in fact the dialogs above just served to add, remove or change the text in the file. I suspect the file was in a standard format that all DNS's use.

Anticipating what people are going to say, yes, I know there's a DNS built into the Mac, but it doesn't have a graphic interface and the instructions for setting it up are ridiculous. I think the one on Windows has a graphic UI, but I can't find any comprehensible instructions that explain how to set it up.

A college classmate, Sandy Wilbourn, who I think of as a brother, is an expert in DNS, and he says the app I'm looking for doesn't exist. I threatened to write it myself, he advised against it. Oh man. What is it with these simple web services that we're allowed to use them through a web app, but they don't want us running our own. I'm going to run my own DNS at some point, and I'd rather do it sooner than later.

Someone is going to ask why I need to do this. I have a good reason. You can either take my word or pay me $1000 and I'll explain.

Update: Chuck Shotton points to MenAndMice's server for Windows, and JY points to CutEdge's server for Mac. Both appear to fit the bill. Thanks guys!!

Joe Hewitt on Bad Hair Day at 7PM

Fri, 28 Aug 2009 00:57:29 GMT

Our special guest for the Bad Hair Day podcast at 7PM Pacific is Joe Hewitt the author of Facebook for the iPhone. What a great day to talk with Joe!

You can listen live on BlogTalkRadio.

I had lunch with him yesterday in Santa Cruz. I said that if Facebook wanted to compete with Twitter they needed a vastly simpler version of Facebook. Little did I know that 24 hours later I'd be looking at it.

If you have any questions for Joe, please post them as comments here, and Marshall and I will try to get to them.

You can listen to the show live on BlogTalkRadio, and of course it will be available as a podcast from the badhair.us site.

Here we go!

My one sentence review of the Facebook iPhone app

Thu, 27 Aug 2009 22:13:17 GMT

I wish the desktop version of Facebook was this simple, fast and elegant.

Update: Believe it or not I actually had lunch yesterday with Joe Hewitt, the developer of this app. I said that if Facebook wanted to compete with Twitter they needed a vastly simpler version of Facebook. Little did I know that 24 hours later I'd be looking at it.

Another screen shot shows why a simplified Facebook kicks Twitter's butt.

Health care in a nutshell

Thu, 27 Aug 2009 19:38:34 GMT

Health care is a lot like a fire department or police department. You never know when it's your house that's going to be on fire, that's why everyone pays equally for protection, and the person whose house burns gets the "benefit" if you can call having your house burn a benefit (or getting very sick).

The main difference is that very few houses burn, but eventually everyone needs life-saving or end-of-life care. Every responsible person must pay for care, and basically only the truly rich (multi-millionaires) can afford to self-insure.

If you assume that everyone has to pay for health insurance, then the question is how much do you want to pay. In the US, our current system costs 16% of GDP and we get less care, in some cases much less care than other rich countries that pay as little as 9% of their GDP.

So we're making poor choices here.

Obama's plan is less comprehensive than the German, Canadian, French or Japanese plans. In each of these other rich countries, health insurance is a non-profit business. That doesn't mean insurance companies don't make money, they do, but not from health insurance. Obama isn't promoting that (although it's not clear why).

And for 40 million Americans they might as well live in the third world, for them health care is based on their ability to pay out of pocket. As long as they just get colds, they survive. As soon as they need more care, they either go bankrupt or become disabled, or die. This is their country too, they get a vote in how our system works. You're related to some of these people (unless you have no family). They're the ones who should be standing in anger at the town halls. And they're not all poor, many of them are middle class or upper middle class, they just happen to not be profitable for the insurance industry. These are the people whose houses burn to the ground when they catch fire.

The people who would vote against universal health insurance are stupidly cocky, because they will all need health care some day and for many of them it will not be there. Sometimes they're people who don't smoke or aren't obese, who don't have any personal bad habits. People get sick for a lot of reasons that no one understands. Maybe just bad luck or bad genes. In the wrong place at the wrong time.

Bottom-line, we could spend a lot less money on health care and take care of everyone. Instead we're opting on the worst approach, we spend a lot more, and a huge portion of the populace isn't cared for and the rest of us are treated not as patients but as profit centers. If you happen to need health care, you can't get it. This is some kind of way to run a country? Yikes.

If you want to understand what our options are, I highly recommend listening to the FreshAir interview with T.R. Reid, who has just written a book on health care systems around the world.

RSS is how the news flows

Wed, 26 Aug 2009 15:21:27 GMT

To Sam Diaz who says RSS was "a good idea at the time but there are better ways now," I have many things to say.

1. People confuse RSS with Google Reader. Let's be clear that there's a difference. Google Reader is an application that reads RSS-formatted data. There are many other applications that read and write RSS.

2. I think Google Reader was, on the whole, a good thing. It's probably the best reader of its variety. You have to go find the new stuff in Google Reader. I prefer a reader that finds the new stuff for me, and presents it in reverse chronologic order. This is known as a river of news reader.

3. Diaz more or less says that's his preference too. Interesting.

4. My newspaper doesn't tell me how many articles I haven't read going back to the date of my birth. I bet it would be in the millions. Why should I care. This was the worst idea ever in news readers.

5. The core problem -- so many programmers who write RSS software are not themselves news junkies. If they were they'd know when they got it wrong. News is about what's new! Show me the newest stuff first. Sorry to all the articles I didn't read, maybe in the next lifetime.

6. He may not use a RSS reader, but the news is still getting to him through RSS.

7. If all the RSS on the planet were all of a sudden to stop updating (key point) the news would stop flowing. Any news guy or gal who thinks they could get by without RSS -- think this through a bit more. We all love the Internet, but don't shut off your gas and electric because your computer and router wouldn't work without electricity. Same with RSS and news. RSS is how the news flows, whether you see it or not. If not RSS, something exactly like RSS.

8. The Internet is layered. New technology comes on line building on tech that already existed. RSS was like that. It built on XML and HTTP, which built on text and TCP/IP. The new things that Diaz likes so much, in exactly the same way, build on RSS.

9. When news authors don't understand how technology evolves, they propagate incorrect notions to everyone else, including would-be inventors, who have to figure it out for themselves, and then convince investors and partners they know what they're doing -- when they just read in ZDNet that things don't evolve at all. So Mr. Diaz does us all a disservice.

10. I object when technology writers tell the story of technology incorrectly. People say I should just be happy to see my name in the story, or in this case something that I fathered. No deal. I want the accurate story out there. I want people to understand how technology really works, because that's central to users being empowered by it, instead of being controlled by it.

Bonus: Marshall Kirkpatrick, my partner in the Bad Hair Day podcast (tomorrow 7PM Pacific) has his own excellent rebuttal to the Diaz piece.

Random Wednesday notes

Wed, 26 Aug 2009 15:08:57 GMT

Last Wednesday I did a Random Links post, and here goes another. A tradition begins?

Very little flamage over my What is an Asshole piece from last night. Guess people got the point. If you fail to understand Hitler, you deserve to get Hitler. Their only sin, beyond stupidity, is their inability to imagine that it could happen here.

What is an asshole?

Wed, 26 Aug 2009 02:17:14 GMT

An asshole is someone who says Obama is like Hitler because he wants everyone in the US to have health insurance.

These people are so stupid they need to be slapped in the face to wake them up. They need to have their mouths washed out with soap and be sent to bed without dinner. They need to be sent into hard labor and allowed to die of starvation.

Hitler gassed my people and incinerated them in ovens. Hitler came very close to wiping us out. Hitler was a monster. Hitler was the human race going insane on a mass level.

If you think Obama is Hitler you deserve to meet with others who agree with you, starving and freezing and dying in a cattle car, sitting in each others' excrement, on your way to a concentration camp and its ovens and gas chambers, along with your children.

You will not be allowed to bring your assault rifle.

How to fix URL-shorteners, part II

Tue, 25 Aug 2009 22:17:41 GMT

Last Wednesday I wrote a piece that explained how to fix URL-shorteners. Today, with the help of Joe Moreno at Adjix, I implemented it.

Here's how my new URL-shortener works.

1. Joe is running the shortener at adjix.com. It's the same one he's always been running, but it's got a few new features.

2. In the prefs for Adjix, I told it that I wanted to use my own domain, c.oy.ly. I also told it to write copies of all my shortened URLs to a bucket at Amazon, which I had given his app permission to write to. By using my own domain, one which I control the DNS for, and retaining a copy of all the data, I am fully protected against his service going away. And I can decide at any time to take over hosting of my own short URLs by directing the c.oy.ly domain to s3.amazonaws.com instead of partner.adjix.com.

3. When I create a shortened URL, I do it by calling an API routine that works exactly as the APIs of the other shorteners. I give it the long URL, some identifying information so it knows to associate it with my Adjix account, and it returns a token, which I smash together with http://c.oy.ly/ to form the shortened URL.

4. All this is done with a bookmarklet communicating with a web app on one of my servers. It then takes the title of the page I'm linking to and adds the full URL from step 3, and redirects me to twitter.com, where I can edit the tweet before clicking on Update.

5. Then, every few minutes I call the Twitter API and ask if Dave has posted any new tweets. If so, I parse them, store the long and short versions of the URL in my database (by dereferencing the URL). Then I call a second API on Adjix to ask it to give me the counts for the most recent 50 links created by Dave. I then update the counts in my database, sort them, and prepare the familiar Top-40 report.

Bottom-line: I am now using URL-shorteners in a way that does not make the Internet suck. I have done my good deed for the day!

Dear Disqus: Can I have the old interface back?

Tue, 25 Aug 2009 19:25:56 GMT

Near as I can tell there are no new features in the new interface. Things were just moved around and everything is way way slower. The UI was always bizarre, but I figured most of it out. Now you're telling me I have to learn it over again? Why? What's the benefit?

All I know now is that my bookmark to the dashboard broke, and to get to the unapproved messages or spam messages, the maintenence I have to do on a regular basis to keep my site working, I have to wait minutes for the page to load. I don't have any idea if there are any new features in this to justify the pain.

I would really like to go back to the way it worked this morning. You know, when it actually worked.

How to get Lessig to blog

Tue, 25 Aug 2009 14:23:04 GMT

It's sad that Lessig is "hibernating" his blog, but there's always hope. It's easy to say goodbye, but what's he going to do when he has something that has to be said right now. Wait two years to write and publish a book? I sure hope not!

In his supposedly last blog post (heh) Lessig points to his first post, which was a response to something I wrote in response to something he said. In 2001 and 2002. It's interesting to recount the exchange, because only seven years later things have changed a lot.

1. First Lessig tells a story of Hemingway and source code, an analogy that I feel is flawed. And I say so, very strongly, but hopefully not in a personal way.

2. Then in August 2002, I expanded it, and on re-reading it -- I said some things that were a bit too much. A difference of opinion between two learned people shouldn't involve throwing people out and "up yours."

3. This got Lessig to write his first blog post! So there is a silver lining.

Now the hindsight.

1. In 2002 I said in five years every member of the US House will have a weblog and will be communicating directly with the electorate. I'd say that's been realized now, only they're using Twitter and Facebook and blogs, and they have to communicate directly with the electorate because the news industry is crumbling.

2. The controversy betw Lessig and myself in 2001 and 2002 was over whether software developers should be required to release their source code to get copyright protection (at least that's how I interpreted it). I was vehement in saying no, that we were already putting our ideas out there and that putting the source code out there too would give us nothing to sell. I still believe the logic of that, but since then I gave up on commercial software and in 2004 I released my main work under the GPL. There was no parade, no new respect or even thanks from people outside the community that already used the software. Did it inspire any young would-be designers? Time will tell, but it's looking doubtful. Just saying it's harder to influence the future than it should be, or maybe not -- who knows.

3. I like to think that Lessig and I have now become friends. Just goes to show that when there's a spark between two people, it may express itself in a variety of ways. I admire Lessig, I've come to see him as an open-minded, generous person who really listens. All good things!

4. I don't believe for a second that he's given up blogging.

Urgently need an Intel build of OPML Editor/Mac

Tue, 25 Aug 2009 13:15:51 GMT

I thought about writing a more creative headline, but opted instead for a direct request for help.

1. Yesterday I pre-ordered a family pack of Snow Leopard. As I understand it, the new version of the Mac OS will run PPC apps only with special software loaded, the way earlier versions of the OS ran Mac Classic apps.

2. The OPML Editor for the Mac is a PPC app.

3. It is also an instance of the GPL'd Frontier kernel, which I understand has been converted to be an Intel app.

4. I can build the Windows version of the OPML Editor. However, I cannot build the Mac version. It's been a long time since I worked at the C level, last time I did was with THINK C on the Mac in the mid-90s. I've tried to build the Mac app on XCode, but I always hit a problem that I don't know how to work around, and honestly I don't want to struggle at this level. I'm going to stick to developing in the OPML environment. When I can do a kernel build on both Mac and Windows, I may look at working inside the C codebase.

5. I need someone to get a build of the Mac OPML Editor together asap and to do some basic testing to be sure it works with the current opml.root.

Resources: The Frontier Kernel project website. Source download of the OPML Editor from August 2008.

Thanks in advance!

What's in the next release of River2

Mon, 24 Aug 2009 17:18:54 GMT

The first release of the River2 aggregator was all about CSS. I wanted to be sure this new aggregator would be buzzword compliant and user-configurable. I wanted the design community to have their way with this tool.

The second release has a completely different set of goals, they relate to the subscription engine, realtime processing of updates, and podcast support. Specifically...

1. Dynamic reading list support. A reading list is an OPML file that contains a subscription list that is read every time the aggregator scans its feeds. Any new feeds are subscribed to, and any feeds that are no longer in the list are unsubbed, assuming they aren't in another reading list or were independently subscribed to. This feature has been in my aggregators but not in most others. Google Reader, for example, does not support this feature, but imho it should. I'm putting this out there to help lead the market.

2. Fully rssCloud compliant. If you subscribe to a feed that has a cloud element, and you aren't behind a firewall or NAT, River2 will request notification, so that updates are received in realtime.

3. A podcatcher that's not from Apple. The market needs more than one podcatcher. So if you subscribe to a feed that has enclosures, it will download them into a folder of your choosing. This works for photo feeds as well as feeds with audio and video.

Tying it all together, here's a reading list that contains podcast feeds, one of which is cloud-enabled.

This release is not ready for download yet. Because I got a bad cold, and was sidelined last week, the project was set back by a week. But developers are moving ahead with their rssCloud implementations, and will need something to test against. That's one important role of River2, it represents a reference implementation of the client side of the rssCloud protocol.

What's next after this River2 release? More cloud-enabled feeds. An editorial tool that produces cloud-enabled feeds.

Yahoo embracing Twitter?

Mon, 24 Aug 2009 03:25:17 GMT

Silicon Alley Insider has an interesting piece about Yahoo's obsession with all-things-Twitter. And at the end they have an even more interesting strategy. "Yahoo should work to be a better place to use Twitter than Twitter.com."

This sounds a lot like the winning strategy Yahoo used to best CNN and MSNBC in web news in the 2004 timeframe. With My Yahoo they became the place to go to find out what's new on CNN and MSNBC, and of course on Yahoo.

This kind of embrace is a perfect prelude to competing with Twitter. First, develop a base of people who use Yahoo as their interface for Twitter, and then gradually add features that only work Yahoo-to-Yahoo.

Twitter could add those features too of course, but they might not, since they believe (incorrectly, imho) that the 140 character limit and URL-shortening are part of the magic of Twitter.

Yahoo, or anyone else who adopted this approach, could capture the users who would like to have a bit more space to express their ideas.

Courage and cowardice

Mon, 24 Aug 2009 00:34:42 GMT

First courage...

Arthur Frommer, the famous travel writer, writes on his blog. "I will not personally travel in a state where civilians carry loaded weapons onto the sidewalks and as a means of political protest." He's talking about the event where people openly carrying guns, one carrying an assault rifle, gathered outside an event where the President spoke.

Arizona can say that people have the right to openly carry guns of any kind at any time, and we can choose not to spend time or money in such a backward place. Perfectly appropriate way to react to an obvious attempt to scare people.

Now cowardice.

Last week I wrote about how Republican Senator Charles Grassley from Iowa, one of a very small number of Republicans who, imho, was honorable -- took the coward's route and threw grandma under the bus, doing his part to confuse the electorate on the issues in the health care decision we will soon make. Paul Krugman follows up, now Grassley has the gall to blame first President Obama and then one of his constituents for his cowardly deception. He's 75 years old. Is winning another election so important that he wants to be remembered as a dishonorable liar and coward?

In all the debates about health care reform, the real issue isn't getting talked about. It's about the people who don't have coverage. Some of the easiest cases are people who have the money to buy insurance, and would buy it, if the industry would sell it to them. But they only want to insure healthy people. So we're in the ridiculous situation here where the people who most need care can't get it. Someone should tell Grassley that some of those people are our grandmothers, and grandsons and granddaughters. Nieces and nephews and mothers and fathers. Don't go claiming the compassionate high ground, when you're selling us out. Shame. (And it could be that some of his own family are screwed by the insurance industry. If not, why not?)

Of course there are the cases where people pay premiums for years, then get sick, and the company denies coverage, disputing information on their application, or claiming a pre-existing condition, long after accepting the premiums. What recourse do we have? We can sue the companies, but that takes huge money, money they have and we don't. And what difference will it make if by the time the case is decided the patient is dead? The whole idea of pre-existing conditions is one that we need to get rid of, completely. Everyone who wants insurance must be able to buy it. Period. No exceptions.

Because these problems concern millions of Americans, everyone knows someone who has been put through the ringer by the insurance process. These stories about angry people (what are they angry about exactly and what does it have to do with health care) are drowning out the tragic stories of people who die because they aren't covered.

One more pointer.

The Democrats aren't blameless because they aren't selling health care reform.

George Lakoff explains how it must be done. Not with lengthy explanations of policy, but with stories that fit into the experiences of all of us, and connecting the values of universal health care with what it means to be an American.

7 years plus 70 days

Sat, 22 Aug 2009 15:52:28 GMT

7 years ago today: "Tomorrow is Day 70 of No Smoking Dave. Ten weeks. A non-smoking story at the Bowie concert last week. As I'm walking out I see people lighting up everywhere. Smell of smoke all around. It smells good. I really want one. In my mind I outline the steps it would take to be smoking and the amount of time it would take. I would ask someone if they could spare a cigarette. If they said no I'd offer them $1. Oh hell, just offer $1 to begin with. Whoo, where would I get a match. I'd ask for a light. Take a drag. Estimated time, 15 seconds to one minute to first nicotine rush. My heart started beating faster. I felt scared like you feel on a NY subway platform as a train is entering the station and you're standing on the platform and in the instant before it passes you think how you could end your life by leaning forward. I never actually jump, and that night I didn't smoke, and it's good that inside I equate smoking with death so deeply that it invokes my subway nightmare. Do I have it beat? No way. I am still an addict, I expect I will be for life. But I'm an addict in recovery, who is not taking the drug. Even better, I am becoming a constant evangelist for a nicotine-free lifestyle for nicotine addicts, illustrating the old adage that you teach what you most need to learn."

Wish I could send a message back in time to that Dave, seven years ago. I'm sure at some level I'm still a nicotine addict, but I no longer go through this torture when I see someone smoking. Quite the opposite. I smell it and it repels me. Given enough time, you go into remission. Maybe never all the way, but pretty close.

My #blogpostfriday post

Fri, 21 Aug 2009 19:00:18 GMT

I've had a non-productive week, I've been fighting a cold -- but I made a commitment to the web to write at least one post every Friday, so here I am keeping my promise.

I'm worried about the web.

We pour so much passion into dynamic web apps hosted by companies we know very little about. We do it without retaining a copy of our data. We have no idea how much it costs them to keep hosting what we create, so even if they're public companies, it's very hard to form an opinion of how likely they are to continue hosting our work.

A few weeks ago an entrepreneur said to my face that he was the one who made the money and I was the one who worked for free. My chin dropped. I knew most if not all of them secretly believed this, but I had never heard one say it out loud.

I know others who told me their business model was to patent my work.

Shaking my head. This can't work.

This system is terrible. It's a bubble, like the real estate bubble. It's going to burst, and when it does, it will take a lot of our history with it.

But not this blog post if I have any say about it. It's stored as a static file on a Windows XP server running Apache. It could just as easily be stored on a Linux machine running anything. Or even an iPod or iPhone. Text files are the ultimate in stability. The same text file you could read on a mainframe 40 years ago could be read on a netbook today.

I'll post a link to this piece on Twitter, that probably won't last very long. But -- the backup I'm making of it is being stored as a static text file on Apache. So it may well be around for a while.

I'm really obsessed with creating a historic record. I want to feel that our writing has a future. I also don't want to work for people who are as openly greedy as the typical entrepreneur of 2009.

Anyway -- time to go to lunch. I've taken my vitamins on behalf of the web.

From the 'It Seems To Me' Department

Fri, 21 Aug 2009 02:02:19 GMT

Sometimes 140 characters is enough to express an idea.