Monthly Archives: March 2004

SubEthaEdit and collaboration

meeting.painting

When these cooperative authoring things work is really is an amazing experience! You get this moment when it becomes clear that a collective effort can be orders of magnitude more powerful.

I’m sure we can all call up some sympathy for this quote.

“The wonderful collaboration I had hoped for had turned into a circus of bullshit.”

A couple dozen experiences of that kind and despair emerges. You get
cranky. So it’s important to drag out, admire, and try to pick apart a bit the cases where it works.

Tools do seem to be making a difference here. A good bug database, the optimistic concurancy design pattern used in CVS, even something as amazingly simple as SubEthaEdit. It gives one hope that some what seems so hard may only be a misunderstanding about how to frame up the work.

Maybe we should call a meeting :-).

mt.el

peg in hole

I’ve been messing around with mt.el (an emac mode for blog editing MovableType blogs) but currently it’s not working out just right. It appears that posting works, but when it retrieves the postings all the open angle brackets are converted to <. It appears that movable type is sending the postings back with converted like that and the xml.el or xml-rpc.el that I’m using aren’t in synch with that behavior.

I have been getting some nice help from the author of mt.el though.

Now I’m playing with ecto. It doesn’t like the unusual characters that appear in some of my postings. Those are a gift of Microsoft Word. Ecto’s editor is surprisingly simple.

Ecto is a little easier for setting up pictures than the vanilla MovableType web interface though.

Revealing, Authorities, Identity

Open systems thrive when contributors are encouraged to toss a little value into the pot. Stone soup and all that. Of course we all know that there are bad actors out there so if you run an open server your going to get evil contributions from bad actors. Open up your email address, your cell phone, your cooperative wiki, your blog comments and some twit is going to show up sooner or later posting porn, selling unregulated herbal remedies, and spraying rude graffiti on the walls.

Three solutions:

  • Authorize only trusted contributors.
  • Moderate contributions via some trusted mechanism.
  • Maintain, i.e. trusted folks fix the damage after the fact.

So it’s all about trust, authentication, etc. etc.

Problem is that we only know how to solve that problem in one way. The contributor must reveal something to us, so we can authenticate him, and we need to have some central authority that vouches for the guy.

Those two terms are trouble:

  • Reveal
  • Central Authority

Those two goes a long way toward explaining why the Internet identity problem is so hard. On the one hand the solution needs to enable revealing (which sounds a lot like privacy intrusion, embarrassment, and identity theft) and on the other it needs to enable the emergence of central authorities (which sounds a lot like authoritarian police state, abusive monopoly, and single point of failure).

This stuff just doesn’t conform well to the end-to-end principle. Sure, sure, you can run your own “authority” out at the edge. Your blog, wiki, email client, can sit there infer the trustworthiness of your contributors from various implicit and explicit info. That’s all well and good but it’s socially dysfunctional.

People are social creatures. They project a personality. They manifest assorted behaviors and attributes so that we can construct a model of them. A world where everyone is totally anonymous is just bizarre.

Worse is that solving this problem at the edges means that trust and reputation isn’t fungible. Not fungible means lock-in and hence increased power-law reinforcement. Not good. Why spend time contributing to dinky open source project when you could spend the time contributing to famous project and hence gain a reputation that’s “worth something?” Let’s say it takes 10 good postings at Bob’s community before I’m allowed to post without moderation and join in the discussion. Once I’ve climbed over that barrier why would I bother to go join Sam’s community?

This doesn’t make for an open system, this makes for a compartmentalized system.

Now I’m not arguing that reputation can be fungible like ounces of gold; but I am arguing that a design that declares that reputation shouldn’t be fungible from the get go is wrong.

So this is the rub. We have a problem that demands that we figure out how to design the central authorities in a manner that avoids them becoming too powerful – we know a lot about that. We have a problem that demands that we empower the users to reveal what they wish to reveal.

It’s just blind foolishness that pretends we can design a system with no authorities and no revealing. Worse is to believe that systems of that kind encourage a more open system. Open system thrive on having complex porus membranes. No membrane is fatal.

Liberty Momenteum?

I consider this a very health sign that the Liberty Alliance specs for solving the problem allowing users and firms to manage the authentication, data sharing and privacy problems might just be getting some traction.

