MySource, the next social worknet?

So it’s funny, but there are now two projects already that are being hosted in Google’s new open source environment that I want to “join” (requests are already in to the creators)… I wonder if, like Flickr groups, you’ll eventually be able to “join” GC projects — and be able to contribute and so forth…

This still doesn’t deal with the need for tools to enable non-code-writers to get involved in open-source (as is the goal of slow and effusive CivicForge) but the simplicity of the GC site makes it much more attractive to folks like me, who can’t stand the clutter and obnoxiousness of SF.

Oh, and in other news, SF is now allowing you to use external SVN repositories for your projects. Accelerated by the Google announcement? Methinks so.

Announcing VibeKit, the NetVibes desktop application

VibeKit

It’s pretty incredible when you can dream up an idea or an improvement in your flow one day and have it in your Applications folder the next, but that’s what happens when you run into cool kats like Chip Cuccio, the developer of Gcal and now VibeKit.

I got this message tonight:

http://www.odeo.com/flash/audio_player_standard_gray.swf
powered by ODEO

The point of the app is pretty simple: give me a stand-alone dashboard for all the web apps that I need to get to quickly that don’t have dedicated desktop-side apps (like PBWiki or Blinksale)… and that keeps me posted on what’s going on so that I’m not constantly switching from my Gmail tab to NetNewsWire to 1001. And so on.

VibeKit iconOh, and good news, it’s open source and supports Sparkle framework for software updates.

So get yourself a NetVibes account and download now (Universal binary)!

WordPress 2.0.4 rolls, Veloso joins Automattic

AvalonStarPress

Good stuff over at WordPress, with a security and “stuff” release, and a new addition to the Automattic family: Flockdotcom designer Bryan Veloso (aka AvalonStar).

First project for Bryan: implement Shuttle with support for Canvas.

Oh, and don’t forget to rub elbows at the upcoming WordCamp.

Backpack gets a calendar

Backpack Calendar

In case you hadn’t seen it (which I assume you have), Backpack now sports a shiny new calendar for organizing your life. Available for pay accounts only (it’s a measly $5 bucks for a basic account), the reviews seem pretty positive so far, even though I haven’t tried it yet. Personally if it’s less heavy and AJAX’d than Google’s implementation, I might be suaded to dish out some moola.

I mean, with Hiker on its way and voicemail for Backpack pages, why wouldn’t I try it?

Well… (and I respectfully disagree with Jason that iCal export is sufficient) hCalendar and hCard support would be a pretty sweet addition. But, as he correctly points out, I’m not really his target audience. Phooey. It’s such a drag when folks are adament about not doing what the early adopters demand. It’s like they have, I dunno, backbone or something.

DevJaVu, Google to offer open source project hosting

Don’t look now, but SourceForge has got 7-letter competition. Besides just funding open source development, Google is now in the business of providing hosting for it. To sign up for the service, a project needs to be licensed under one of seven approved licenses: Apache license, ArtisticLicense, GNU General Public License (GPL), Lesser General PublicLicense (LGPL), Mozilla License, BSD license, or MIT license.

Interestingly, data portability out of the service is an uncertainty at this point:

One of the most discussed topics at OSCON this year hasbeen open data — the ability for users to get their data out of aprogram or service and use it elsewhere. Stein says that Googleunderstands the importance of being able to move data. “We don’t havethose [migration features] in there now, but that’s something we intendto [have] … we intend to do it soon after launch.”

Devjavu_bannerThere is an alternative that fellow DevHouser Jeff Lindsay is working on, however, called DevJaVu — simply Trac and SVN hosting for a variety of projects and iniatives (currently in private beta). If PBWiki is any indication of the kind of stuff that comes out of this crew, DevJaVu seems like a perfect tool for the independent’s toolkit that won’t have your data stuck in the creeping grips of King Google.

SoylentGreenSpace v3 launches

Technorati Redesigns

My buddy Dave Sifry over at Technorati has launched v3 of Technorati, commemorating their three years as a company and as the interweb’s reigning whuffie tracker. However, the changes as I see them so far seem to represent a shift away from the Matrix-green-loving blog divas and digerati that have made Technorati their shrine towards a wider, and perchance less discerning, audience:

While we love expert bloggers, we’ve also spent a lot of time making Technorati understandable to normal people.

As long as normal doesn’t mean “mediocre” or “average” I guess I can see a need for this change — but my feeling already is that the new design is too Friendster-cum-MySpace than the good ol’ Technorati greenback of yore. Don’t get me wrong, I’ve been anticipating this redesign for some time — my concern though is: did they identify their audience correctly? …or am I feeling a bit snubbed because I’m not part of a presumably profitable demographic (profitable for advertisers that is)?

