The death of the beta

Guardian Technology Icon

The term "beta" will also collapse into irrelevance in downloadable software, predicts Chris Messina, who calls himself director of experience at Flock, a startup developing an open source browser. Users of Microsoft products know that when software products move out of beta, users are flooded with security and quality patches in short order, meaning that version 1.0 isn’t so much a magic milestone as just another point in a continual cycle of development.

"I see gradients of validity where for my mom I might wait until Flock gets to 0.8 before I install it for her," Messina says. "For friends who I like I’ll give them the development version that won’t crash the system, and then for people I don’t like they can have the nightly builds. So I think we’ll have three tracks."

Guardian Unlimited Technology | Are you a dummy for beta software?

So there you have it, if I don’t like you, go download an nightly hourly build. 😉

No, just kidding.

But the point stands — software development is indeed becoming more organic, without really even realizing it (or maybe it has been all along, but we’ve fought its natural state for business reasons — after all, selling upgrades is a lucrative bidniz). Sure, you’ve still got holdouts and beta logos plastered all over the place, but the reality is this: software is a process. It’s never really done. The longer we go on pretending that the vaunted one-dot-oh somehow indicates a sense of finality, security or stability, the harder time we’re going to have convincing folks not in the geek world that there will always be bugs, that there are no right answers, that, just like natural systems, we’ve got to design for imperfection, frailty, accidents and hell, the irrationality of human actors.

So listen, I’d read somewhere recently (I forget where — I wasn’t using Flock so I can’t full-text search my history) that this whole BETA program fad is just a way for companies to shirk responsibility for the apps they deploy. It’s like, you call something "beta" and poof, no more responsibility. Well, clearly no one really does read EULAs anymore or you’d know that, beta or not, no one takes responsibility for anything anymore. It’s all the in the EULA, usually in some big bold type like this: WE DON’T CARE IF YOU BLOW UP YOUR COMPUTER WITH OUR SOFTWARE, IT’S NOT OUR FAULT AND THE LAW IS ON OUR SIDE, GET OVER IT (copied from the IE7 beta 2 EULA).

(No, just kidding).

Anyway, I think the point that Schofield makes in his article is a good one, and I enjoyed the chance to talk to him about it. But really folks, and this was raised in that conversation, what the heck are we going to do with desktop apps and the ever-present push towards one-dot-ohs? I don’t see them going away any time soon and yet they simply don’t reflect anything useful, especially since webapps have the luxury of never really worrying about that problem and can be in a constant state of flux and no one really cares… As it is, Thunderbird has been downloading updates every other day, asking me to restart it so that it can update itself… I have no idea what version I’m running — only the knowledge that somebody, somewhere is working on the thing and that its stability comes in fits and spurts. And that’s ok, because I’ve come to Jesse baby, hallelujah!, praise the Ford, Zen-master dojo, taekwon-do and on and on. Yeah, now that software development is becoming more zen-like, how do we help the rest of the world cope with the realities of such uncertainty?

Incurring the wrath: tags vs labels

Tags vs LabelsSo now that the Google Toolbar has added support for “labels” (and not tags) it seems like there should be some consensus built about the heck we should call these little jellybeans in Flock.

Vera has repeatedly told me that “tagging” is a hard word to use in documentation because it has multiple purposes… whereas “labeling” is a bit more clear and more singular in its utility. Let’s face it, when you label something, it’s pretty clear what the before and after states are. When you tag it, not so much.

The other thing we have to consider is this: since Google is obviously throwing its hefty weight behind labels and not tags (consider Gmail, Picasa, your search history, the toolbar and elsewhere), we might do well to realize that the de facto “word” for this behavior will not be “tag”, but will instead over time become “label”.

Sure sure, we need consider what Redmond will standardize on, but from what I’ve seen of IE7, etc., they’re playing a game of catch up and will do whatever the consumer market standardizes on first. (Imagine that… what happened to that whole bit about needing a monopoly to innovate? Guess that didn’t work out after all, eh guys?)

Anyway, Flickr has tags, delicious has tags, ‘rati has tags and most other Web Two projects seem to support tags… so when Google goes the other way and pushes labels, seems we ought to pay attention.

Mind you I’m not advocating one or the other or suggesting that we all change course now (especially within Flock), but instead proposing that we think seriously about this now before the rift between the two starts to hit teh long tail and we have massive confusion between one term and another.

Tom Raftery catches me in the AM

