The atmosphere of community

Hurricane Katrina Satellite Image
Photo shared by Glenn Letham under a Creative Commons License.

Was thinking over the Digg and Flickr hub bubs and had an observation.

For one thing, Kathy Sierra’s mediocrity index comes to mind — where you’re either at both ends of being loved and hated (to greater and lesser degrees) or you’re in the middle, and frankly, no one cares.

There’s something else that’s missing from that graph though… part of it is helping to prepare community builders and managers for what happens when you get a surge in one direction or the other… and the other part is what leads you to climb outwards, in either direction.

I might propose a natural phenomenon to be considered here, and that is the phenomenon of atmosphere and the weather that results by being contained in this protective particle shell.

Without atmosphere, you’re a dead planet — there’s no oxygen, the conditions are extremely harsh and barren, and life simply cannot thrive.

Too much atmosphere and you get global warming effects — things like “community algae blooms” where too much life is created too quickly and the internal ecosystems break down because they buckle under the weight of the increasing resource demands… we are living in a period similar to this today (also, think spam!).

Now, the sweet spot — where systems are in harmony and life is able to sustain isn’t necessarily a walk in the park. Under these conditions you definitely get weather — and that weather can be destructive, can come on unexpectedly and worse, can ultimate change the landscape forever.

From a community building standpoint, this is the kind of weather that you need to be extremely careful of, because these tempests in teapots can wreak havoc on the livelihood of your broader community ecosystem and can do untold damage if you’re unprepared when it happens. The strategy to take varies on the kind of weather we’re talking about, and whether you’ve conjured it up by something you’ve done or whether external factors are to blame.

A couple examples: Digg’s founder Kevin Rose declares the end of the Top Diggers list… Flickr declares their acquisition by Yahoo… 18 months later, they announce the termination of independent Flickr accounts… The Wikipedia co-founder breaks off to establish his own competing project called Citizendium… Mozilla revenues are flat after earning upwards of $80M the previous year… The Flock founders leave in semi-rapid succession… BarCamp is planned and executed in a span of 6 days “changing the way we think about, organize, and participate in technology conferences“.

All of these events bear an interesting semblance to what I might call social weather patterns: moments in time when a tropical storm could have made the shift from a benign warm rain into a destructive gale force hurricane at a moment’s notice. Also consider tremors and earthquakes as coming from within, typically along well known social fault lines where some well known controversy erupts and shakes the pillars of the community. In some cases, these shifts have happened, taking out entire communities or leading to the crumbling of support infrastructure or the dissolution of leadership causing people to flee for refuge in neighboring communities. These behaviors are all fairly well documented and established in the real world — but for once, because of the digital context I’m thinking on, we can see precisely that this weather is heavily influenced by us — a conversation of sorts that our environment is having with us and for us on a grand scale.

In any case, looking at Flickr in particular, there are lessons to be had.

In particular, Flickr decided to drill into a particularly well known fault line in the community and stirred up a minor tropical storm. They had prepared for it, however, and in the early hours of the storm, had staff manning the levee-forums as the first order of defense. Next came the blogger response with heavy winds and crashing waves — Stewart and others waded into the comments and attempted to diffuse any self-spiraling weather patterns. Finally, with the leadership and community infrastructure still firmly intact, the storm subsided into the sea (aside from a few stray lightning bursts) and things continued on as normal, as they should.

But this is not always the way things go down. And without proper preparation and an understanding of the goal of resiliency as opposed to domination, you’re likely to fare far worse under similar conditions.

So the greatest lesson from this is to consider the existence at the poles of Kathy’s index… to realize that stormy weather is a good thing, and a result of positively creating atmosphere — an excellent indicator that you’re alive and creating the conditions for life and for survival. Without weather, you’re probably dead; and with too much atmosphere, you’re probably suffocating your community, in which case, it could be too late to turn back anyway. Keep these things in mind as architect the foundations of your community — and remember that community isn’t warm and fuzzy all the time.

