Rattling cages

October 20, 2007 —

MySpace blorp

Social networks suck. I’m tempted to stop right here, but I realize that’s just a side effect of my Twittering. Since we have more than 140 characters to discuss, I’ll keep it going and try to explain what gets me down.

It isn’t the friending issue. As much as I hate re-upping each friend / colleague I have inside each new network, support groups are already being formed by geeks with more friends than me, and solutions will find the market (real people) before the market finds the issue (social network fatigue).

It’s not even redundant profiles. The idea of creating / gardening more than one is also lame, but there’s a lot going on with decentralized presence. Services like OpenID and OAuth are already batting at the cause, and it’s only a matter of time before the browsers jump in as well. (I’m downloading Flock 1.0 right now.)

Then there’s your caged activity profile (i.e., who, when, what you interact with). This also sucks, but I can live with the idea that, beyond my friend lists or profiles, most of my data activity is meaningless outside of the context in which it’s caged. Did I get bit by a zombie or a werewolf? Maybe it was a chump. Whatever. I’m only interested in keeping the connection, Facebook can have the manner.

So what else is locked down? Publishing streams, right? I can get past that too. I don’t originate anything inside a closed network that doesn’t need that context to make sense. The crap I post in MySpace should stay there. I don’t want it on my blog. The streams I deem ready for public consumption are available for re-syndication via RSS, etc. My answer to not being able to export my Facebook statuses, for instance, is to not post them there to begin with. I republish my public Twitter timeline instead.

I’m pretty much over all of that (which is to say, I can point to and even implement emerging solutions for most of these issues).

What I can’t get past is the idea that these damn things (social networks) put a log in wall between communication channels. So any point of contact I want to make (whether message, friend request or zombie bite) means the network I’m currently logged into is just going to bleep/blorp an email to my counterpart instructing them to log in if they’d like to see what just happened.

WTF is that? It’s certainly not interaction. At least not in the sense of anything that’s come since email chess, circa 1993.

*sigh*

We bang up against requests to build social networks every day at ep. Most of the projects we’re engaged in, though, are either niche enough to keep my data caging complaints at bay, or they aren’t actually social networks at all (they’re collaboration apps). But we still battle the idea of the log in wall.

Too many people think you measure community in terms of sign-ons. And the way to build sign-ons is to blorp a bunch of teasers to their users.

But what if there was a service like OpenID that actually did act as a single sign-on model? What if people were perpetually signed in to their networks? And, what if messages and alerts and notifications across all networks were delivered in decentralized form, like that of an IM window?

Crazy right? It shouldn’t be.

They’re my people, and I’m taking them with me

August 4, 2007 —

I love the picture on Oberkirch’s site of Tantek jamming on portable social networks. I can just picture the problem being cracked on all Will Hunting style – complex XOXO lists being greased up on whiteboards, chalked up on blackboards, penned out on napkins – nerds getting excited about breakthrough stuff. “We’re tearing down the walls over here! Woo! Hey Facebook, you like apples? How you like them apples?!?”

Alright, let’s slow this down. If you made it past the Good Will Hunting reference but I lost you at XOXO, that’s okay. A fraction of the online population knows what microformats are. Fewer still know what to do with them.

And those of you who did swim alongside the microformats reference are probably getting ready to hit me in the comments with “Why not just use hCard + XFN to mark up friends lists? There’s an FAQ and everything.”

I like the idea of simple fixes. hCard + XFN is one such example. For my non-microformats people, hCard is a simple format that allows you to structure contact data with machine-readable tags in standard xhtml. XFN is even simpler way to represent your relationship to each contact using the rel attribute inside anchors. Easy stuff.

Luckily, it’s only the nerds that are having the problems maintaining 30+ profiles / porting friends right now. Because the nerds know microformats, and we’re beginning to see more and more networks supporting the ideas above.

Personally, I don’t think that’s enough. I’m a huge fan of microformats, but I’m a realist. Browsers will have to fully support them before they do much good for most.

I’m also a huge fan of opml, especially if it’s of the hosted flavor. I’d love to see a similar, standard xml spec for contacts that you could host [and point to inside your OpenID account] and then allow social networks to subscribe to. But that’s still geeky.

Here’s what I see going down. My heros behind microformats are going to keep working on recommendations. The cool networks are going to pick them up and mark up friends lists. (The geeks will know what to do with that.) And just as the networks figure out how to allow you to import your contacts, Microsoft will swoop in, plug in a friends organizer inside the Internet Explorer nut, and proceed to take over the social networking world. I saw it happen in a dream – it must be true.

In the meantime, I’ll mark up friends lists [on networks we're working on] if you do.