Factory RockstarThat spikey Irish-bloke Tom Raftery (who I met at Les Blogs) interviewed me the other morning.

A little poppy, but y’know, might be worth a listen if you’re into sadomasochism and listening to a web geek waxing intelligent floats your ship.

Anyway, a podcast that smells like bacon must be good and Tom does well grilling me on Flock, Web Two Dot Oh, and software that I’d marry (are you listening, Jitkoff?). I also go off the deep end about DRM and robot take-overs and say something in French that someone else told me to say. I mean, it was like 8:00am, gimme a break.

send_pings and losing my innocense

Sleight of handI’m writing this post with some real hesitance, feeling like I’ve just stepped into a cigar-smoke filled backroom with the bunch of thugs who really run this town… and they’re pulling out their tommy guns to take me out as I’m frantically trying to write this.

Heh. 

Yeah, I tend to get a bit melodramatic when I write, but this time I really feel like I’m tossing it on the line… I mean, this is my job I’m talking about here and though I’ve feigned to be so direct before, this issue cuts at the heart of the work that I’m doing. And fuck if I feel like a piece of me is dying as a result of this.

Darin posted yesterday about a new ping attribute being added to link anchors in the trunk builds in Firefox. Basically links that used to look like this:

<a href="http://flock.com">Flock</a>

can now be written like this:

<a href="http://flock.com" ping="http://myeviltracker.com?source=factoryjoe.com/blog">Flock</a>

The result? Well, hover over the link and you’ll get a handy little status bar message telling you that Firefox is about to open (in this case) flock.com as it silently pings myeviltracker.com in the background. The benefit to you? Well, supposedly because you’re no longer visiting the redirection sites prior to hitting your final destination, pages will be perceived as loading faster. Whoopee.

