So, once I got done talking (very very quietly) about how Raindrop sounds awesome, but also kind Chandler-ishly vague, I saw this Twitter from Sonny, “Raindrop is the innovative idea that Google Wave was hoping to be.”

Which got me all kinds of excited again. And also musing on the failures of Wave. Really hoping that Raindrop can be useful to me, whether or not you’re also using it, Google is qualified to build boil the sea solutions, but they lack elegances.

Just the name Raindrop sort of sounds to me like something that could build slowly to a crescendo, a “delicious play”: a tool useful long before its adoption curve cross the plane where its latent social dimension is revealed. (my imaginary friend is old school, he pointed out that IM tools successfully required people to opt-in to build value and they’ve done fairly well, to which I can only say times were simpler when ICQ was launched and we were all more desperate for better tools, and AOL already had a meaningful desktop internet install base they could upgrade largely in place)

And then Raindrop has all this buzz about personal/people centricity, but I’m worried not to see much acknowledgement on the failure of RSS readers. Its easy to get confused by the real time web buzz and think people actually want real time, comprehensive information. Fuck that. I want a tool that delivers meaningful, timely information, everything else is just anxiety producing.

Blaine has done a lot of good thinking, and talking, and not nearly enough good writing on the game changing, sea change that is the switch from pull-to-push, that perhaps the white-list vs black-list is the most important kladistic trait, and I’m wondering if papering over those divides in a single client misses the point. (Blaine useful refers to this as, “the total fucking brokenness which is email” or words to that effect) It’s something I’ve been meditating on a late into the night recently having just opened a new push communication channel on Flickr.

“Raindrop uses a mini web server” is also old school. Wow. There was a really wild and wooly bunch of apps being evolved at the end of the 20th century that largely died out, interesting to see that design idea still kicking out interesting creatures. (this is what Aaron calls the I-hate-to-admit-it-but-Dave-Winer-was-right principle)

And while I love to see Flickr get love, “flickr arrives, your messaging client should be able to show the video or photos near or as part of the message”, it really raises the question in a system of social object sharing, what is the object? Just the photo? Something else? (and smacks a bit of the one-system-to-rule them all, which is cool, but again, see Chandler, and Dreaming in Code)

What can I say, that’s the sort of thing my imaginary friend and I talk about. Now I guess I should go finish reading those docs.

… I mean Flickr/Upcoming/Delicious. In particular, I mean that brief moment of optimism in the Spring of ‘06, on the roof of the Iron Cactus, at the Spread the FUD party, when it looked like Yahoo! had a wedge and the will to solve the social search problem, and magically, I might even get to be a part of that. I said in my cover letter (in silly flowery, cover letter speak)

“The next round of innovation will be about building connections. The explosion of voices, information and ideas is currently outpacing our techniques for coping with them. We need to be helping people and communities find new ways to connect, interact, and work together to make sense of this accelerating decentralization. Innovation has been blossoming at the edges of the Net since the beginning, but innovation is also moving back to the connecting nodes, like Yahoo.”

Which is much on my mind when I hear about Marissa demo’ing social search yesterday.

And I’m deeply puzzled (and not a little disappointed) that anyone would care if Bing or Google can search the public status timelines, if it doesn’t come with social context.

Now the question is can Goog shake their historied failure at all things social.

Photo from Jan Brašna

Walking into work this morning, thinking about the vibrancy of the Twitter API developer ecosystem. Twitter has embraced (not necessarily intentionally) what I see to be open source’s two key aphorisms on successful community engagement (lightly paraphrased)

“Get people laid” – JWZ

“Leave lots of low hanging fruit” – Karl Fogel

People don’t go back often enough to the well of hard fought wisdom on community and online collaboration which the open source community developer. Believe me you do not want to spend the blood, sweat and tears to re-learn those lesson the hard way, they were fighting for a noble cause they believed in and it still sucked. Your micro-poking app ain’t all that.

Photo by curlyjazz

A griot (pronounced /g?i.??/ in English or [??i.o] in French, with a silent t) or jeli (djeli or djéli in French spelling) is a West African poet, praise singer, and wandering musician, considered a repository of oral tradition. – Wikipedia