To be more positive (since I’m trying to make an effort lately!): the things that I am excited about in this milestone are taking place either behind the scenes or will only show value over time. For example, getting more accurate link counts and stats (which lately have varied between Technorati Mobile and the main site)… Consider the expanded popular page (whose URL should really be renamed to /popular)… or take a look at your personal page — certainly a lot more cluttered and riddled with things of little use to me personally, but at the same time showing the promise for someday becoming my electrocardiograph on the web. Oh, and the Favorites feature is an interesting not-too-del.icio.us-like addition that unfortunately doesn’t do anything better than NetNewsWire, Flock, Bloglines or others already do (popups?!) — so why not just integrate with those and offer me a remote view of feeds in context? (Especially since NetNewsWire syncs with NewsGator and has an open API that would make this process fairly trivial).

But Dave et al — here’s my plea and my challenge to you: in your efforts to grow your business and maintain your position as top of mind for what’s going on in the blogosphere, don’t forsake those who have championed you for so long in exchange for what looks like an opportunity to go massive. The long tail is chunky and has a richness that Technorati can help us all make sense of. In that way, Technorati should endeavor to become (hold your groans) the Flickr of Blogs — in the truest sense. When I come to Technorati, I don’t want only what’s popular, I want what’s good. And sure, “good” is in the eye of the beholder but frankly, if you take my earlier suggestion, then you’ve already got the data that you need to help me understand just what is good and relevant to me, rather than a broad swath of what’s out there and being linked to.

So Dave, think about it this way: when I come to Technorati as a blogger and as a registered user, I want Technorati to reorient and rebuild itself around me at the center. And I’ll tell you, every other blogger feels the same way. For the longest time, this is what Technorati offered to the world. Forgive us for being self-absorbed and echoic, but blogging works when you know who’s talking about and to you, so that you can respond — and as our ears to the ground, you offer an essential piece of the conversation toolset. Essentially, you provided me an inbox for my blog and for my second ego. I hope that, in orienting towards “normal people”, you don’t end up diminish what it is that puts the rati in Technorati.

CSS3 Columns loves me some Gutenberg 2.0

Multicolumn layouts in CSS3 -- Source: pathf.com

Apparently some work has been going on implementing columns as a CSS3 module. Trouble is, the approach is more related to newspapers and magazines of yesteryear than with the way the web works. How useful will this kind of thing be for my Blackberry? For highly interactive sites?

Sorry, admit it: tables are still the best structure for web layouts even if using them is a semantic bastardization. And until there’s a standard that emerges that is better, simpler and more semantic than tables, you’ll still find people arguing for their use in layouts.

Don’t get me wrong — I’ll never use tables for layout and can’t remember the last time I did, but the CSS3 draft seems so painfully out of touch with the realities of interface development for which tables are most often used (since when do you see an interface widget “flow” from Column A to Column B??) that this module seems focused on Tofu-style reading rather than making any real progress in the development of a richer interface layout language.

Browsers, the future thereof

Doug Engelbart

When I first realized the web as a medium — like artists found clay — I was someone who built websites. I grew up an artist, dabbling with pastels, sculpture, painting; I took lessons in all the classics. Back when I started out on the web, well, I threw my paint against the wall, watched it dry differently; tried watercolor and salt; mixed in color pencil. I created on someone else’s canvas, beholden to the whims of the Internet Explorers and Netscapes.

It wasn’t until I grew frustrated trying to create a publishing and composition tool for regular folks in CivicSpace that I realized that it wasn’t that the brushes or paint that I was using that were flawed — but that the canvas itself could be streched so much further. And so when the opportunity arose to go work on and set the direction of Flock, I jumped at the chance. The thought that I could take a number of the ideas on content creation that I’d been trying to implement in regular webpages into the browser itself was too irresistible to pass up.

And that’s how it started for me — working first on the side of web content developers — and then on the side of the actual rendering context and application. I doubt that I was qualified to work on either, but that’s besides the point, since that’s where I found myself (and artists worth their weight are hardly what I would call experts).

So now, a few months out after leaving Flock, a few heady announcements about microformats, a new Firefox Beta to toy with, a number of webkit-based apps to ponder over and an emerging identity standard coming to the fore, I’m starting to see the future materialize in front of me. From where I sit though, there is a lack of clarity as to what it’s all about, what’s really going on and what’s missing in between to glue it all together and — perhaps most importantly — a sense for what we can learn by focusing on the negative space of our current situation.

I’ve been reading about Doug Engelbart lately and the stuff he was doing in the 60s with his Augment system. He’s now collaborating with my buddy Brad Neuberg on a system he calls “Hyperscope”. I can’t help but see disjoint parallels between his ideas and what’s emerging today. Simply put, there is no grand theory or unifying concept that will bring it all together, just as there’s no single design for a tree — in fact, it takes many to make a forest, and we’re only now beginning to see the emergence of the forest in spite of the individual trees that seem oh-so-important.

And we don’t even have the benefit of LSD. Man, how are we to escape what we already know to imagine what’s possible? Oh well.

Anyway, lemme get down to brass tacks, coz I can tell you’re getting bored already. I almost am, striking out at some kind of point out of this rambling.

When I was at Web 2.0™ (I think) I mentioned to Jason Fried — as I’ve done to others since — my desire to have a webwide conversation about what the future of web browsers should look like. This was the work that I thought I’d started at Flock, but the reality is that they’re a business and not an academic institution and need to pay their employees (a harsh reality that I’m now realizing owning my own company and having a payroll). I left because of this — and maybe for other personal reasons — but primarily because my vision for the future wasn’t exactly compatible with where they needed to go in the short term. Hey, bills, remember?