At least, that’s the idea as spec’d by the WhatWG. Including it’s inherent evilness (see #4).

So why does this matter so much to me? Well, because I’m working on building a browser based on Firefox. Decisions made upstream obviously effect this work since the Mozilla technologies that power Firefox make up the core of Flock. And the decision to enable browser.send_pings by default trickles down to us. We inherit that decision and all the baggage and rationales that come with it. Including the impact on privacy.

I’m not so naive that I don’t recognize that all of our behavior is being tracked, analyzed and quanitified already, both online and off. (Hey, I saw the Matrix too!) But right now, as Hixie pointed out, it’s being done by advertisers via a series of obfuscated redirection URLs. Ever use a service like eBates? Notice the 5 or 10 servers that you’re bounced across before you land at the final page? This ping attribute is designed specifically to address that "problem"… to make landing on your final destination… smoother, faster.. more calming… wha? huh?

Sorry, I dozed off.

So while all the greedy hands in an online transaction will presumably be daylighted in the status bar (yeah, like they’ll all fit), it’s how this feature is being pushed through that scares the bejeebies out of me the most.

And dammit, I feel like more of my online childhood is being robbed from me. 

Think about it. Why is this feature being introduced? Who does it really help? Who does it really stand to benefit the most? Lemme give you a hint: it’s not you and it’s not me (despite what the proponents might say). Let me quote:

This change is being considered in large part because some very popular websites have asked for a solution to this problem.

Gee, can’t imagine which "very popular websites" those would be. Scoble, are you asking for features in competitor browsers again? C’mon man, we talked about that!

Oh wait, not that kind of popular… that kind of popular! As in… "all knowing, all seeing, all controlling"?

Oh oh, I get it; yes, exactly: to make tracking your behavior easier for advertisers.   

And here I thought the next name for Firefox would surely be Volksfoxen.

If the features of the next generation of browsers (Firefox 2 Alpha is just around the corner etc etc) are being driven by advertising, TBL help us.

I mean, sure, we’re trying to ask some serious questions about what the next 10 years of browsers look like too and we’re also funded by dudes with stogies in dimly-lit rooms (oh what, I’m not supposed to say that?), but, as far as I’m aware (remember, I’m young, dumb and naive), I haven’t been asking what the advertising industry has on its wishlist when I design features. Nor the et al. Nor enterprise. And no, that hasn’t happened with Firefox just yet, but I’m just concerned that if we’re not vigilant, it might. (Hey,shuddup, it might!)

I mean, the future of the web that I’m interested in investing in doesn’t treat people as statistics to be quantified. No, instead it’s more about what they have to say, what their contributions to this massive jerky conversation pool might look like, what bit of brilliance they might shine on the web that will change my life forever. It’s happened a couple times already and it didn’t result from monetizing the web better.

This send_pings feature reeks of special interests. So hey yeah, just because we’re downstream doesn’t mean we’ve gotta accept everything that trickles down. Insomuch as I’ve yet to be convinced that this feature doesn’t do anything to humanize the web or improve web standards, or help people communicate better, I’m moving to keep it from landing as default "on" in Flock. Call me a luddite, fine, but bug logged. Consequences, well… be damned.

The Case for Community Marks

Executive summary: In recommending the establishment of Community Marks, I propose that an alternative to trademarks is needed for community-based projects like Bar Camp and Microformats. The need for Community Marks stems from the non-commercial focus of these projects and the way these projects spread virally on the web. While we need to protect the integrity of a brand like Bar Camp, licensing and legal enforcement is too costly in terms of time and money to make sense for loosely joined communities. Therefore, if we can leave enforcement up to the community via the Community Marks denotation, we will be able to serve the vital function of identifying a community’s work and projects without burdening that community with undue legal process and enforcement costs.

Community Mark You can’t imagine how excited I am to write this post… not only is it an important one, but I’ve just gotten my busted laptop back and wow (is this bad?) I feel like I have my life back again. Never really thought I’d say such a thing, but eet’s true I teenk.

So I’ve been discussing the idea of Community Marks with a wide number of folks for some time (starting back when I was working on Spread Firefox and preemptively released the hi-res versions of the Firefox logo before I had full authority (that post has since been taken down)). I believe that this idea is an important tool which has grown out of the emergent philosophy that I see in the camps and in community-directed, “unowned” projects like Microformats.

Let’s get into it: I’m not a lawyer and I will never pretend to be, but that doesn’t really matter as far as I’m concerned and I’ll tell you why.

When it comes down to it, law is totally made up by humans. It’s just a system of conventions that codify certain beliefs about morality and righteousness within the context of a given civilization, society or group.

Laws weren’t and aren’t always penned in Congress, either. In fact, unbeknownst to most school children, that timeless classic that tells of the “life of a bill” is simply a story that you can choose to agree or disagree with. For the purpose of this discussion, I disagree with its fundamental premise that all laws (and rules governing trade and so on) must go through that process to become “real” or as enforceable as any other law.

Sure, this could be an academic or artistic inquiry on my part, whatev, that’s fine. Today, I’m interested in a little armchair-legislation, the kind that has no teeth or legal basis in our current legal system, but nevertheless solves an important need with which existing law currently doesn’t deal: the need for community owned and enforced marks (as in an open alternative to trademarks).

I won’t belabor where this all came from, but suffice it to say that the SpreadSpread campaigns (Spread Firefox, et al) have repeatedly encountered problems when commercially valuable trademarks need to be put in the hands of a community and the public domain is not an option.

The view heretofore has been that this is necessary, with dubious restrictions that protect the ability of the trademark owner to enforce their brand and indeed ensure the perceived quality that their logo, wordmark or servicemark represents.

In the case of Firefox or Flock, even though they are the result of countless hours of volunteer effort, you still need to be able to prevent some nefarious hacker in the remote expanses of cyberspace from releasing a spyware-laden version of either browser and calling it by the name of the official binary. Allowing such behavior could conceivably cause confusion in the mind of the consumer and potentially lead to an economic impact on the brand’s reputation. Therefore, it would be legitimate (and legal) for either Flock or Firefox to go after the offender and stop them from continuing such behavior. Just check out the on the lengths one can go to protect their IP in such a situation. Seriously.

And that’s why trademark was created: to make sure the people who own a brand can enforce their dominion over it to keep making money off it unfettered.

Um..

I mean.. uh… “to guarantee the integrity of a brand’s goods or services in order to prevent confusion in the marketplace.” (Stupid Freudian slips!)

So anyway, that’s all good and well, but it’s not enough. And it doesn’t address the issue I’m trying to resolve: the need for a mark that is owned, operated and enforced by a community that isn’t driven by purely economic interest. Instead, the motivation derives from the desire to uniformly represent their work product as the output of a specific community. Period.

So the case for community marks is primarily necessitated by projects like Bar Camp, which collectively is the product of scattered cadres of individuals the world over who take ownership of the brand on behalf of the larger community. None own the name or mark outright, instead they agree to hold an event based on Bar Camp, espousing its primary principles; in that way, they are extending the reach of the mark and therefore have earned a de facto license to use the Bar Camp logo and moniker. Now, should another separate event be created with primarily commercial gain in mind that uses the Bar Camp brand and co-opts the integrity of the name, it would be up to the community to go after and enforce the brand, either through blogging, boycotting or other subversive means. We simply don’t have the financial or temporal resources to go after such an offender, but we do have a small army whose response could be economically devastating to that effort.

I mean, let’s look at two precedents here: Creative Commons and Microformats.

With Creative Commons, you’ve got this idea that maybe not everything needs to be owned exclusively by default… Maybe you can allow for some distributed ownership of intellectual work in order to grease subsequent derivative creative expression. And maybe both the community and the original author will see benefits.

With Microformats, they’re leveraging community behavior to standardize the way we mark up our documents for the benefit of everyone. No one owns Microformats, though Tantek et al do a pretty good job shepherding the community. Nevertheless, the result of their work is something that the community takes pride in, identifies with, would be willing to expend individual effort to defend the integrity of.

And we learn two more things from them: to solve human problems as a primary objective and second to pave the paths of existing behavior. Don’t reinvent everything all the time. Just do what’s simple; just codify what’s already being done.

And gee, we’ve come full circle haven’t we?

Microformats are basically mini-laws for marking up your documents. Hell, go ahead and break them, do your own thing, there’s no punishment because the community doesn’t see punishment as being in line with its sense of justice. But joining up and following the rules, in this case, will actually bring you some benefits and not to mention, make your life (if you’re a user of the web, anyway) a little bit better.

So let’s codify this need to represent community works in a common mark. I want to be able to put a stamp on the work that I do within a community that identifies it to the world — that says: Me and a buncha folks made this and we’re proud of it. We did it not to make money but out of passion and love and because it’s in our nature to create without secondary purposes in mind.

And then let’s call it a Community Mark to make it clear what’s driving our purpose. It’s not tradeit’s the community, stupid! And from now on, if you want to create your own Community Mark, just slap a CM on your mark and hope for the best. Hell, we can’t enforce these things unless we hand them over to a broader community anyway — and since it’s really the community that owns the mark anyway, who better to look out for their wellbeing?

It’s an email, email, email world

I had a very useful and informative call last night with some folks from the Portland Usability group, organized by Frank Spillers of Demystifying Usability (a recording of the event is available for the next month). They had a lot of really useful feedback as they walked through the Developer Preview of Flock, explaining their expectations of certain interface elements and expressing confusion when they couldn’t figure out what terminology like “Star this page” meant or what a “Shelf” might be used for. Feature discoverability was another big problem; for example, they really thought that the history search was an awesome feature… but only once they found it!

On the one hand, a lot of the that I’ve been doing since we launched our Preview Release was validated. Much of the confusion they experienced has been addressed and hopefully resolved, though I look forward to doing more of these events both prior to and after each major release.

And since I was also able to give a high-level overview of where we’re going with Flock and what our vision of the web looks like (more sharing of timely “me-created” content than static-library-lookup-information old skoolness), they were able to point out aspects of Flock that didn’t seem to fit that vision — many areas, again, that we’ve been actively working on.

One thing that I didn’t expect — and this is more due to my own developeresque myopia than anything else — was that sharing to the group implied email! Yeah yeah, I know, what? Of the six people involved (albeit a small sample but nevertheless of fairly technology-familiar folks) only one knew of Del.icio.us… and that was Frank, the organizer. I purposefully chose not to explain what delicious was before we got started, instead interested to see how the group might discover or at some point desire “bookmark sharing”. Well, that never happened. At least in Flock (chalk one up for the Firefox del.icio.us extension).

Everytime they thought of sharing, they instantly turned to email (only Frank had previously blogged as well). So we’d get flows like this: Create a collection… Ok, want to share? “Oh, right click and email it!” Create a snippet in the shelf… Ok, want to share? “Oh, right click and email it!” And so on.

This was fascinating feedback. Apparently we have much to do to evangelize blogging, favorites sharing and similar socially-centric web services (Flickr had no traction with the group either) if we’re going to bring the benefits of Flock to folks who haven’t yet discovered that there’s a rich social social social world awaiting them!

…and yes, this really gave me even more enthusiasm for the direction that Flock is heading. We’re just a couple years ahead of the curve for the quote-unquote longtail, which honestly is a very very good place to be right now.