An annotated anthology of Arun Ranganathan's Web noise.
When Vikram and I shook on building samosapedia.com after a boisterous lapse into the kind of Bangalore patois so typical of the average South Indian porki, we honestly didn’t think it would get the kind of attention it has been getting, delusions of grandeur notwithstanding. Of course, the whole team is delighted by it. CNN, the Economist blog, the Wall Street Journal blog, The Huffington Post, and The Times of India have covered it, along with a few other online and offline publications. And given that I recently wrote a small exposé about the foundational three Ms behind the idea, it’s high time Samosapedia got some airtime on my own blog.
I spend a substantial amount of time either thinking about or working on Samosapedia, which is not surprising for any co-founder. Software alone is not really what keeps me busy. The very smart Braxton, who joined us because he loves the concept, stewards the code (Ruby on Rails straddling Heroku) really well, and puts up with our proclivity to IST with humor, which cemented our bond. The big questions to me include the editorial oversight needed to build the world’s largest cultural dictionary.
Let’s first touch very briefly on the imperfection of calling it The Definitive Guide to South Asian Lingo, since in choosing to call it that, we reveal something about ourselves as editors. One of the most priceless reactions we got to the term “South Asian” was “Aren’t South Asians Filipinos?” It turns out the term “South Asian” causes a small modicum of irritation and confusion. Other observations were that we shouldn’t use the term South Asian at all, but instead say “desi” or “Indian.” On this one, we’re sticking to our guns. There are enough commonalities linguistically and culturally, and enough radical differences, for us to be geographically inclusive on the site. The term “South Asia” may come from a taxonomy generated outside South Asia itself, but we can’t find a better, more inclusive term that matches our aspiration for a giant cultural dictionary. We’re ceasing to worry about labels. The existing one has been well received so far — thanks to our users, we have over 6000 entries now, and we’re going to keep on growing.
What becomes interesting is that sometimes, definitions aren’t merely objective. We don’t really want them to be objective, which is why we allow for multiple entries for a given term. Take for example entries like the one for the Jan Lokpal Bill, which as of this writing, still features prominently in popular press in India. One user’s idealism may test another user’s opinion on the whole approach taken by the bill, with the result being controversy. We welcome it — the lingo we’re collectively cataloging is multifarious, and controversy is the by product of engaged users. By that same token, one user’s humor may offend another. Here, we’ll traipse as lightly as possible, because we want to allow maximum self-expression, liberating language and encouraging our users to be creative and playful. Soon enough, we’ll also want to have users help with moderating words. It’s not just a dictionary we’re building here, but a community, responsible for its own editorial oversight, without the founders being gatekeepers.
Samosapedia has rapidly become a small anthology of South Asian writing, and makes people laugh, bringing delight and nostalgia (nostalgindia?). I am really excited about it, and about all the things we’re going to do with it in the future.
Let us say you move to New York after the bold liquidation of some chutzpah, and that your friends back in west coast cities want to know what you’re up to. They want to know how you like NYC and what you’re doing on a daily basis ever since you moved there. Naturally, others are curious about who you’re seeing romantically, if anyone at all. What’s up, they ask (inquiring minds, etc.).
Sometimes a potent mix of wanderlust and the allure of an unanswered “what if” question causes change to happen. I recently moved from San Francisco to New York, and I recently transitioned from my full-time role at Mozilla to a part-time consulting role.
Of course, soon after I left, the Giants are making a World Series run, making me long to be near Willie Mays plaza. I love San Francisco, with its micro-climates, improbable topography, and draconian parking inspectors. I spent one third of my adult life here. I worked with inspiring people to advance the reach and capability of a massively hyper-connected world; I played enthusiastically (if not adeptly) in the magnificent outdoors; I got up to all the usual urban shenanigans in my twenties, even getting my heart broken and wizened; and — at the great risk of courting the obvious metaphor — I emerged from the fog of a prolonged adolescence into what I hope will pass for maturity. I’ll miss the City by the Bay. There’s no place like it in all the world.
Within reason, I relish change, and seek it out whenever I feel I’m getting lulled into complacency. I’ve wanted to explore non-technical projects for a long time now, and the best way to do that was to leave the epicenter of technology for a while. My childhood brought with it much travel; I was raised in India, Hong Kong, Ethiopia, Russia, China, and France, with some time in Canada. I often dodge direct questions about where I grew up, preferring the quick version of the story, but I am sticking to the facts when I tell people that San Francisco is the longest I’ve ever lived in any one place. So why, then, New York?
I’ll spare you my romantic observations about cities. E.B. White (of Strunk and White and Charlotte’s Web fame) said it much better than I ever can back in 1948 (but you should read him in 2010, since his words have aged so well). A small snippet:
“There are roughly three New Yorks. There is, first, the New York of the man or woman who was born here, who takes the city for granted and accepts its size, and its turbulence as natural and inevitable. Second, there is the New York of the commuter — the city that is devoured by locusts each day and spat out each night. Third, there is the New York of the person who was born somewhere else and came to New York in quest of something. Of these three trembling cities the greatest is the last — the city of final destination, the city that is a goal. It is this third city that accounts for New York’s high-strung disposition, its poetical deportment, its dedication to the arts, and its incomparable achievements. Commuters give the city its tidal restlessness; natives give it solidity and continuity; but the settlers give it passion.”
For the next conceivable while, then, I’ll be a settler. I’ll bring to New York my “what if” questions, and see what happens when I pursue the answers with passion.
The transition does mean I’ll miss the people I worked with over the years, particularly at Mozilla, a project I grew up with almost right out of college. Few things compare to the thrill of contributing to something that you really believe in. Mozilla paved the way for what is now the triumph of open-source on the web over a closed-source monopoly. Not working on it full-time means that I’ll no longer be associated with some things, like being the Chair of the WebGL WG or being front and center for developer relations. But it also means I can take on some manageable tasks and make sure they get chaperoned through to completion.
I’m in what seems to be a a bigger pond now — a chaotic, crowded one with four seasons and a subway and even more draconian parking inspectors. The Fall is lovely here, and I am optimistic.
This year, I’m not moderating the Browser Wars Panel at SxSW. I did it for three years in a row, and maybe three time’s a charm. It got written up by PC Magazine each time, and that felt great. The truth is, I can no longer be unbiased (I work for Mozilla on Firefox now). What’s even more true is that I’m so occupied with standards-body issues that I’m concerned I no longer have my ear right on the pulse of what web developers want. Last year, Jeremy provoked a riot when he “threw some shit at the fan” (his words) about font formats. Me, I largely kept the peace, but couldn’t resist a little school-boyish bullying of Chris Wilson (then still the IE guy) about a few things, and I also got accused of going easy on Darin, the Google guy.
What makes a compelling story for me is the browser peace, though. The web as a platform (“The Web Platform”) wins through consensus about standardization. I blogged recently about standards in the device era. What I didn’t touch on is whether patents will thwart the attempt to build out the promise of a seamlessly interoperable web. I’m not moderating a discussion dubbed “Browser Wars” this year, but I’ll leave last year’s attendees (as proxies for their browser companies) some fly-by notes:
Suketu Mehta says Mumbai is a vada-pav eater’s city. Within a city of riotous diversity, vada-pav, typically a street food, may be an obvious unifying factor.
It’s also being cleverly co-opted as a symbol for MozCampMumbai, another amazing Mozilla community event, taking place on Sunday July 19 in Mumbai.
Speaking at MozCampDelhi was one of the highlights at the start of this year, and I’m sorry I can’t be at MozCampMumbai in person. Asa, Mary and I recorded a video for the occasion, which I suspect we’ll post on Air Mozilla before long. I spoke about font-face, HTML5 Video, and a few other things that I think are particularly relevant to folks attending MozCampMumbai. If you’re attending MozCampMumbai and reading this after you’ve watched me prattle on in the video, happy MozHunt 
Enjoy some vada-pav, hackery and conversations about the Web.