Anyway, let me put it out there: I don’t get where Firefox is going. I don’t think it’s going anywhere actually. I think it’s strong, it’s stable, it’s a great platform. But it’s not innovative. It’s not Quicksilver. It was a response to IE and now IE7 will come out, co-opt everything that makes Firefox great or interesting and we’ll run through another coupla years of stagnation. Blah.

There is a solution though — you’d be surprised maybe, but you can find it in Safari and I’m dead serious about this. The number of webkit-based apps being released is growing by the week. Pyro, Gcal, Webmail, Hiker (thanks Josh!). There was talk about the future of the merged Internet-desktop as, quite clearly, this is where we’re going — but the choice of user agent is sadly coming down to facility over featureset or robustness. Why isn’t this happening with XUL Runner or Firefox (you figure it out)?

At Flock, this is where I saw things going. I didn’t see Flock as a monolithic package of integrated apps like Netscape or Office — bundled up with unmaintainable software sprawl… but with a solid underlying platform that these secondary apps could be built upon (yeah, Lucene, yeah, Microformats, yeah IM, yeah video and audio and all the rest). Speaking RSS, microformats, Atom and other syndicated content natively, you’d be able to universally star anything for later sharing… you’d be able to upload anything… be able to have any AJAX’d experience offline with a super-cache that could handle the sporadic network connectivity that most of the world puts up with (or that we put up with when we travel). And hell, with OpenID, we’ve even got a way to sync it all up together. Toss in a platform that is built on and around people people people and you’ve got something to really take us forward into the next evolution of Things As We Know Them™.

I wanted Firefox to be my Chariot, Flock to be my Sun.

Such as it is with Open Source, trying to inspire end-user interface innovation is often a losing battle.

(As an aside in parentheses, I think this is biological; I met Tara’s 2-year-old niece this weekend and she mimicked everything we did; thus it’s developmental and inherent — yet the problem remains: how do we bring the majority of user interface innovation to the open source space?)

So anyway — Safari; webkit apps… the future.

For the benefit of everyone involved, whether Mozilla, Flock, Microsoft, Opera, and so on implements any of this stuff… there needs to be some major advancements made in browser technology, both for normal humans and for web… um… painters. This stuff, seriously, is still way too opaque, and way too obscure for most humans for whom “delicious” still means “tastes good”. I want to have that web-wide conversation about the future of the web but somehow, my instincts tell me that the venue to have that conversation isn’t going to be on the web… it’s going to be in barber shops and gas stations and restaurants and the places where normal people really hang out.

If we’re ever going to bear witness to the promise of Doug Engelbart’s achievable vision, it has to be this way. And, to paraphrase walkway wisdom: nothing worth doing is easy. And so I challenge you — those who give a shit — look at what’s out there — and more importantly — what’s not out there — and begin to think seriously on what comes next… on what’s missing… on where this medium needs to be stretched in order to make the most of what’s possible.

Picoformats: microformats for mobile

Andrew Turner pinged me about a project I started up as an offshoot to my work with Mozes called Picoformats. He wrote that a picoformat is a standard-means for defining markup in small, probably mobile, devices.

That’s not exactly the original idea, but it actually makes a lot of sense and, the more that Tara and I use our Blackberries, the more we see a need for standard micro-interfaces. Sure it’s great that you can download my hcard into your address book from your regular web browser, but the same seems not to hold true on mobile devices.

Anyway, that’s an issue that needs to be addressed in mobile browsers, and Opera‘s well on their way working on such problems.

Andrew’s post did highlight both the need for me to get the word out about this project and also explain it a little more clearly since Microformats could actually address the formating of data for mobile devices (especially when we start pairing up microformatted content with relevant media-specific CSS).

The goal of the Picoformats project is to use an open process that reflects existing behavior and come up with standards for an SMS-based dialect for interacting with mobile services.

Dodgeball already has a pretty good SMS/email dialect. In fact, I use it all the time. What I want is service interoperability, so that when I send a message to (okay, I’ll reveal my bias) Mozes, I can use the same syntax to compose the command or message. For example, if I send a message formed like this: “! heading to the movies at 10pm”, it shouldn’t matter if I’m on Dodgeball, Facebook Mobile, MySpace Mobile, or FactoryCity Mobile — each service that supports Picoformats should send out the blast message to my friends, just as I’d expect it to. But already there’s divergence — with Mozes using “@” for blast messages and Dodgeball using “!”. This is the kind of thing that will make it extremely hard for people to move between services or, worse yet, use a multitude of services.

You can probably begin to see how this is similar to life before Adium or Trillian. Personally, I like not having to run 5 different instant messenger apps. I like having them all in one and being able to IM my friends regardless of the service they’re on from one interface. I’d like to be able to do the same with the mobile services I use. And that’s why this Picoformats idea is important — it’s syntactic interoperability.