Trite

I hate to say it, but reflecting on my recent post on Flickr’s Ides of March, I can’t but help to think that talking a “digital bill of rights” is a bit trite, and seems wholly ignorant of the fact that a great number of people in other parts of the world still lack basic *offline* rights.

Way to think, poindexter. I can see you have your priorities straight.

Ho boy.

Making more sense of Flickr’s Ides of March

Yesterday I wrote a post that was admittedly vague and rambling. I definitely did not “go home” before I wrote it, so I’d like to correct that, and try to make my meaning clearer (and by “go home”, I’m using speaker trainer Lura Dolas‘ concept of being grounded and authentic before opening your mouth to say something).

So, if I were to rewrite my post, I might say something like this:

The account merger for Yahoo! and Flickr accounts on March 15 (the Ides of March) should not come as a surprise; indeed, we’ve known that it was coming for a long time.

What the deadline represents to different Flickr members is personal and unique; there is very little generalization that can be made of the event, except that the reactions vary greatly along a spectrum from utter indifference to downright anger and resentment.

What Flickr members are experiencing is consistent with what any passionate community experiences when something that represents the core of their experience is disturbed. Whether logical or not, it’s kind of like repotting a plant — the more sensitive to the environment, the more the transplant can be debilitating, destabilizing and disorienting. There’s no rhyme or reason per se, but the individual shock can be a challenge to overcome.

Anecdotally, my personal experience was rather blasé. Previously, I had maintained a “self-perceived independence” by not succumbing to the demands of the Yahoo! conglomerate and merging my account. Indeed, every time I signed in via the “old skool login”, I got a rush of silent pride that I was still free, having avoided “following the sheep”.

My resistance somehow guaranteed that I still had ultimate control over my destiny — and that no corporate monolith could tell me what to do — especially as long as I had trusted friends on the inside advocating for my right to free choice and free association.

But that was a temporary illusion that I knew in the back of my mind would someday end.

And yesterday, the jig was up, the mirage evaporating in the form of a FlickrMail: the embodiment of Flickr’s final transformation from a renegade underdog that busted convention and ran roughshod over a corporate hegemon to become yet another cog in the machine.

Or so the self-serving mythology goes.

In reality, I’m not so sure that all that much has changed, really. I am inclined not to make any final pronouncements about Flickr, Yahoo! or whatever else. Hell, I switched over my account, and it wasn’t that bad. Innocence lost, yadda yadda, the world carries on.

Now, the part that I want to take a moment to reflect on, which I also alluded to in the last two paragraphs of yesterday’s post (and is somewhat carried on here), is the part about managing, owning and making choices that effect the destiny of the identity (or identities) that one has spent time creating and cultivating online.

I would posit that the fear or fear-driven reactions that a lot of people have expressed or experienced in the past two days can be traced to this particular nugget of thinking.

What we lack online today is the equivalent of what we call human rights in the offline world. As it stands, Terms of Service are written foremost in the interest and protection of the Corporation. Thus individuals have little transformative recourse when things go wrong for the vocal are but few among millions.

As such, minority hold outs are left feeling particularly vulnerable and exposed. Especially in the case of Flickr, where people have developed visceral and almost human connections through the service, anything that threatens their “dominion” is an invasion that provokes an immune response by what I’d call the “proverbial community anti-bodies”, for better or worse.

In this case, Yahoo! — as the larger organism eclipsing the smaller — is perceived as effectively infusing its memetic DNA into the cultural neurology of the lesser system and without effective recourse to prevent this kind of “digital “, the anti-bodies lash out in response to the invading foreign agents, as you would expect in any system.

This dance is natural, is normal, and a simple part of biological and social evolution. In the scheme of things, I think the reaction of the minority does make sense here, even if it ultimately doesn’t matter that much. Given the current architecture of social networks, where your existence and environment is at the whim, pleasure and financial health of the network owner (let’s call her “God”), these kinds of decisions will continue to elicit strong social responses when God acts like… well… God.

