It's Just this Little Chromium Switch Here

Weblogging and commentary by Chip Rosenthal

SXSW: Open Source Panel

I mentioned in a previous posting that I was drafted onto an SXSW panel. Here is what happened.

I ran into Hank Jones that morning. He mentioned something about dropping by his panel that afternoon. I responded, "Hrmm. Huh? Whatever. Ask me when I wake up." Remember, this is the morning that I lost my car.

Recall Verisign

in

I've written several articles about the damage Verisign caused with their Site Finder product rollout. The current Verisign controversy is over a scam called "Wait List Service." Fed up yet? Go Daddy has started a petition to recall Verisign.

SXSW: Warm, Dry, Happy

Day two of SXSW was much happier than the previous day. This time I remembered where I parked.

I already discussed some of the great panels I attended and some of the interesting people I met. It all added up to make one great day.

Plus, I got to say "hi!" to Molly Ivins.

Full Content RSS

Tonight, I switched my RSS feed to include full article content instead of just an entry synopsis. I'd been ambivalent on the issue. I realize many people like full content, but I wish they'd come to my site to get it—for the comments if nothing else.

That, however, is imposing my preference on others. Probably the best thing is to give people the choice and let them pick whichever they want—and just be grateful somebody wants to read my crap.

Unfortunately, I have a lot of content that will not work in RSS. Many of my blog entries use relative links. Although the newer Atom standard allows for relative links, prior RSS versions do not.

Today I realized I don't need to worry about historical entries. I just need to be sure that from here on out I only use absolute links in my entries. The RSS feed contains only recent entries. The old ones don't matter.

There are some very good reasons to put full content in RSS. So, as of now, it's there.

SXSW: RSS Solutions

I spent the morning doing the "search" track at SXSW. First was Don Turnbull's panel on Revolutionary Search Technologies, followed by Marissa Meyer talking about Google.

I asked a question of the first panel, more related to information architecture than search. "Since RSS has become a fad, people have been rushing to move all their structured data into it—even if it's not an article for syndication. Is that a good thing?"

Scott Johnson fielded the question. He said a year ago he would have said stuffing everything into RSS was a bad thing. He's changed his mind. People are putting all sorts of things into RSS and it seems to be working. At the very least, it gets the information partitioned properly.

After the session, I introduced myself to Scott and explained that I was thinking about this problem in the context of event scheduling. I'd like to see organizations, say, around Austin be able to publish their event calendars in an XML format. Then people could aggregate a calendar of events from whichever organizations they might choose. RSS provides a powerful syndication mechanism for the project, but not the appropriate structure for schedules. Scott pointed out there is an RSS extension out there for scheduling. I was excited to discover that. This project suddenly seems more feasible.

I tagged along with the search people for lunch. Over ribs and chopped beef sandwiches, I mentioned one of my worst, current RSS annoyances. I stuffed the Austin Bloggers blogroll into an RSS feed, but it won't validate. The <author> tags for the blog entries sometimes are names or 'nyms and not full email addresses, which violates the RSS spec. I guess I'm not the first person to complain about this. Sam Ruby rolled his eyes and said, "Use <dc:creator>. It's a perfectly good tag." I'm not sure why I overlooked the Dublin Core tags, but that's the perfect solution to my problem.

SXSW: Cold, Wet, Grumpy

Onward to day two of SXSW. Day one ended not with a bang, but a sloosh.

At the last minute I got pressed into service as a panelist for the Can You Build a Company From Free Code session. I was glad to help, although I have been more suited for a panel about not making money from open source software.

After that panel, the last of the day, I hooked up with a crew of local ruffians to find a happy hour. We headed out towards 5th Street. The gray skies started drizzling. The battle tank laptop on my shoulder started dragging. I thought it would be a good idea to split off, find my car, drop off the laptop, grab a jacket, and rejoin the group at the club.

An hour later I was wandering around Convention Center area in the rain, trying to remember where I'd parked that morning. By that time my clothes were soaked and my laptop weighed another twenty pounds. I was getting very cold, wet, and grumpy.

