Irina (from the hottest vlog of the Bubble 2.0) cornered me at SHDH 0x06 for an interview.
I have no idea what I was talking about, but mmm!, that wine looks tasty!
Irina (from the hottest vlog of the Bubble 2.0) cornered me at SHDH 0x06 for an interview.
I have no idea what I was talking about, but mmm!, that wine looks tasty!
David Parmet offers excellent advice for folks looking to do the public releas early and often thing (yeah, like we did):
The whole release early, release often mentality is good in theory. When practiced against an impatient audience, it can quickly squash whatever goodwill and coolness factor a start-up can generate. And the process will only feed itself as more start-ups do alpha releases (if alpha is the new beta, what’s the new alpha) and invite-onlyl pre-alpha pre-releases in response to a blogosphere hungry for the Next Cool Thing(tm).
So what’s the solution? Managing expectations can only take you so far. So release early and put on your flack jacket.
Don’t believe the hype at Marketing Begins At Home
technorati tags: opensource, flock, release early
So there’s been some more talk lately about Flock and extensions and relevancy and Performancing’s new blogging tool for Firefox. I’m all for it. The more we talk about open source, about Firefox, about Flock, about coming up with better, cooler, faster and more usable technology, the more we’re inclined to just go build it. And in doing so, make sure that it’s relevant and actually meets the needs of real people.
I have to admit though, the potshots at Flock are becoming a little … tiresome.
So ok, I’m all about being skeptical. I’m all about looking a gift horse in the mouth, in its eyes, and … elsewhere… yah. (Y’know, you gotta make sure there’s no sneaky Greeks lurking about or whatever.)
And this post was going to about that old information autobahn thing and how there’s plenty of room for one more automobile manufacturer. And that was going to be my analogy for why Flock is a good thing for drivers, etc, etc. But I decided that’s a dumb idea. And boring to write. So let me get right down to it.
Here’s the thing. We’ve actually been pretty certain for some time that most of the features that we build into Flock will be eventually be ported back over to Firefox as extensions. Or become commodity features in other browsers. That’s the way open source should work — and the way software development plays off itself — and we’re totally in support of that! The point is not to make a bunch of proprietary tools that only work in Flock. That would be rediculous and counterproductive. I mean, our goal is to make using all the great tools now available on the web easier to use by building a more consistent user experience. Yeah, that’s our big top secret plan.
So why build our own browser if we’re in support of this whole extension model anyway? Well, let me paint a picture of my vision for Flock and why it at all makes sense that we continue doing what we’re doing, no matter how many extensions come out and attempt to mirror our featureset.
Cue lights … cameras rolling… pull curtains … 5, 4, 3…
So in the olden days, there was a web of interconnected computers and file servers and yada yada that were conceived of as a massive network of libraries containing all kinds of hyperlinked data and information. Now, pieces of that data had individual addresses, just like books in libraries had unique identifiers called Dewey decimal numbers. Thus pieces had a static position in the system and you used a web browser to pull up those pieces of data. So when someone added a piece of information to the network, say an online shrine about their cat, it got its own address, acronymically known as a URL.
So so so, jump forward in time a bit. Welcome to today, a time of spheres… blaw-go…spheres… where currency is measured by one’s attention-magnetism and linkification, where if you don’t have a blog, you don’t have a pulse and you’re dead, kaput, worse than history, see ya later, sayonara, did you even exist in the first place? Oh yeah and what’s your feed again?
Hmm. So let’s slow it down a second here. Get this, here it comes, I’ve got a visual metaphor to sink yourself into: so say you’re walking down the street, a crowded street. Let’s put you in Manhattan, or Boston, DC, Copenhagen, Tokyo wherever. Look, it’s busy. 10,000 people trampling the sidewalk concrete and they’re all in chaos, no no, wait, calm, but y’know, this is chaos theory in motion.
This is 100,000 people walking down the concrete towards you, you, you’re walking the other way — who knows why? you just are — and there are these crescendoing voices around you, swirling, smashing conversations. You’re grasping at words, sounds; the ring of cell phones, change being dropped between high heels and rubber soles. A cacophonic masterpiece of human communication.
So listen, you hear something, it piques your interest, you think to yourself, “Aha.”
Moving towards it, crowd parting in front of you, shoulders meeting; you sideways, all arms and elbows, towards the sound. One motion, you blur, find the source. Listen, speak, are heard, enlightenment and voice. This is conversation. This is fleeting. This is connection and this is what sustains you.
Now there are ten of you. Ten. Or maybe ten hundred. And each one of you is having this experience. As you weave your way in and out of the throng, you’re merging and joining ongoing; nascent; 1,000-year-old conversations. Say your piece, move on. Don’t stay too long, surely something else as interesting is being said … just around the corner.
Ok.
Stop.
Curtain down, lights go on; watch your eyes, it’s bright.
Now that, that picture, that experience, that’s the web. Yeh, that’s the web today except imagine it with your eyes closed, with blinders on, with the sound fuzzed out and staticy, with orange icons all over the friggin’ place. And yes, every now and then some jack-in-the-box assclown pops up trying to sell you V_1agra.
It almosts make me want to go back to the old library model.
But no, see, that’s where Flock comes in. Or I don’t care, don’t call it Flock. Whatever you want, but that’s where the thing we’re building comes in. That’s why we exist, that’s why we matter, that’s what the point is.
Yeah, Firefox and Duct tape, it’ll help. Sure sure. It’ll get you some of the way there. But hell, when I’m talking to someone, engaged in a conversation that threatens my very existence, or that threatens to change the way I flip my omelettes, man, I do not want my mouth to fall off at the jaw because it wasn’t tested, wasn’t built right, didn’t have a million beady eyes boring down on it while it was being fastened to my head, making sure the stupid thing would function in the real world without needing pliers or a tire-iron to get it to work right. No, I do not want my memory to hiccup, to recede, for me to lose my place in line, to have my line of thinking severed when I’m talking to someone else. I need to be there, fully, to be there in the conversation, as a whole, as one integrated thing, yes yes, a fully functioning machine. No, I don’t want to be some bootstrapped, schizophrenic, unintuitive, semi-confused and incomplete afterthought kludged together and mistaken for a vision of the real thing. No, I want more than that, I want to be as in the conversations that I have online as the ones I have offline — I want to get to the point where there is no difference, that a conversation is a conversation is a conversation. It’s sharing understanding and it’s sharing confusion. I need a tool that helps me achieve that. It needs to understand things the way I understand them; it needs to reflect the reality of what’s going on online today.
When was the last time you thought twice about the fact that you’re talking to a digital signal every time you use your cell phone?
Or how about the fact that your instant messages (which indeed seem so instant) actually travel over thousands of other people’s computers and servers before they reach you?
And your email? Even worse. If you think herding cows is messy, you should see the way email is schlopped all over the place.
The point is this. These technologies have become second nature vehicles for communication and expression. And blogging, podcasting, vlogging and the whole lot of recent “mecasting” technologies aren’t as integrated, aren’t as easy, aren’t as accessible as they need to be for them to be picked up and made as commonplace as the telephone (or cellphone, if you prefer). Point Four Percent of the population is nothing (that’s 23.6 million blogs as a percentage of the world population by the way). And yet another extension is not the answer. I don’t even know if another browser is. But we need something that works to solve this problem… or at least to make it better.
Yep, we’ve got a vision for how a browser with a different understanding of the web can help. We wouldn’t be building it otherwise. This is what drives us to make Flock the best possible, most easy-to-use and most useful tool it can be, because we’re experiencing all the same problems that everyone else is. Just coz us at Flock’re a tech savvy bunch doesn’t mean this stuff comes easy for us either. And for chrissake, it’s got to get easier, so much easier, if these conversations are going to include and be accessible to those who most need a voice.
Ryan King pointed me to a post by Tim Bray about how unintuitive feed consumption is in browsers today.
I couldn’t agree more. Indeed, RSS and general feed consumption in browsers have been tacked on, hacked in, and bludgeoned into the UI in inconsistent and narrow ways. Safari‘s got its poorly-named RSS view. Firefox (for now) has its simple toolbar and livemark feature as well as countless third-party add-ons.
We’ve also got some great web-based and desktop tools whose tasks are to deal only with feed content.
But all those are simply not sufficient nor reflect how fundamentally syndicated content is changing the way people interact, publish and share on the web.
To date, we’ve taken mere baby steps towards a truly syndicated web. We’ve tended to stay close to our concrete, static websites because of the familiarity and stability they offer us. We’re used to things existing in one place at a time in real life; on the web, general expectations have stuck to this powerful paradigm (look, I had a talk with my mum about this stuff so I know it’s true! If you already get RSS, you’re excluded from this generalization (notice my use of the word “general“?).
What is becoming increasingly clear, however, is that the old ways of thinking about content and where it should exist (or indeed where it actually does exist) no longer need apply. Consider podcasts, the perfect example of empheral media. You can’t search for podcasts directly; no, instead you have search for text about the podcast unless you go to some visual directory, which still relies on word and image (still not aural search technologies — we need the Riya of podcasting!). On top of that, you typically have to download the “physical” file and play it locally or on your pacemaker, severing the link back to the original source which may be updated or changed later.
The point is this: Tim Bray is not only right but the problem he describes goes deeper than just poor feed integration and workflows in existing browsers. It’s that browsers aren’t moving fast enough to embrace the potential that syndicated content has for radically improving the efficiency, responsiveness and collaborative nature of the web. Think about all the information you consume with feeds already — it’s only going to get worse until browsers fundamentally look at the web as an event stream and less as a library of independent books and pages.
Browsers in particular need to change to address this emerging opportunity and make it both easy and seamless to leverage the benefits of syndicated content. Flock is obviously taking a stab at it, both in the browser and in how we’re architecting our web real estate (or should I say faux estate?). In my view, Flock is an API aggregator that lives and breathes syndicated content. Yeah sure, it’ll load up webpages like any other browser, but it’s how we expose web services and feed content that’s really exciting and new.
So now I’m curious. As hourly Flock builds aren’t terribly stable, I’ve been without an aggregator for some time and so I’ve probably gotten behind in personal aggregation trends. How have you guys been managing your feeds? I notice that I get a lot of traffic from Bloglines and Rojo, so what are the key features you’re dying for in a syndicated content app?
Open Source World Domination
Originally uploaded by net2photos in I Want Change.
It’s good to dream, isn’t it?
I had a meeting with Daryl, Vera and a sleepy Lloyd the other day to figure out how to bring the Flock.com website properties forward, in terms of both design and utility as well as towards an architecture for participation (thanks Tim!).
So what’s gong to happen to *.flock.com? Simple: massive syndication, resyndication and the collapse of web development as we know it.
Using Drupal as our core platform enables us to move content back and forth between all the different platforms that we use (and trust me, there’s quite a few (password: flock). It also means that the content building blocks that we’re using to build our site will be available to our community to mashup pretty much however it wants (sticking within some liberal licensing scheme, of course (thanks Larry et al!)).
The implications of moving to such an architecture are significant.
To begin with, it means that besides producing content ourselves, we’ll be able to consume feeds seamlessly that our community produces. Yeah, so we can pull in other people’s blog feeds, Flickr feeds, forum feeds and on and on (thanks for adding RSS to Basecamp, Jason!). If it’s got an API or feed output (password: flock) (or is marked up with microformats) figure that at some point we could use it somewhere on our site. It’s like one big disgusting paste-board exercise. Glorious, glorious!
So get this: this is where web development is going; this is also where Flock is going. Static websites are a relic of a foregone era. It’s no surprise that when you come upon a prone animal on the side of the road, it’s a good bet that it’s dead. Roadkill or natural causes or radiation sickness. Same thing is true on the web.
Yeah, if this direction sounds like chaos, it’s not. It’s ordered madness, which, you’ll note, has massive amounts of potential energy in its structure. Go ask a physicist what that means coz I have no idea. Fortunately, we’ve got some tricks up our sleeves to tame this beast. Check it out.
One thing that’s important here is being able to 1) navigate your way around the site and 2) get back to where you were many days or weeks ago (in an event stream, how do you hit pause?). Well, for one, tagging. Duh. And rich, full-text search (thanks Google!). And a social network thingamabobber. And favorites. And outgoing feeds. With permalinks.
Gee, a website that mirrors Flock’s featureset? Eeeenteresting.
No but seriously, back in the days of Round Two we were building both a browser and a web service. Why? Well, it’s actually pretty interesting when you’re designing both the content source and the user agent. It’s like choosing both the bread and the cheese for your fondue. Or chocolate and fruits. Um yeah ok, but why? Because intimate knowledge of both sides of the equation helps you fill in other variables that much faster!
Consider: 1 + x = 3.
Easy right?
So try this one on: APIs + Feeds + Drupal + Microformats + Flock + mojo, baby = you figure it out.
But I’ll tell you one thing, it’s going to kick ass.
Flock’s crossed the Pacific and is landing in China, the land of free speech and civil liberties!
No but seriously, the sun doesn’t set where Flock is going, so China had better get ready. Bloggers know no boundaries and sure as hell aren’t polite. When the Bokee edition of Flock comes out, proponents of democracy can breathe a sigh of satisfaction; we are taking back the web and talking about it every step of the way. And you can’t stop us. You won’t stop us.
So in my other life as a fake celebrity, I get interviewed a lot or end up in OPML (other people’s media and links).
I thought I’d post a bunch a these for reference, more to promote the enterprising work of these kindred spirits than for any self-gratifying purposes (yeah right). But no, seriously, I’m totally honored that any of these amazing folks would take the time to chat with me and have me ramble on and on about changing the world and such nonsense. I don’t know why you’d listen necessarily either, but if you’re into sadomasochism, here’s hours of pleasure for ya:
And I might be appearing on Irina and Eddie’s fabulous Geek Entertainment TV soon… And then, well, there’s the incredibly embarrassing drunken stuck-in-an-elevator-in-Paris vidcast that I really shouldn’t be linking to. Eh, c’est la vie.
I had an interesting discussion with Freeman Murray at SHDH last night about offline apps for use in remote areas where network latency can sometimes stretch from days into weeks for access to a “network”.
In such circumstances, you’ll have folks driving around on mopeds or busses with wifi antennae, USB drives or CD-ROMs delivering email and providing a means to getting “online”, admittedly asynchronously. Thought 28.8 was slow? Try email by bike messenger. It’s only one step above message delivery a la Paul Revere.
But in some cases, this is the best they’ve got and you can’t expect Google to trot around the world setting up mesh wifi networks for these folks (not in the near future anyway). And while some folks are working on this project and it is getting better, nevertheless, we must constantly be aware of and design for a rich offline experience.
This is especially close to me, considering I’m writing this on BART without connectivity as I head to the airport. Yes, even in industrialized areas connectivity is still not guaranteed (let alone free).
So an idea I’ve been playing with for some time is how Flock can support offline browsing and interaction, beyond pulling simple content from your cache or downloaded feeds. In the old model of the static web, the permalink model made sense and was perfectly useful — indeed, it’s still nice to be able to pull up that bar’s website when you’re wandering around Paris at 9pm, an hour late for the meetup that you helped coordinate and you’ve got no idea where it is except for the micromap saved in your browser’s cache.
But the problem is that we’ve divorced the data from the interaction layer. It’s like having your Halo saved games without having the game engine to play them. Boy, that’s a whole truckload of fun.
So anyway, Freeman and I were discussing how Flock could help with this problem. One idea that has some legs, I think, combines data delivery in microformatted XHTML pages (you’re caching it already, might as well make the data semantic and thus useful) and then allow basic interactivity with that data through extensions that are designed for both online and offline use. Thus, in the event that you’re offline, well, instead of pulling unsuccessfully from the server, it would pull from your local cache and allow you to do certain basic things, queueing your actions to be performed when you have connectivity again.
Indeed you could even use a P2P architecture for this, sharing encrypted offline action-scripts across a mesh network. When any one of those nodes reconnects, it could upload those instructions to the final destination where they’d be executed in batch. This would have the added benefit of spreading the need for connectivity across many nodes, instead of just one (like a USB drive which could get lost, stolen, confiscated or otherwise compromised). Should the actions have already been performed when the “message in a bottle” arrives, the commands would be simply ignored. There are technical details in here that are beyond my comprehension, but be that as it may, the idea is promising.
So back to offline extensions development… Freeman proposed an architecture in which Flock would ask the web app for a locally-run “servlet” that would provide similar offline interactivity when not connected. Autodiscovery would happen in the way that sites provide favicons or perhaps through a rel=”offline” link. The question though, is whether the user would need to take explicit action to install the servlet extension outright, or if, by visiting a web app (like Gmail or Basecamp), you’re implicitly expressing your interest in using the functionality of the app, whether on or offline.
I think the latter reflects a reality that I want. Installing apps on the desktop doesn’t make sense anymore, what with all my data being hosted in the cloud. So being to access and manipulate my data when I’m offline is going to become a requirement that the browser can tackle. I mean, this is the problem with solar power. You need to use your car whether it’s sunny or not, and so we’ve got rechargeable batteries, right?
Well, I think you get the point. Here’s the high-level description of the proposed solution (which I may or may not have communicated effectively):
I probably got a bunch of the technical details wrong, but whaddya think of the general concept? Does this already exist in some other form somewhere?
I met up with Jesse Andrews (of BookBurro and Userscripts fame) and Kragen Sitaker last night and they suggested that we have a bit of a XUL show-and-tell-hackathon at SuperHappyDevHouse. I’m wickedly stoked.
And just maybe I’ll get a chance to whip Rhyzomatic into functional form. Finally!