Asides (lightly scrambled)

I do wonder, then, if this kind of personal exasperation would more quickly lead to the creation of “articles of digital personhood” or a collective “bill of digital human rights”. Or if, instead, it might drive the furtherance of independent identity services that promise to restore dominion over one’s online personas.

On a larger scale, will these experiences lead to the recognition of our digital selves as rights-weilding extensions of ourselves? Were there a “Digital Civil Liberties Union”, would those with grievances turn to such a centralized body for redress? or, rather than unionizing power, would they prefer to simply come and go as they pleased, as one does when she moves from one house to another, taking all her possessions and friendships with her but leaving the structure behind, and letting the market woo and serve her by playing to her desires and free will to choose?

Further reading

Bating the mousetrap with chunky peanut butter

Flickr peanut butter
Original by starpause kid and shared under a Creative Commons License.
When it comes to mousetraps, it’s fairly common knowledge that an effective cheese alternative for trapping mice is peanut butter.

However, we already know that Yahoo isn’t too fond of peanut butter. At least the smooth kind spread thin.

So it’s interesting to note that, perhaps as part of the strategy to outlaw renegade peanut butter within the organization, the formerly independent outpost known as Flickr will be forcing users to either merge or create a new Yahoo account to login after March 15:

On March 15th, 2007 we’ll be discontinuing the old email-based Flickr sign in system. From that point on, everyone will have to use a Yahoo! ID to sign in to Flickr.

We’re making this change now to simplify the sign in process in advance of several large projects launching this year, but some Flickr features and tools already require Yahoo! IDs for sign in — like the mobile site at m.flickr.com or the new Yahoo! Go program for mobiles, available at http://go.yahoo.com.

If you still sign in using the email-based Flickr system (here), you can make the switch at any time in the next few months, from today till the 15th. (After that day, you’ll be required to merge before you continue using your account.) To switch, start at this page: http://flickr.com/account/associate/

Complete details and answers to most common questions are available here: http://flickr.com/help/signin/

If you have questions or comments about signing in with a Yahoo! ID, speak up!

You can imagine that not everyone is happy about this, especially after the reaction the first time around:
Jimbo doesn't like it

Now, I’m not interested in opening old wounds. The Flickr folks have given plenty of notice about the coming changes (figure at least a month and a half if not the full 18 months since they were acquired) and of course are available for consolation, hand-holding and so forth.

Oh, and contrary to my tendency towards conspiracy theories, I’ll let Stewart debunk them outright:

And that’s it: there’s no secret agenda here, no desire to come to your homes and steal your TV. Over time, it just gets more expensive to maintain independent means of authentication and we could “spend” those efforts on other things which make Flickr more useful, more fun, more versatile, etc. And the smaller the ratio of old skool to Y!ID-based gets, the harder it is to justify not spending that effort on improvements.

I will, however, take this opportunity to rise up on my soapbox again and point out something worth reflecting on…

Look, Google’s already done the same thing with Dodgeball; it’s a sure bet that they’re going to do the same thing with their YouTube acquisition. We know that Yahoo logins are going to show up on MyBlogLog and eventually, probably Upcoming too — and, for that matter, any other user-centered acquisition that comes down the pipe. Microsoft is no different. Let’s face it: the future of the web is in identity-based services. And this is a good thing, if you’re ready for it.

My buddies Brian Oberkirch and Aldo Castañeda talked about the potential for this new economy recently. It’s coming and it’s scary (for some) and it’s unclear what it looks like. But the more that this happens under authoritarian login regimes, the more concern I feel for the effect these consolidation efforts will have on true democratic choice in where and how you spend your attention.