I ducked out of the rain and phoned my girlfriend at home. "Help!" She drove down and got me. We had a quick dinner and then set out to retrace my steps that morning. Naturally we found it almost immediately. I suppose I could have rejoined the evening activities, but by that point I just wanted to go home and crawl into bed.

I hope that doesn't happen again. Today I made good note of where I parked. I'm over at the corner of Third and....errrr....something.

SXSW: The $85 Blog Entry

The sickly batteries in my aged Dell Inspiron laptop won't hold much more than fourty-five minutes charge these days. I brought it with me to SXSW, thinking maybe I could do a little blogging during the breaks. I'm currently sitting in the hallway pulling a good W-Fi singal, in a location near a power outlet.

Unfortunately, one of the conference volunteers just stopped by and suggested that I may want to unplug from the wall. He said if somebody from the Austin Convention Center staff sees me, they will bill me $85 for power.

If that happens then I'm bringing a TV and microwave oven with me tomorow. If I'm going to have to pay for power I want my money's worth.

SXSW: Per-Message Email Charges Won't Fly

in

Last month I wrote about stopping spam by placing a per-message charge on email. I think it's a bad idea. The proposal is getting a lot of serious attention, though, because Bill Gates is its most visible advocate. He points out people are willing to pay 37 cents to send a letter, so why not a penny for email?

I think there is ample evidence this just won't fly. John Levine has pointed out we've already been there and done that. There once were commercial email systems such as MCI Mail, which were supplanted by flat rate Internet email, and are now just a dim memory.

I don't think we need to reach into the distant past for a good example. How about celullar phone subscribers? At least for basic voice service, subscribers seem to demand a fixed rate subscription and will do anything to avoid per-minute charges. I think any Internet service that implements per-message charges will find themselves hemorrhaging subscribers.

This morning at SXSW, the "History and Lessons of the Cellular Industry" panel offered an opportunity to sanity check this theory. After the panel I approached Jeff Nelson of Verizon and asked him what he thought about switching from fixed rate to per-message charges as a spam solution. He discussed business models and was quite unapologetic that his goal was to get subscribers to pay as much as he could get them to. I was curious what he thought about this anti-spam proposal.

Like most people, just the mention of "spam" tripped his alarms. He said that spam is a huge concern for cellular providers. They careflly watch what happens on the net as a whole, which serves as a leading indicator for activity on the cellular networks. All the providers are worried and working to keep spam at bay.

I dragged him back to the question: what about switching from flat rate to per-message charges? He just rolled his eyes. He said under his breath, "If my Internet provider tried to charge me for email I wouldn't stand for it."

It was like he viewed per-message charges as a third rail issue. I think it shows that scheme isn't going to get very far.

Do Something for Democracy: Support Safe Electronic Voting

What's worse than a Florida-style election that degrades into a recount quagmire? How about an election that can't be recounted at all?

When it comes to election integrity, "just trust us" is not a viable strategy. Yet, that's the direction we are headed. Throughout Texas, including Travis County, we are deploying electronic voting machines (that's good!) that lack a verifiable audit trail (that's scary!).

RDF: Die Die Die!

I think it's time to kill off the RDF feed of this weblog.

For those of you not following at home, there are a multitude of format choices for the RSS syndication format. This is not a good thing. This is mostly the result of a number of people acting badly.

When this blog started, I published 0.91 and 1.0 feeds. Last December, I dropped the 0.91 feed and upgraded it to 2.0. I think now it's time to drop the 1.0 feed (also called "RDF") and consolidate everything to a single 2.0 feed. This may help reduce confusion and hassle created by multiple feeds. Now that 2.0 is widely supported, I think it's the right choice. It offers much of the flexibility of version 1.0 without demanding all of the complexity.

There is another reason for simplifying the feed choices. There is yet another new syndication format on the horizon. I do not want to end up in a situation where I am supporting three feeds.

My RSS 2.0 feed is available at http://www.unicom.com/chrome/index.xml. Soon, I will replace the index.rdf file with a static document that points to this article. I hope folks who were using the RDF feed will switch.