JPU — Just Plain Useful — tools for the Mac have been updated recently. Haven’t tried them, but might be worth a look: first, Aquaticprime is a free, open-source secure registration method for shareware applications; second, Sparkle, which is “a module that developers can stick in their Cocoa applications to get instant self-update functionality”.
Category: I care about…
Event In a Suitcase and Running Remote S5 Presentations
Continuing the tradition of the “Event in a…” meme, we came up with the notion of “Event in a Suitcase” at the most recent Mash Pit.
The idea is pretty simple: make it easy to walk into a room and make a presentation.
Well, among the five of us, we came to the conclusion that there’s nothing really that makes it easy. There are tools, both hardware and software, that make it possible, and writing them down was a good place to start from. But there really isn’t an open source or free workflow that gets us where we want to be… where everything is affordable and fits in a literal suitcase.
So anyway, we documented our work and could use more help. If you’ve got ideas, tools, solutions, workflows or whatever, add them!
· · ·
So, one of the cool hacks that we brainstormed and that Kevin Marks was actually able to implement before the day was out involved Eric Meyer’s public domain slideshow format S5. Essentially he made it possible for people watching an S5 presentation, like Tantek’s excellent Building Blocks for Independent, to see the slides change as the presenter changes them.
Of course bringing this awesome hack together with a Gizmo call-in means that people can at least watch and listen remotely as presentation happens — and participate in IRC. So voila, it’s like NetMeeting, but open source! Anyway, Kevin’s code is in Twisted and now that I’ve blogged this, hopefully he’ll be incented to clean it up and publish it!
ClaimID makes the OpenID connection
I have to say that it’s things like this that really make me shiver with excitement…
I mean, it’s pretty simple, but it’s also pretty important.
What’s the big deal? Well, for one thing, it’s yet another site adopting OpenID, a decentralized identity system. And, as more and more sites adopt this system (which should remain transparent to end-users if they don’t want an OpenID), we near ever-closer to a lightweight, single sign-on solution.
To be sure, OpenID isn’t a panacea. It’s not intended to be one. The primary attractiveness of OpenID is its simplicity: it’s decoupled the issue of trust from identity and simply offers a way of staking your identity to a given URL. In a sense, if you can trust the credentials of Website X, then you (as a web service provider) can trust accounts created on that domain as well. The benefit for the account holder is that they don’t have to re-register on Website Y.
Note that this is a web-centric solution and doesn’t carry well into the real world where people don’t identify themselves by URLs (hmm, what if instead of a social security number, we were assigned a URL at birth? whoa.).
The other thing that’s great about this announcement is that it’s the work of Scott Kveton’s new startup, JanRain. I brought Scott and Terrell Russell together some time ago, so it’s awesome to see the fruits of this connection already — and that Scott’s going off to do this kind of work full-time.
What I want to see? Well, the proliferation of OpenID across all the various sites that I use. The cost is minimal since the libraries are being developed on all kinds of platforms — and it should integrate fairly well with existing login schemes. Then I want to see either Ma.gnolia or ClaimID add support for XFN (they already support hCards and ClaimID allows for custom rel values). Then, of course, we need to be able to string together (loosely coupled, mind you) my contact list and my group membership list so that I can import and export them wherever I go (obviously this should be done with microformats). Once we’ve got that situation fleshed out, and I’ve claimed my sites with either MicroID or (preferrably) rel=me, I’ll have a pretty portable social network to carry around the web!
Yahoo! Local goes Cuckoo for CoCo Puffs!
The title means nothing, but today at Supernova, Andy Baio announced that Yahoo! Local has added support across the board for hCard, hCalendar and hReview, following Flickr, Upcoming and Yahoo! Tech (blurry video 1, video 2 — turn it up!).
I can’t exactly say what adding 10s of millions of microformatted bits of data will do for the web, but it certainly makes the rush to develop UI around this new opportunity all the greater…
Oh, and bonus: when I was at Flock, I wanted to see ground-level integration of microformats in the browser. Imagine having Lucene indexing all the microformatted content that you come across on the web (whether you know it or not) and then having that data separated out for use in extensions, in filling out forms, in generating new cross-sections and views of your ‘history’. And Rohit gave me another side of that idea: being able to autofill forms anywhere by creating an index of microformat classes-to-input value pairs for specific websites… Yeah, the client/browser part is going to be key to making all this work have obvious value for folks on the web. Can’t wait to see how this moves forward.
MashPit by day, Microformats by night
Today I’ll be hosting the third Mash Pit in San Francisco at the Wharton West, downtown at 101 Howard Street, Suite 500. Things kick off at 10am and go until 5pm (not 6pm, necessitated by the facilities and the fact that we’ll be hungry!).
What can you expect? Well, it’s pretty simple. The goal of the day is work on mashups — particularly ones that work on solving “human problems” — like making it easier to find wifi cafes in the city or autotag your photos based on your Upcoming or EVDB account (which, by the way, is really about making it easier to help folks find your photos later).
Tara and I came up with the agenda this morning. We’ve got a bit of experience now, so we’ll see how it goes!
And of course, after this is all over, tonight is the Microformats 1-year Anniversary Party at 111 Minna. We’re pretty excited about how far this little fledgling community project has come in the last year and want to celebrate! It gets going around 8pm — and, if you can’t be there, you can always order a shirt!
Ah! And before I forget, a big thanks to Tara, Tantek, the Supernova folks (especially Kevin and Jeanne!), and Mozes for helping make Mash Pit possible!
Drupal founder coming to San Francisco
Dries has announced a trip to San Francisco from June 25-30. Surely we’ll have to make sure he gets to meet all the fine folks in our community while he’s in town!
The future of open leadership
With the Feed Icon Trademark debate, I’ve become fascinated by a number of Mitchell Baker‘s recent posts on open source leadership (or perhaps more appropriately community stewardship).
Just last night we held our second coworking meeting to discuss a number of topics (of which we were able to plow through very few)… Key among them was the question of how to best open up the space for non-anchors while not overly burdening the existing key-holders. And, in opening up the space, how to we set a fair pay-for-the-time-you-use rate that doesn’t burden the project with excessive overhead or rules.
After an exhausting discussion for over an hour and a half, we had to adjourn the meeting following Brad’s Snooze Button Guideline. We covered quite a number of possibilities, from hourly rates to hosting quarterly “supporters”, but ultimately ended up without a final resolution other than to submit proposals to the mailing list for continued debate.
Here’s what’s strange about it: throughout the meeting (I can’t be sure but…) I did feel like I was sitting in the role of facilitator — not exactly the leader, but close enough. I mean, that’s a pretty common role to play, right? Most meetings need a leader of sorts, right?
So now the question that I have is, or perhaps what I’m most confused about, is what kind of leadership does the coworking project need? What kind can it stand? I agree with Mitchell that relying on the “community to decide” will moreoften than not result in disappointment or frustration for communities actually don’t decide anything, they only appear to make decisions. And yet, there is this apparent allergy in open source communities that forces the subversion of the ego and the consequent vilification of those who attempt to make a decision on behalf of the group.
Ian responds to Mitchell:
Good leaders do not make decisions – they simply help the community to make better decisions. To do this they listen well, and they think long and hard. Then, when they see the prevailing wisdom surface, they communicate those decisions more fruitfully.
…which sounds pretty good and egalitarian on the surface. In fact, not a bit unlike what they call representative government. And yet, I think that that only captures a fraction of what a leader, in the community context, really does.
It is my belief that good, reflective and responsive leadership is needed for any project to find success. But that leadership need not be hierarchical. Or dominant. Or, most of all, exclusively masculine. And it also can’t be cowardly or cow-tow to the imposing and voluminous voice of the community it serves. That’s why leadership is important; it’s not about power, it’s about clarity of purpose and of seeing things through to their desired conclusion, deterring that which threatens to scuttle the intentions of the group.
Case in point, the witch-hunt that O’Reilly recently survived suggests that communities can easily be turned into echo chambers for groupthink and channeled hostility. Without strong leadership, you’re liable to end up with a neverending succession of teapot tempests without accomplishing anything productive.
So, coming back to the meeting last night, we have goals in common, even if the path is not clear. Which is precisely the kind of opportunity in which leadership emerges — the kind that isn’t focused in any one individual but is shared among the individuals in the collective. In a very real sense, it is the BarCamp model of leadership, of self-determination, of personal responsibility and of realizing your own role in consciously creating circumstances for yourself.
The point is this: open source leadership is not a contradiction, it’s just deeply misunderstood. And it seems high time that, as we open up to serving wider markets and communities, that we learn what it really means to embrace a kind of leadership that does not rely on traditional concentrations of power or of exclusivity or malevolent competition, but instead works to helps us each reach beyond ourselves to reveal each our own potentials. I don’t know clearly what it looks like, but I do think that Mitchell is on to something and that somehow, this little coworking experiment of ours might bring us steps closer to discovering just how open, modern leadership will actually bring us forward.
Flock 0.7 in the wild
Flock has released its first public beta after many moons of rough ride’em development. Out of the box, things look pretty smokin’, but I still think Flock has a ways to go before becoming the next generation browser (and of course, I’m only consistently hard on the things I care most about).
With a brand new (Drupal-based!) website from Facebook UI designer and design rockstar Bryan Veloso, the Flock project is starting to look like something, and they’ve certainly brought it along considerably since I left in March. Whether they will really pioneer novel interfaces and inspire new thinking on how the browser can better democratize the more compelling social aspects of the web remains to be seen. As they say, Rome wasn’t build in a day; then again, by Rome 0.7, I wonder if a broader foundation would have needed to have been built for Rome 1.0 to become as great and powerful as it did. Time will tell, won’t it? Time will tell…
All in all, congrats to the team — I remain eager to see what’ll come next.
Patent the baby, trademark the bathwater
If you take anything away from the second trademark brouhaha in as many weeks, it’s this quote from Mozilla Chief Lizard wrangler, Mitchell Baker:
I believe the Free and Open Source Software world is due for a long discussion of trademarks, how we use them, what their value is and so on. Ultimately I’d like to see some Creative Commons type options available for trademark- type purposes. (Creative Commons licenses are all copyright licenses, and do not purport to address the trademark – like issues of providing clarity to consumers about what consumers are getting.) We haven’t had this discussion yet.
So obviously, this points to the discussion I’ve been waging towards the establishment of something akin to the Community Mark idea. It’s not that trademark should necessarily go away; instead it’s about providing a choice when traditional trademark law simply does not make sense and only stands to incense and divide communities — which, ironically, such laws were intended to protect.
I don’t think the question in this case really revolves around the question of the meaning of icons so much as the enforcement and consistent use of symbols that come to mean something to a given community. For what Mitchell is really proposing is something more like reverse trademark, where you compel someone to use your mark in a certain way in order to produce consistency. Let’s face it, by restricting the use of the mark or icon, you’re actually moving away from your goal, which in this case is to establish a symbol, to be used in common, to identify a particular interface interaction.
It doesn’t seem like trademark is the appropriate means to the end in this case… and I’m very happy that Mitchell has proposed that the best solution is likely her option #3, “to try a less formal process with more authority resided in community norms and [see] how that works.” This is, I believe, the only true option that stands a chance of gaining widespread adoption as well as heading off the kind of scorn and antipathy that members of the open source community simply don’t need.
I am a citizen and I have agency
So in case you missed it, Tara left Riya very recently, following a trend that’s at least a couple months old (but blowing out recently).
The obvious question is: “what comes next?”
Well, without much time and without much hesitation (which means going on the sense in our collective gut, which our worldly president espouses), we decided to take the plunge and start our own consorgency.
We’re calling it Citizen Agency. And we’re still trying to figure out what we’re gunna shape it into… but we’ve got some initial ideas.
The name was spontaneous to be sure, as we’re on a tight deadline to get this thing launched, but it captures some of the important organizing principles behind what we’re doing. And of course, no good project or idea is without a kickoff track to its soundtrack… so, substitute “Patriot” with “Citizen” in the eponymous song by Pearl Jam and a picture starts to emerge:
And I ain’t no communist
And I ain’t no socialist
And I ain’t no capitalist
And I ain’t no imperialist
And I ain’t no democrat
I sure ain’t no republican either
I only know one party, and that is freedom
Whatever this thing we’re building is, it’s gunna be consistent with everything that’s lead to our shared success so far, including starting with a community model and building it out through channels that respect the dignity of our consorgents and partners.
Ah, and if you have an idea of what kind of symbol might represent this idea, we’re all eyes.