Realistically, it’s not terribly surprising that Yahoo! and the rest are going this direction. Hell, from a systems perspective, you’re just two entries in a grand database in the sky whereas you could be one. From a service perspective, unifying “you” across systems allows convenience and synergies to emerge. The problem is that these actions belie the sophisticated relationships that some people have with their online accounts and how their personas are represented. Though not everyone cares a whole lot about their screennames, others absolutely do. And beyond that, for whatever reasons they have, some people simply do not want to go near Yahoo! — something they never thought would be a concern of theirs when they originally joined Flickr.

But there’s a curious reality to look at here.

While I call Flickr home (NIPSA’d and all), just as there is a vehicle to vent my individual frustrations to Flickr, those same vehicles and mechanisms are available to me to splinter off and build my own peanut-butter-rich outpost anew. The missing piece of the puzzle, however, is my identity. I can’t just pack up my digital self and move on… whichever login system Flickr uses — Yahoo’s, Google’s, their own — I can’t “take it with me”. Even with their API, which is one of the most generous in the biz, it still doesn’t give me the ability to fully reincarnate myself somewhere else.

Now, I could and would like to turn this into a pitch for OpenID, but I won’t, at least directly. The Yahoo! folks have already expressed their distaste for creating Just Another Identity Silo and I keep waiting for them to prove it. I don’t mind waiting a bit longer. The wheels of the OpenID community are already in motion and I don’t have to plead for acknowledgment from the powers that be. The truth is, there are only a few more sites that will fall. The truth is, we are only now beginning to realize the degree to which we are all exposed and what the reality of our transparent society looks like. And the truth is, we are only just beginning to wake up to the idea that we should and can have dominion over our online lives, just as we believe is our right offline.

Scoping XFN and identifying authoritative hcards

Before I can write up my proposal for transcending social networks, I need to clarify the originating and destination scopes of XFN links.

It’s currently understood that links describe personal relationships between two URLs.

Typically the endpoints of XFN links are URL-centric personal blogs (i.e. horsepigcow.com or tantek.com), but not always. And because we can’t always assume that the outgoing linker speaks for the whole URL, or that the destination linkee is all inclusive, we need a set of standard criteria to help us determine the intended scope of the originating linker.

Put another way, how can we better deduce who is XFN-linking to whom?

Let’s take a concrete example.

The established XFN protocol states that when I XFN-link from my blog at factoryjoe.com to horsepigcow.com, that I’m describing the relationship between me and Tara Hunt, and our blogs act as our online proxies. Readers of our blogs already know to equate factoryjoe.com with Chris Messina and horsepigcow.com with Tara Hunt, but how can computers tell?

Well, if you check our source code, you’ll find an hcard that describes our contact information — marked up in such a way that a computer can understand, “hey, this data represents a person!”

If only things were so simple though.

If I linked to Tara and there were only one hcard on the page, you could probably assume that that single hcard contained authoritative contact details for her since knowing that Tara blogs at horsepigcow.com there’d be a good chance that she put it there. Sure enough, in her case, the hcard on horsepigcow.com does represent Tara.

Now, flip that around and let’s have Tara XFN-link back to my blog. This time instead of one hcard, she’ll most certainly find more than one hcard, and, most perplexing of all, most are not me, but rather people for whom I’ve marked up as hcards in my blog posts.

So, if you’re a computer trying to make sense of this information to determine who Tara’s trying to link to, what are you to think? Which relationship is she trying to describe with her link?

Well, as a stop-gap measure that I think could be easily and universally adapted to add definitiveness to any arbitrary hcard at the end of an XFN link, I propose using the <address> tag. Not only has this been proposed before and not been overruled, but it is actually semantically appropriate. Furthermore, there are already at least a few examples in the wild, notably on my blog, Tara’s blog, and most importantly, Tantek’s.

Therefore, to create a definitive an authoritative hcard on any page, simply follow this example markup (note the self-referencing use of rel-me for good measure):