Automaker General Motors Corp. has just completed a successful pilot with a 401(k) retirement-services provider as part of a plan to link its employee intranet portal, called Socrates, with a variety of employee-benefit service providers, says Rich Taggart, director of enterprise architecture. The technical part, based on Liberty Alliance specs, wasn’t hard. “That part of it went rather well,” he says. “Everything is very interoperable.”

Momenteum is a key aspect of an emerging standard. While there are lots of phases in building the momenteum of a thing like this. For example getting big names to throw their reputation on the bandwagon. Short of standardized-exchanges/second the most significant sign is actual adoption. So it’s very encouraging seeing people talking about that.

The real challenge was getting both companies comfortable with the idea of linking their systems, so when an employee logs on to the GM portal, he or she is automatically able to access the financial-services provider’s systems as well. There were lots of discussions over “the comfort level of doing this and how it could affect the business relationship and relationship with the employee,” Taggart says. There were lots of conversations between legal groups, he adds.”

Indeed. This problem is very hard and deserves a good open solution. I am quite encouraged by the Liberty designs. We may actually get something that addresses everybodies concerns.

Full disclosure: I have had a tiny part in the Liberty project.

Negotiation Stages

Three phases of creating a public good.

  • Getting the parties into the room.
  • Reaching a bargain: Keeping the parties in the room.
  • Maintaining the agreement after the fact.

In the first stage the key is to find sufficient common cause that the parties are willing to invest in the enterprise. I can’t count how many meetings I’ve attended where some people thought they were at the second stage, since they were in a room, but in fact they were still in the first stage.

In the second stage the key is to know what’s fungible. The challenge is to search for things that can be rearranged. Again I’ve often gotten people in a room only to discover that all the resources are immovable. At that point you need to revisit the urgency of the situation.

The first and third stage are curious because both of them depend upon a common understanding about how things work. A commitment to along term agreement and it’s maintenance over time.

I’m amused by the parallel that can be drawn between these other triplets: exit, voice,and locality; or culture, market, structure.

See also: Getting to yes

Coney Island

This picture is a tiny bit of a drawing of the beach at Coney Island by Reginald Marsh.

push.png

While this picture is a tiny bit of a painting of the beach at Coney Island by Paul Cadmus.


cadmusBeachBit.jpg

I love art that shows crowds or urban life.

Fighting the last war.

This
is outrageous.

“I blame the entire Bush leadership for
continuing to work on Cold War issues when they back in power in
2001. It was as though they were preserved in amber from when they
left office eight years earlier. They came back. They wanted to work
on the same issues right away: Iraq, Star Wars. Not new issues, the
new threats that had developed over the preceding eight years.”

Please! Read
the entire thing.

Project Rights

This is a list of various “rights” regarding projects that firms need to allocate to one or more parties. That’s a design problem that when poorly solved leads to too much or too little conflict. I gleaned this list from a paper I was reading yesterday (thanks Karim).

  • Right to make decisions
  • Right to initiate projects.
  • Right to ratify projects.
  • Right to implement projects
  • Right to monitor projects.
  • Right to evaluate projects.
  • Rights to own or capture the residuals created by projects.
  • Rights to stop projects.

Most institutions are in a continually renegotiating these things; it’s exhausting. Most of the literature on stage gates is an attempt to provide people with a template for taking the conflicts implicit and by proscribing a ritualized version of them reduce the amount of resources expended renegotiating them.

The paper gets to talking about what I call “swooping;” i.e. where management swoops down like a seagull grabs your dinner out of your hand and takes a crap on your head. In the paper it’s call “selective intervention.” The problem with swooping is that it causes the subordinates to raise their hurdle rate and back off their investment in the task at hand. Stage gates are, for all there many flaws, a way to try and frame up a contract about swooping, monitoring, evaluating.

I’m forever fascinated by how hard it can be to get the right to stop a project.

Stallman and Gates!

Interviewer: Is studying computer science the best way to prepare to be a programmer?

Gates: No, the best way to prepare is to write programs, and to study great programs that other people have written. In my case, I went to the garbage cans at the Computer Science Center and I fished out listings of their operating systems.

You’ve got to be willing to read other people’s code, and then write your own, then have other people review your code. You’ve got to want to be in this incredible feedback loop where you get the world-class people to tell you what you’re doing wrong.

This wonderful snippet was revealed by Dan Bricklin and found in the old book Programmers at Work. Spread the news.