Also an emerging tag for describing the ongoing protest in Athens over a 16 year old being shot to death at point blank range by Athens policemen.

Being used on Flickr, blogs, and Twitter and the meta del.icio.us. Not being used by the corporate media (aside: the trailing ’s’ is lexically significant, classic stemming does not work on tags)

Does anyone know how and where this tag emerged?

Clearly the next evolution in participatory media (and the only type with a future) is figuring out what the tools to discover, distribute and broadcast these meta-media collaborative objects. Who is thinking and writing about this?

Photo by murplejane

One of the key topics (I think) in my Casual Privacy talk last week was the importance of “context” in privacy and sharing. That some people have trouble understanding how fundamental context is to all social interactions was my primary take away from SG Foo, and I’ve been preaching it quietly where I can.

All by way of saying, I made one of my rare visits to FriendFeed this evening, and I was reminded that I consistently regret it. Breaking down those contextual walls means I consistently like the people I find there less then I did when I was able to interact with them in isolated manners; fire walling the aesthetic from the technical from the political from the personal.

We need routing not aggregation.

A hashbot is a robot that hangs out on an IRC channel (hence the #) and provides a conversational interface to a resource.

hashbots are the ancestors of Social Software for Robots, and the idea of Twitter/YubNub as Web CLI.

Places is a new Flickr feature that mines our corpus of geotagged photos, identifies characteristic features on a per location basis, and then goes back into the data looking for “iconic” beautiful photos. (btw try reloading that /places page, the feature places are random. As to a certain degree are the photos on the individual Places pages themselves)

It also is where a good chunk of my creative energy went for the last few months which is why the blog has been so quiet. And its a hell of a lot of fun, not to mention a privilege and pleasure to deep dive into our database and be reminded just how much fabulous photography there is on Flickr, and maybe just barely fumble around the edges of surfacing the diverse communities shared vision. Eyes of the world indeed.

A Place for GeoRSS feeds

Dan roped me in on Places months ago. We had geoFeeds working for semi-arbitrary places, and we needed a page to hang them off of. That page looked a lot like search result. You never saw it because the Flickr project management process (a blog post of its own) left that particular prototype a bloody, heaving wreck. Don’t worry, the current version is much much much better. (of course you also never saw Dan’s brilliant prototype of the current version, which was too cool to release on an unsuspecting public) And voila, many months later, the feeds are there. (though I’d still like to bring back that SRP view to allow rich searching within a location)

Increased Surface Area

We brought a bunch of different design goals to Places, but one of my obsessions that I think we nailed was the idea of “increasing the surface area” of Flickr. (also known as providing new ways to level up in the Game of Flickr[tm]). Only a few people, and a limited range of styles will ever be featured on the Flickr Explore pages. Which is fine, most people don’t care. But Places provides another way to recognize the contributions of Flickr members, by hilighting their geotagging and their photography skills. I’m looking forward to adding a couple more similar features to Places, recognizing other Flickr Games one can level up in, and other contributions back to the commons you can make.

Mo’ Betta

A bunch of stuff didn’t make our initial launch. Some of that has come in since then. More will be coming. I’m particularly excited about using adding some new data sources to improve the page. (e.g. the Groups right now a bit weak, and we don’t have reliable neighborhoods in cities, both of which are in process of being fixed)

Thats kH8dLOubBZRvX_YZ to You

Turns out there are a lot of San Franciscos in the world, and we personally struggle to keep track of which one is which. So we’ve been experimenting with giving them unique place_ids. If you look really close you’ll start to see these popping up around flickr, in photos.getInfo, photos.search, and as microformats on the Places pages. Its all very experimental, this unique identifiers thing, but we think it might work.

Arm Chair Travel

And because I love you, I’m going to let you in a on a secret. Have a great trip.

Taking a break from all the collaborating, originally uploaded by George.

We slaved iCalico to Crowdvine to add a social networking layer, a network that was walked, mapped, and color coded by the Pathable folks.

Tony has a nice report back on it, as does Shelly from Pathable (6 weeks aka a couple of late nights). And Scott Berkun (who owes me a copy of “Art of Project Management”!) said super nice things.

Collusion Patterns

So how do you do that — stitch together 3 different sites to provide a unified experience? Visions of APIs, Internet scale SSO, and messaging layers spring to mind. Or more likely hash and slash patches, jury rigged shunts, juggled install directories.

We did the dumb easy thing, and I’m surprised more people don’t do it.

1. Crowdvine.com sets a cookie collusion. This cookie contains the data we needed to display the logged in view of iCalico. (you’re nickname and optional your URL). In addition it contained a md5 hash of the concatted data, plus sekret known only to Tony and myself.

2. If we find the cookie collusion, we load the described user from the database, or create it on the fly behind the scenes.

3. There is no step 3.

Amazingly useful, trivially simple, ultimately flexible. Niche sites are great, but you need techniques for stitching them together before they can realize their potential as pieces of an ecosystem. I don’t necessarily expect to see this kind of integration become more common, but I think it would be great if it did. (and in the name of transparency disposable apps are huge enablers, disposable sites/apps is another pattern I’m puzzled we don’t see more of — its as if we more inclined to converse bits then landfill)

update: Whoops, it was pointed out there was a step 3, or rather a step 1.5: use CNAMEs to point to individual components on sub-domains.

NYTimes has an article on the ongoing Netflix recommendation open challenge thing. ($1mil to a team that can produce the best collaborative filtering mouse trap)

Unfortunately the project is flawed, because the basic question is flawed, fundamentally and in a very simple way. We have moods, we have shifting interests, and trying to compile all those multi-variates into a single vector of interest is impossible.

Rather then making the computers super smart, I’d rather see an interface like the Pandora channel creation where you choose 2-4 songs that suit your mood and the system finds the common elements.

Tonight at the video store I wanted something that was smart and fast enough to be engaging, without being so smart that it took work to follow. Maybe a political thriller? If I could have mixed a recommendation queue out of 3 Days of the Condor meets Wag the Dog meets something like Enemy of the State to find something in that vein that would have been better then all the weighted neural nets.

And I’ll wave the million dollars if they just build it already.

Not sure where this systemic biasis for computer as deep thinker comes from, probably dates all the way back to the Ultra project and other primordial computer science legends. But its the wrong metaphor here and now, smarter, smaller tools to extend the human reach, not replace humans.

(can you tell I didn’t find my movie?)

Photo by wili

Stone Cottage pointed to a great post by Rick Skrenta, CEO of Topix (and mad mind behind NewHoo/DMOZ for those who can remember back that far) on the Topix re-launch.

Lot of really interesting stuff about identifying a brand’s core value and putting it into practice. But also a phenomenal laundry for a problem that has stumped a lot of us, how to make a local news site succeed. Including:

• Anthropomorphize our existing technology into the roboblogger. This was a brilliant idea from one of our lead engineers. It simultaneously solves three problems:

  1. Booting up a new city — you need posting activity to draw the first editors. The roboblogger would give us that. But he is shy and gets out of the way if humans show up and take over a page.
  2. If the community editors go on vacation, the roboblogger can step back in and take over while they’re gone.
  3. People know when a robot is editing the page vs. a human. His profile icon is a picture of a little tin-can robot. His handle is ‘roboblogger’.
  No more confusion.

A project has to already have value to draw a valuable volunteer base, this is the classic and yet fundamentally hard problem with boot strapping all local sites. But as soon as you have volunteers your contract with them is to rain attention and love down upon their contributions. roboblogger is a really neat hack to handle the delicate balance of a site’s lifecycle and mix community and data mining techniques in social software. Looking forward to watching it play out.

Everyone say ‘I’m in’ to get onto a list of N people participating. Then write down N numbers, positive or negative, that add up to your salary and send 1 of them to everyone else on the list. Add the N-1 numbers you receive to the number you didn’t pass out, and announce that to the list. The sum of those numbers is the total salary. If N-2 people gang up on you they can’t guess yours. As a bonus, you can always back out at the last minute before divulging your own sum without having given anything away.

Which you got to admit is a beautifully simple, and elegant solution to the problem of sharing sensitive information in a low trust environment.

The solution? A 7 line Perl CGI to just write salaries to a log, and a good faith promise not to track IP addresses.