.code { border: 1px solid #ccc; list-style-type: decimal-leading-zero; padding: 5px; margin: 0; }
.code code { display: block; padding: 3px; margin-bottom: 0; }
.code li { background: #ddd; border: 1px solid #ccc; margin: 0 0 2px 2.2em; }

  1. <address class="vcard" id="hcard">
  2. <a href="https://factoryjoe.com/blog/contact/#hcard" rel="me" class="fn n">Chris Messina</a>.
  3. </address>

At the destination URL, include a fragment identifier (#hcard) for the hcard with the complete contact information and add rel-self in addition to rel-me (as per John Allsopp’s suggestion):

  1. <address class="vcard" id="hcard">
  2. <a href="https://factoryjoe.com/" rel="me self" class="fn n">Chris Messina</a>.
  3. </address>

This practice will primarily help identify who XFN-linkers intend to link to when pointing to a blog or URL with multiple hcards. In the event that no definitive hcard is discovered, the relationship can be recorded until later when the observing agent can piece together who owns the URL by analyzing secondary clues (rel-me or other hcards that point to the URL and claim it).

Oh, and I should note that from the standpoint of multi-author blogs, we should be able to scope XFN links to the author of the entry — with entry-author making this infinitely easier.

Can charging for comments stop spam?

Over on Tom Coates’ blog, ZF has a novel, if not somewhat outlandish, proposal for attacking the comment spam problem:

The real barrier to spam will have to be some sort of micropayment you have to make to post a comment. A good idea would be to have a checkbox associated with your identity – something like (a) give the money to the site owner, (b) donate it to offset carbon emissions, (c) give it to the Gates Foundation, or some such.

While this is an interesting idea, it could obviously be abused very quickly — and create an encumbrance that most folks might not be willing to put up with.

I wonder if we could take the same basic premise here — which is transaction based — and turn it on its side a bit…

What if, instead of forcing someone to pay someone else, we force them to pay themselves in order to comment?

I know, I know, wacky — but hear me out.

If I was charged, let’s say, five cents for every comment I wanted to make, I might reconsider making a spurious comment. If I was a spammer, well, I definitely wouldn’t be bothered… for two reasons, which I’ll get to in a moment.

But going back to that five cents — it could certainly add up over time, judging by my Co.mments feed. But, what if that payment simply went back to myself? What if I used Paypal or Google Checkout for the payment and simply roundtripped the money to myself? Taking it one step even further, what if there were no processing cost associated with this transaction? It would literally be like taking five cents from one pocket and putting the same nickel in the opposite pocket.

Why bother? Well, here’s why.

I would conjecture that not a lot of spammers would be willing to pay to comment to begin with — even at five cents, given the large volume of comments that they push, it would just be fiscally impossible. Second, PayPal has some of the most ridiculous and rigorous anti-spam and anti-fraud measures in place to guard against evil-doers and ne’er-do-wells. It’s not flawless, but heck, it’s backed up by the Fed whereas Akismet is not. And if a spammer wanted to go through the trouble of paying him or herself, well, they’d have to have a legitimate account with a name and address attached to make such a transaction go through. Somehow I highly doubt that that would be an attractive option for folks who prefer to lurk in the shadows and remain untraceable.

Oh, and bonus, it would be pretty hard to spoof given you’re paying yourself and not someone else. Even captcha wouldn’t be able to match the kind of deterrence this kind of system would afford!

Maybe? Am I totally off?

hResume is live on LinkedIn

Detecting hResume on LinkedIn

And the hits just keep on comin’.

I’m thrilled to be able to pass along Steve Ganz of LinkedIn‘s Twitter announcement (tweet?) of their support for hResume on LinkedIn (these tweets are becoming trendy!).

Brian Oberkirch is curious about the process they went through in applying microformats post facto — that is, without changing much of the existing codebase and design — and will have a podcast with Steve tomorrow on the topic. Personally I’m curious if they developed any best practices or conventions that might be passed on to other implementors that might improve the appearance and/or import/export of hResumes.

If you’ve been playing along, you’ll note that this is one of the first examples of a successful community-driven effort to create a microformat that wasn’t directly based on some existing RFC (like vcard and ical). Rather, a bunch of folks got together and pushed through the definition, research and iteration cycles and released a spec for the community to digest and expound upon.

Soon after, a WordPress plugin and a handy creator were released, Tails added support and then Emurse got hip: Elegant template has hResume support — long term planning, ya know? It’s your data, and we want to make it as flexible as possible..

I wrote about the importance of hResume in August:

Why is this better than going to Monster.com and others? Well, for one thing, you’re always in charge of your data, so instead of having to fill out forms on 40,000 different sites, you maintain your resume on your site and you update it once and then ping others to let them know that you’ve updated your resume. And, when people discover your resume, they come to you in a context that represents you and lets you stand out rather than blending into a sea of homogeneous-looking documents.

Similar threads have come up recently about XFN, hcard and OpenID on the OpenID mailing list and the possible crossover with hResume should not be ignored. When LinkedIn is already support hcard and XFN — it’s just a matter of time before they jump on OpenID and firmly plant themselves in the future of decentralized professional networks.

Oh, and the possibilities to accelerate candidate discovery for all those job boards shouldn’t be understated either.

The Burning Man trademark controversy

In this post I talk about the Burning Man trademark controversy and its ramifications for other community initiatives, for the community mark concept and then outline a few ideas relating to the advance of community-driven intellectual property.

Burning Man TM
Original uploaded by Sterling Ely and shared under a Creative Commons License.

Scott Beale has been keeping me up to date on the Burning Man trademark controversy and today Eugene Kim pinged me about the story hitting the Chron.

What’s so interesting and didactic about this controversy is that it embodies, on a grand scale, the kind of micro-controversies that open source communities have faced for a long time around intellectual property and trademark matters.

On the one hand, you have the folks from , the ones who put on the event, fearing corruption and abuse by commercial interests:

…about the idea raised in the lawsuit of putting the Burning Man name and image in the public domain. While the concept is interesting, the reality is that we’ve been fighting attempts by corporations to exploit the Burning Man name almost since the first day we set foot on the playa. Making Burning Man freely available to individuals who would only use it to make money would go against everything all of us have worked for over the years. We will not let that happen.

On the other side, you’ve got folks, like John Law who filed the lawsuit, willing to embrace the chaos, as we often say, and let the market and — more importantly — the community — decide the brand’s fate (given certain conditions):

Burning Man belongs to everyone.

Burning Man is the sum of the efforts of the tens of thousands of people who have contributed to making Burning Man what it is.

The name Burning Man and all attendant trademarks, logos and trade dress do not belong to Larry Harvey alone or to Black Rock City LLC.

If they don’t belong to anyone, they belong to the public domain. If they are in the public domain, the event can still go on and the trademarks, logos and trade dress can still be used. But the event organizers don’t own those things and each and every one of the event participants are free to use these things as they want without permission or interference from the event organizers. There’s nothing to stop the party from being as big and wild as ever.

Then, of course, there are the corporate and commercial interests, who see a huge opportunity to capitalize on the value, reputation and attention-getting that the brand has generated over the years, who, according to reporter Steven T. Jones, envision MTV coverage, a burner clothing line from the Gap, Girls Gone Wild at Burning Man, billboards with Hummers driving past the Man, and other co-optations by corporations looking for a little countercultural cachet.

It’s unfortunate that when money starts changing hands, the original ethos and spirit of creation inevitably becomes undermined and damaged. I’ve seen this happen many times over — and when it doesn’t, it’s either because the commercial potential (the true measure of modern-day success in most circles) dissipates, or the community refuses to go down without a fight and relinquish dominion over the destiny of the project — of their creation.

But protecting the integrity of a community-built brand is a massive challenge for any collective — especially when protection isn’t exactly top of mind for most members of a group (ignoring the bystander effect). This kind of protective behavior is also, in many ways, antithetical to the type of free and open ethos that was so originally attractive. Thus, when things migrate from an ethos-driven commons to a commerce-driven economy, many of the original drivers for participation are subsumed by “maintenance- and protection-mode activities”.

This is something that Mozilla, Creative Commons, BarCamp, Microformats</a, OpenID, Tribe and others have and will continue to deal with. Thus given my experiences, I’ve been trying to express ideas for an alternative to trademark in the Community Mark concept, to varying degrees of success.

With this Burning Man situation starkly highlighting how nasty trademark disputes can get (and it’s only going to get worse for decentralized communities in the future, as the burners tend to be early pioneers of digital culture).

So, the question that remains to be considered here is what kind of moral code could be applied in this situation to mitigate the harmfulness of this dispute? — and for the future, what can similar community groups do to preserve their culture, their idealism and their connection with positivity and creativity when they begin to experience internal or external commercial interest?

Gollam: My PreciousIt’s long been my contention that, if the BarCamp mark should ever be co-opted (in that the community at large would lose effective dominion over the brand’s destiny — and we’ve had our brushes with disaster as well as ongoing and continuing controversies), that the brand and name should effectively be destroyed.

It is my opinion, perhaps naively so, that the health of the BarCamp community and resultant cultural productions are far more valuable and useful as contributions to the advancement of civilization than the name or the brand. And, the brand is really only as valuable as the community is healthy, so in my thinking, the nature and organic decay that might occur over time to the brand itself is to be embraced, accepted and allowed to run its course, even if it means that the original mark be abandoned or annihilated in the interest of preserving the sinews of the collective.

I think that John Law’s proposal to put the Burning Man mark into the public domain is an interesting one, and I would hope a genuine one. On the other hand, however, he contends that if the other two owners of the mark are going to continue raking in $8M a year running the business, he deserves his piece of the pie. Such is the insidious damnation of intellectual property:

If it’s a real fucking movement, they can give up control of the name, Law told the Guardian in the first interview he has given about Burning Man in years. If it’s going to be a movement, great. Or if it’s going to be a business, then it can be a business. But I own a part of that.

Now, I have two proposals of my own to make in this case, and they probably will not come as a surprise.

The first is a response to centralization and crystallization in and of communities — in other words, a way to address the stabilization, ordering or staleness of a community leading to its isolation, vulnerability and/or co-optation. As Ori Brafman has said, the best remedy and protection is disintegration, shattering the community into its original component parts, and the sending of those pieces to the wind to reformulate elsewhere, in a wholly new and unfamiliar form. This is actually the process of conflagration that signifies the ending of Burning Man every year and should be a salient reminder of the temporal nature of these constructs; indeed such renewal is necessary for the long term survival of the global organism.

The second proposal is more specific. I would like to append an escape clause to the current thinking on the Community Mark concept. Whereas the lifetime of a Community Mark shall be “as long as the community is willing to protect and uphold the integrity of the mark, and no longer”, I think it is necessary to also stipulate what happens to the brand after a disintegration event… and, as a sort of “living will” for the community to protect against the corrupting influences of consolidation-in-the-sole-interest-of-commerce… There may be two outcomes — one, that a community mark may end up unowned and in the public domain, whereby no single entity may lay claim to it; and the second: a kind of intellectual property black hole where the mark is Robert Paulsened — that is, completely erased from memory, never to be spoken of or invoked again, at least in the context of the original meaning. Instead, and in its void, a new entity may be created, but totally new, with no connection with the former, such that the restorative acts of creation can save the community from itself and from the destructive and minimizing effects that possession, consolidation and megalomania leads to.

So, I do hope and expect that the community of Burning Man can pull itself through this and beyond the stagnating grasp of commerce for the sake of commerce, but only time will tell. I imagine that the community is resilient enough to live through this and at the same time, hope that the rest of us are able to learn from the pain and anger that that community is now experiencing.