Results tagged “facebook”

Zuckerberg's FWD: Making Sure They Get It Right

May 2, 2013

Mark Zuckerberg built himself a political action committee called, and they're diving headfirst into trying to change immigration policy as their first priority. They seem to have good goals, and they've already adopted some extremely polarizing tactics, so I've tried to collect my thoughts here, as informed by a roundtable conversation yesterday which included President and co-founder Joe Green. Spoilers: I don't have a simple, easy "It sucks!" or "It's great!" conclusion about, but hopefully I've put together enough perspective here to help inform the discussion, provide some specific areas of improvement for the PAC, and offer a useful starting point for the discussion within the tech community of how we'd like to be effective in driving policy, whether specifically about immigration or on any broader issue.

It's already clear that with, the tech industry is going to have to reckon with exactly how real the realpolitik is going to get. If we're finally moving past our innocent, naive and idealistic lack of engagement with the actual dirty dealings of legislation, then let's try to figure out how to do it without losing our souls.

The Fundamentals

Mark Zuckerberg wrote an editorial in the Washington Post a few weeks ago announcing the launch of, in concert with a list of prominent Silicon Valley supporters. (Post CEO/Chairman Donald Graham is on Facebook's board, hence the choice of platform.) Zuck started by listing top-tier tech execs like Reid Hoffman, Eric Schmidt and Marissa Mayer, went through listing VCs and investors who are well known within the industry, and concludes with former Facebookers Aditya Agarwal and Ruchi Sanghvi, who aren't big names in the industry but are actual immigrants, in contrast to most of the other backers. Shortly after launch, names like Bill Gates, Reed Hastings and Fred Wilson were added as they apparently became financial backers as well.

All those dollars are being spent to support an organization that's pretty small — half a dozen people in Silicon Valley and four people on the ground in DC. ADrian Chen's excellent look at offers lots of good perspective on the functioning and funding of, but this is an organization that seems to be built with a long-term mission in mind.

I've long wanted the tech industry to engage in a serious and effective way with the policy world. At the peak of the protests against SOPA and PIPA, my dream was that we might black out our sites in protest of torture as state policy rather than simply focusing on self-serving goals. And while we've thus far had limited avenues for participation such as the White House's innovative petition platform, we obviously haven't played in the serious realm of policy before, either with our attention and interest or with the greasing of palms that actually makes legislation happen in DC.

So if we've got a practical organization working on meaningful problems and that's what I've wanted the tech industry to do, why am I so concerned? Let's take a look.

This is Zuckerberg's Game

Move Fast and Break Things

I come by my skepticism about Mark Zuckerberg sincerely. This is a man who's an absolute radical extremist when it comes to issues of identity and privacy. He ignores his own privilege when making decisions that impact the lives of billions of people around the world. And his single greatest credential for engaging in civics or the public sphere was stage managed by Sheryl Sandberg in response to an unflattering movie portrayal. Worse, his donation to those Newark schools has yet to yield any substantive results, despite its extravagant scale. There's very little to indicate that Zuckerberg's ability to make a popular social network translates into effective policy advocacy. Worse, his extremism in regard to people's personal information and identities as seen as some esoteric tech concern, and not as a serious threat to civil rights and personal freedom with significant political implications.

Mark Zuckerberg already has tremendous political impact, but it's in realms that most people in mainstream society don't yet identify as being political, including Zuckerberg himself.

But folks like Joe Green (From NationBuilder and Causes, and President and Co-founder with Zuckerberg of, though the site lists him as "Founder") and Daniel Shih (a Rhodes scholar Stanford Grad who worked as a policy analyst for Joe Biden) are much more credible and intentional political actors than Zuckerberg. Both of these guys have engaged with policy for some time, and to their credit they also have reasonable credentials for being sincere in their desire for meaningful immigration reform. So let's look at what they're doing right and wrong.

The Good

  • Lots of money: seems to be backed by a real, serious investment of tens of millions of dollars that they're willing to spend on advancing their agenda. This isn't a casual slacktivist effort by a few techies who want to meet with politicians, it's enough funding to support a protracted engagement in Washington, D.C. That's progress.
  • Pragmatic tactics: They're trying to win, by doing pragmatic things like ad buys in the home districts of congresspeople who are both on the fence on the immigration issue and at risk in upcoming elections. For too many years, geeks have tried using ineffective, unrealistic tactics to influence politicians, but spending money the same way that real, grown-up industries do is important. It's especially key that the spending be accompanied by education of elected officials about issues and how an industry functions — these basic methods are what power successful lobbying efforts from teachers' unions to military contractors, oil companies to pharmaceutical companies.
  • Multi-faceted reform: If I take Green's statements yesterday at face value, then doesn't intend to focus just on the narrow immigration challenges for engineering professionals (so called "skilled" immigrants), but on comprehensive immigration reform, encompassing border security for conservatives and paths to citizenship for undocumented immigrants to appease progressives. This is the claim I'm most skeptical about, but they've repeated this breadth of commitment explicitly, and unprompted, in several different meetings so I'm cautiously optimistic that the intention is sincere.
  • Transparency, kinda: Much of the criticism of has been about their willingness to fund politicians on both ends of the conventional political spectrum (more on that below). But the reason we know backs both the obviously conservative Americans for Conservative Direction and the ostensibly-progressive Council for American Job Growth is because there's actually a surprising amount of information available about where is sending its money. Who knows if this will stay true now that their transparency has been used to criticize the PAC, but thus far at least, it's a surprising amount of visibility into where the funds flow.
  • Proactive, not reactive: We've seen from SOPA/PIPA, and to some degree from later efforts like the CISPA actions led by the Internet Defense League, that geeks are willing to try and stop legislation that they think is bad. But long term, staying on defense all the time doesn't get any points scored, and so I'm happy to see any tech-led initiative that's aimed at actually creating good legislation, not just stopping bad laws.

What Sucks

Given my skepticism about in general, and about Mark Zuckerberg in particular, it's surprising how many positive aspects I've found to the organization. Naturally, I've found just as many negatives to the organization:

  • No standards for what's beyond the pale: This is slightly different from the primary criticisms from the tech industry. Much ink has been spilled by those concerned that is funding ads promoting drilling in ANWR or building the Keystone XL pipeline; TechPresident's Sarah Lai Stirland ably describes the reaction of geeks, which ranges from baffled to disgusted, a perspective well articulated by Josh Miller of Branch. But Green made a smart case for the pragmatic strange-bedfellows approach that is taking on backing candidates, so my concern is more nuanced: What positions won't be supported by We know they'll go counter to most of their ostensible constituents (and a few of their financial backers) on issues like oil drilling, but what about marriage equality? There clearly must be some standards, but are they documented, and if so are they by consensus of all the funders of, let alone by consensus of the industry the organization claims to represent?
  • There's no admission of "collateral damage": Green used the phrase "collateral damage" to refer to the important issues that might get sacrificed in favor of a single-minded (at present) focus on immigration reform, and it seems relevant. If we compromise on marriage equality and bring in a new crop of immigrant workers but many of them aren't able to bring their spouses, how can that be considered success? needs to communicate clearly to those of us who it would like to enlist in a grassroots community about where it draws the line. Will they back ads that promote the border safety plank of the immigration reform bill by using images or language that vilify people of color? What cost is too high?
  • The case for H1B increases is not solid: Within the technology industry, it's been taken as an article of faith for some time that we have a talent shortage in the United States, and that there aren't enough STEM graduates here in the U.S. to meet the industry's needs. I had accepted this conventional wisdom as correct without questioning it for so long that I was deeply disappointed in my credulity when this recent Economic Policy Institute report provided a well-supported set of evidence that we actually don't have a talent shortage. We reflexively talk about overseas talent as the solution to a tech shortage, but we seldom talk about whether there's evidence for that "shortage". The Atlantic's Jordan Weissmann outlines the issue well, and he's been on this beat for a while with pieces like this article from February. needs to either clearly demonstrate that this shortage exists, or explain why these findings don't apply to the technology industry that it is trying to serve.
  • What will we do for these workers? Even if we concede that there's a talent shortage, or if we simply accept that it's a good goal to have smart immigrants coming to the United States, almost no part of the conversation from has been about how they'll help improve conditions for the workers who come to the country on these visas. H1B workers live in a costly, stressful limbo for years on end, with little control over their professional careers and with their personal lives often being stuck in suspended animation. Immigrant workers of all sorts, whether in the technology industry or in so-called "unskilled" trades such as agriculture or the hospitality industry, have significantly less control over their working conditions, wages and negotiations with employers, and meaningful immigration reform has to give a worker a life where they're not living as an indentured servant to a company that can essentially threaten them with deportation-by-firing at any time. must address the issues of dignity and respect that immigrant workers are often denied.
  • You're the richest people in the world, and this is what you work on? Despite's protests that they're working on areas such as education and science funding (both of which I care about a lot!) it's hard to believe this is the most important issue that this group of incredibly powerful and wealthy people can support. Essentially they're pushing an agenda that will make a number of super-rich people slightly more rich, while providing some legitimate jobs and opportunities to people who'll never substantially participate in the profit-taking that's benefactors will enjoy. It'd be easier to believe that will be a positive force if we knew the full breadth of its agenda.

How to get this right

There are a lot of good intentions, and a lot of grave concerns, about Here's what they can do to address these issues, making the PAC both more effective and less fraught with risk.

  • If wants to "win", how is "winning" defined? Provide a clear public list of which policies the organization wants to impact, which bills or proposed legislation they support, and which causes or debates they won't use to achieve their goals.
  • Don't concede to politicians that you have to support their most cynical, extremist issues. Maybe pragmatism requires to back a candidate that is against background checks for guns; Sometimes life has these compromises. But instead of funneling dollars into a campaign vilifying a reasonable compromise on weapon reform, could simply pay money for conventional attack ads against the candidate's opponent on other policy grounds. Starting with zero spine on non-immigration issues that Silicon Valley cares about is going to make it impossible to go back and fix things later.
  • Stop bullshitting about whether this is Zuckerberg's personal agenda or Facebook's corporate agenda. The stated claim this is a personal from Zuckerberg, but given his dominant control of the company what's the difference? If Facebook is blocking ads that protest on the grounds that Zuckerberg is intrinsically part of Facebook's brand, then it's pretty clear what the reality is. Acknowledge that this is both company policy and Zuckerberg's personal focus.
  • Relatedly, Zuckerberg is focusing his social, technical and political powers on a set of goals, but he's never identified those goals nor been made to answer for his extremist, radical principles. This is critical especially because of Zuckerberg's backing of Chris Christie — are tech's biggest names being used to prep a policy platform for a future Presidential campaign? It's easy to overlook, but given the number of big names involved, there are undoubtedly tech execs who are going to contribute to simply to ensure that they're seen as part of Zuckerberg's A-list. That's a hell of a commitment given how opaque Zuckerberg's overall agenda is.
  • Finally: What are they going to do when the coalition falls apart as starts to succeed or fail. What if a candidate who's against foreign aid for preventing malaria asks for an ad from Is Bill Gates going to let his money be spent backing that politician?

One of Mark Zuckerberg's most famous mottos is "Move fast and break things." When it comes to policy impacting the lives of millions of people around the world, there couldn't be a worse slogan. Let's see if we can get to be as accountable to the technology industry as it purports to be, since they will undoubtedly claim to have the grassroots support of our community regardless of whether that's true or not.

Further Reading

And some related pieces from my own archives here:

  • The history and future of web protest, outlining how the tech industry needs to be more proactive after its initial success in fighting SOPA and PIPA. This is also echoed in Ignoring it won't make it go away, where the reflexive libertarianism of Silicon Valley culture again rears its ugly head.
  • Zuckerberg's history of being blinded by his privilege to the serious social and political consequences of his extremism on privacy and identity underpins The Facebook Reckoning. This reached its apotheosis two years later when Facebook made it official at the end of last year that users have no say in site governance policies, by ending user voting on its terms of service.
  • And as a broader look at ways we can impact policy in addition to direct lobbying, there's How the 99% and the Tea Party can Occupy, which is about exactly what it sounds like.

Rebuilding the Web We Lost

December 18, 2012

We have the obligation to never speak of our concerns without suggesting our solutions. I've been truly gratified to watch the response to The Web We Lost over the last few days; It's become one of the most popular things I've ever written and has inspired great responses.

But the most important question we can ask is: How do we rebuild the positive aspects of the web we lost? There are a few starting points, building on conversations we've been having for years. Let's look at the responsibilities we must accept if we're going to return the web to the values that a generation of creators cared about.

  • Take responsibility and accept blame. The biggest reason the social web drifted from many of the core values of that early era was the insularity and arrogance of many of us who created the tools of the time. I was certainly guilty of this, and many of my peers were as well. We took it as a self-evident and obvious goal that people would even want to participate in this medium, instead of doing the hard work necessary to make it a welcoming and rewarding place for the rest of the world. We favored obscure internecine battles about technical minutia over the hard, humbling work of engaging a billion people in connecting online, and setting the stage for the billions to come. To surpass the current generation of dominant social networks and apps, which have unsurprisingly become arrogant and inflexible during their own era of success, we'll have to return to being as hungry and as humble as we were when the web was young. Because last time, we were both naive and self-absorbed enough that we deserved to fail.
  • Don't just meet the UX standards, raise the bar. Obviously, the single biggest reason that the new era of social apps and sites have succeeded where the early efforts did not is because of their massively superior user experience, from the front-end user interfaces to the back-end performance. The expected thing to do would be to hope that a new generation of user-respecting apps came along and matched the best that Facebook and Twitter and Pinterest to have to offer. But actually, due to the profound entrenchment that these platforms already have across culture, the new apps have to be an order of magnitude better in user experience. The good news is, as the rest of the web transitions from making pages to making streams, they'll all be revisiting the tools and technologies they use to connect, and that'll form a big opportunity for new players to participate.
  • Rethink funding fundamentals. As we've seen over and over, the giant social networks seem to inevitably piss off their user bases by changing product features and terms of service in ways that catalyze huge waves of user-generated discontent. But the fundamental reason these sites refused to accommodate so many user demands is because of economics. Those sites make their revenues on models dictated by the terms of funding from the firms that backed them. But as we've discussed before, it's possible to fund contemporary startups either without venture capital, or with a level of efficiency that allows mom and pop startups to reach web scale. To be clear, venture funding powered much of the first wave of social startups and were a big reason they were able to achieve many of their successes, so VC will be part of the ecosystem in the next wave as well. But the terms and dynamics can be profoundly different, supporting startups that are intentionally less efficient, perhaps even making use of the skills of blue collar coders to provide a lot of people will good, solid middle-class jobs instead of optimizing, as current companies do, for making a small number of people enormously wealthy.
  • Explore architectural changes. One of the fundamental reasons that the economics of doing a startup at web scale are different is because of the proliferation of cloud computing and very, very high-performance, reliable open-source components that provide advanced functionality which was prohibitively expensive a decade ago. Instead of backing up a truckload of Dell servers to a data center and then installing a few hundred thousand dollars worth of Oracle software, we can pick and choose a few components off the shelf to get started. More importantly, consumers will start to be able to use the cloud themselves, which removes the current constraint around having to build single, centralized services to provide a great consumer experience. Today, big social apps have to spend millions of dollars handling DMCA takedown requests and FBI investigations into illegal content and in general fighting the web's fundamental desire to be centralized. New apps don't need to obey those constraints.
  • Outflank by pursuing talent outside the obvious. The current wave of the social web doesn't just demonstrate its arrogance through its product decisions. The people involved in creating these platforms are hired from a narrow band of privileged graduates from a small number of top-tier schools, overwhelmingly male and focused narrowly on the traditional Silicon Valley geography. By constrast, the next wave of apps can harken back to many of the best of the early social startups, which often featured mixed-gender founding teams, attracted talent from geographically diverse regions (Flickr was born in Canada!) and were often created by people with liberal arts degrees or even no degree at all. Aside from being the responsible thing to do, having a diverse team generates a variety of unexpected product features and innovations that don't come from the groupthink of homogenous cultures.
  • Exploit their weakness: Insularity. Another way of looking at the exclusionary tendencies of typical Silicon Valley startups is by considering the extraordinary privilege of most tech tycoons as a weakness to be exploited. Whether it's Mark Zuckerberg's unique level of privilege limiting his ability to understand why a single, universal public identity might ruin people's lives, or the tendency to launch apps first to a small, clubby circle of insiders, new startups don't have to repeat these mistakes. And by broadening their appeal from the start, new apps and networks can outflank the big players, paying attention to audiences that hadn't been properly respected last time. That insularity even extends to the tech industry typically ignoring the world of policy and regulations and government until it's too late. While the big tech players have formed their own RIAA, the best case is that they'll focus on overall issues like spectrum policy and net neutrality, ignoring the coming reality of policy changes that will try to protect regular users.
  • Dont' trust the trade press. Another essential step for breaking out of the current tech industry's predictable patterns will be for entrepreneurs and creators to educate themselves about the true history of the tech industry and its products. Our business tends to follow a few simple, repeating cycles, like moving from centralization to decentralization and back, or from interoperable communications to silos and back. But as we've discussed, you can't trust the tech press to teach you about the tech industry, so you'll have to know your shit. Fortunately, a lot of us old-timers are still around, and still answer our emails sometimes, so it's possible to just ask. Imagine if Instagram had simply asked the folks who used to work at Flickr, "Did you ever change your terms of service? What freaked people out?" And even better, we can blog our own progress, because if you didn't blog it, it didn't happen. In that way, we form our own community of practice, our own new peer review process for what we learn about making the web work the right way.
  • Create public spaces. Right now, all of the places we can assemble on the web in any kind of numbers are privately owned. And privately-owned public spaces aren't real public spaces. They don't allow for the play and the chaos and the creativity and brilliance that only arise in spaces that don't exist purely to generate profit. And they're susceptible to being gradually gaslighted by the companies that own them.

Overall, there are lots of ways that the current generation of social sites are vulnerable. There are users that the current tech industry considers undesirable, and technology choices that are considered taboo, and traditions around hiring and product strategy that force them to concede huge opportunities right out of the gate.

As is obvious from the responses I've gotten, many, many people care about a social web that honors certain human and creative values. As I've spent years thinking about the right way to write for this blog, and to build ThinkUp, and to sit on the board at Stack Exchange, and to advise clients at Activate, and to work on all the other stuff I do, I just keep running into the fact that there's a huge opportunity to make a great new generation of human-friendly apps with positive social values.

These new companies will be recognizable in that they'll impact culture and media and government and society, and that they'll invent great new technologies. They'll still make a bunch of money for the people who found them. But they'll look different, both in terms of the people who make them, and the people they serve. And they'll be more durable, not optimized based on current fashions in financing, but because they're built on the accurate belief that there are people who care deeply about the web they use, the works they create, the connections they make, and the humans on the other side of those connections.

The Web We Lost

December 13, 2012

Update: A few months after this piece was published, I was invited by Harvard's Berkman Center to speak about this topic in more detail. Though the final talk is an hour long, it offers much more insight into the topic, and I hope you'll give it a look.

The tech industry and its press have treated the rise of billion-scale social networks and ubiquitous smartphone apps as an unadulterated win for regular people, a triumph of usability and empowerment. They seldom talk about what we've lost along the way in this transition, and I find that younger folks may not even know how the web used to be.

So here's a few glimpses of a web that's mostly faded away:

  • Five years ago, most social photos were uploaded to Flickr, where they could be tagged by humans or even by apps and services, using machine tags. Images were easily discoverable on the public web using simple RSS feeds. And the photos people uploaded could easily be licensed under permissive licenses like those provided by Creative Commons, allowing remixing and reuse in all manner of creative ways by artists, businesses, and individuals.
  • A decade ago, Technorati let you search most of the social web in real-time (though the search tended to be awful slow in presenting results), with tags that worked as hashtags do on Twitter today. You could find the sites that had linked to your content with a simple search, and find out who was talking about a topic regardless of what tools or platforms they were using to publish their thoughts. At the time, this was so exciting that when Technorati failed to keep up with the growth of the blogosphere, people were so disappointed that even the usually-circumspect Jason Kottke flamed the site for letting him down. At the first blush of its early success, though, Technorati elicited effusive praise from the likes of John Gruber:
[Y]ou could, in theory, write software to examine the source code of a few hundred thousand weblogs, and create a database of the links between these weblogs. If your software was clever enough, it could refresh its information every few hours, adding new links to the database nearly in real time. This is, in fact, exactly what Dave Sifry has created with his amazing Technorati. At this writing, Technorati is watching over 375,000 weblogs, and has tracked over 38 million links. If you haven’t played with Technorati, you’re missing out.
  • Ten years ago, you could allow people to post links on your site, or to show a list of links which were driving inbound traffic to your site. Because Google hadn't yet broadly introduced AdWords and AdSense, links weren't about generating revenue, they were just a tool for expression or editorializing. The web was an interesting and different place before links got monetized, but by 2007 it was clear that Google had changed the web forever, and for the worse, by corrupting links.
  • In 2003, if you introduced a single-sign-in service that was run by a company, even if you documented the protocol and encouraged others to clone the service, you'd be described as introducing a tracking system worthy of the PATRIOT act. There was such distrust of consistent authentication services that even Microsoft had to give up on their attempts to create such a sign-in. Though their user experience was not as simple as today's ubiquitous ability to sign in with Facebook or Twitter, the TypeKey service introduced then had much more restrictive terms of service about sharing data. And almost every system which provided identity to users allowed for pseudonyms, respecting the need that people have to not always use their legal names.
  • In the early part of this century, if you made a service that let users create or share content, the expectation was that they could easily download a full-fidelity copy of their data, or import that data into other competitive services, with no restrictions. Vendors spent years working on interoperability around data exchange purely for the benefit of their users, despite theoretically lowering the barrier to entry for competitors.
  • In the early days of the social web, there was a broad expectation that regular people might own their own identities by having their own websites, instead of being dependent on a few big sites to host their online identity. In this vision, you would own your own domain name and have complete control over its contents, rather than having a handle tacked on to the end of a huge company's site. This was a sensible reaction to the realization that big sites rise and fall in popularity, but that regular people need an identity that persists longer than those sites do.
  • Five years ago, if you wanted to show content from one site or app on your own site or app, you could use a simple, documented format to do so, without requiring a business-development deal or contractual agreement between the sites. Thus, user experiences weren't subject to the vagaries of the political battles between different companies, but instead were consistently based on the extensible architecture of the web itself.
  • A dozen years ago, when people wanted to support publishing tools that epitomized all of these traits, they'd crowd-fund the costs of the servers and technology needed to support them, even though things cost a lot more in that era before cloud computing and cheap bandwidth. Their peers in the technology world, though ostensibly competitors, would even contribute to those efforts.

This isn't our web today. We've lost key features that we used to rely on, and worse, we've abandoned core values that used to be fundamental to the web world. To the credit of today's social networks, they've brought in hundreds of millions of new participants to these networks, and they've certainly made a small number of people rich.

But they haven't shown the web itself the respect and care it deserves, as a medium which has enabled them to succeed. And they've now narrowed the possibilites of the web for an entire generation of users who don't realize how much more innovative and meaningful their experience could be.

Back To The Future

When you see interesting data mash-ups today, they are often still using Flickr photos because Instagram's meager metadata sucks, and the app is only reluctantly on the web at all. We get excuses about why we can't search for old tweets or our own relevant Facebook content, though we got more comprehensive results from a Technorati search that was cobbled together on the feeble software platforms of its era. We get bullshit turf battles like Tumblr not being able to find your Twitter friends or Facebook not letting Instagram photos show up on Twitter because of giant companies pursuing their agendas instead of collaborating in a way that would serve users. And we get a generation of entrepreneurs encouraged to make more narrow-minded, web-hostile products like these because it continues to make a small number of wealthy people even more wealthy, instead of letting lots of people build innovative new opportunities for themselves on top of the web itself.

We'll fix these things; I don't worry about that. The technology industry, like all industries, follows cycles, and the pendulum is swinging back to the broad, empowering philosophies that underpinned the early social web. But we're going to face a big challenge with re-educating a billion people about what the web means, akin to the years we spent as everyone moved off of AOL a decade ago, teaching them that there was so much more to the experience of the Internet than what they know.

This isn't some standard polemic about "those stupid walled-garden networks are bad!" I know that Facebook and Twitter and Pinterest and LinkedIn and the rest are great sites, and they give their users a lot of value. They're amazing achievements, from a pure software perspective. But they're based on a few assumptions that aren't necessarily correct. The primary fallacy that underpins many of their mistakes is that user flexibility and control necessarily lead to a user experience complexity that hurts growth. And the second, more grave fallacy, is the thinking that exerting extreme control over users is the best way to maximize the profitability and sustainability of their networks.

The first step to disabusing them of this notion is for the people creating the next generation of social applications to learn a little bit of history, to know your shit, whether that's about Twitter's business model or Google's social features or anything else. We have to know what's been tried and failed, what good ideas were simply ahead of their time, and what opportunities have been lost in the current generation of dominant social networks.

So what did I miss? What else have we lost on the social web?

A follow-up: How we rebuild the web we lost.

Facebook makes it official: You have no say

November 28, 2012


Late on Wednesday, just as Americans were taking off for the Thanksgiving holiday, Facebook announced its intention to change the feedback process for the policies which govern use of its service.

For the last few years, as I'd mentioned in Wired a few months ago, Facebook held sham elections where people could ostensibly vote on its policy changes. Despite lots of responses (the most recent Site Governance vote got far more people participating than signed the secession petitions on the White House website), Facebook never promoted these policy change discussions to users, and the public has never made a substantive impact on site governance.

Now, Facebook follows the steps that most tyrants do, quietly moving from sham elections to an official policy that users will have no vote in site governance.


I'd like to give Facebook the benefit of the doubt on their change to site governance, as the company pinkie-swears that they'll listen to users now. Facebook even offers up their well-intentioned Chief Privacy Officer, Erin Egan, to lead conversations designed to engage with the public about site policies:

As a result of this review, we are proposing to restructure our site governance process. We deeply value the feedback we receive from you during our comment period. In the past, your substantive feedback has led to changes to the proposals we made. However, we found that the voting mechanism, which is triggered by a specific number of comments, actually resulted in a system that incentivized the quantity of comments over their quality. Therefore, we’re proposing to end the voting component of the process in favor of a system that leads to more meaningful feedback and engagement.

But if Facebook believed in this move, and thought it would be embraced as positive by users, it wouldn't have been announced late on the day before Thanksgiving, with a deadline for responses just a few days later. No matter how earnestly Egan wants to hear from the public, this effort is structured in a way where public feedback on site governance will almost inevitably be futile.

Copy and Paste Panic

Though this policy change from Facebook attracted very little attention, as designed by its release just before a holiday weekend, a separate panic about Facebook's terms of service raised its head in the last few days. A copy-and-paste meme inspired thousands of Facebook users to post a message to their profiles asserting their copyright over their content, with explicit calls for Facebook not to exploit their posted data, tied to a bigger perceived threat due to Facebook's recent listing as a publicly-traded company.

Facebook offered a terse refutation of the need for the meme, explaining correctly that users retain copyright on their works by default and thus have no need to share this declaration. (Especially true as posting this message to a Facebook wall would be ineffective for this purpose regardless.)

But Facebook's one-paragraph response to hundreds of thousands, perhaps millions of users expressing concern about their personal data and content shows exactly why their site governance process is unacceptable.

A brief "fact check" about the site's copyright policy assumes that simply correcting the factual error in the premise of postings solves the issue that's being raised. One can almost hear the condescension behind the Facebook response ("they spelled 'Berne Convention' wrong!"), but there's a glaring absence of any effort at addressing the emotional motivation behind so many users crying out.

Facebook sees a large-scale user protest as a problem to be solved, rather than as an opportunity to serve their community. And as a result, they dismissively offer a short legal or technical dismissal of users' concerns over their content, rather than empowering them with simple, clear controls over the way their information is used.

What Facebook Could Do

Facebook and its apologists will say, "but we already have good privacy controls!" and will point to their settings page, which, to their credit, has been admirably simplified.

Now imagine if, instead of posting a "fact check", Facebook had responded to the rapidly-spread cries for intellectual property control on the site by leading and guiding their community in a way that was better for users while also being better for the web.

The same brief explanation that users retain copyright on their content could be followed by two simple controls, the first reiterating the existing site's existing controls for privacy:


And then a second one (this is just a quick, silly mockup I made) could default to the existing rights and protections, but offer a simple interface for Creative Commons or similar license for sharing content.


"But wait!" you cry. "Isn't this much more complicated? Isn't it a bad UX to force a choice on a user?" To which I reply: Not when a desire for control is what they're expressing.

Because the emotional underpinning to the hue and cry over copyright and permissions on Facebook isn't some newly-discovered weird mass fixation on intellectual property rights. It's a simple expression of a lack of trust for Facebook, one where their status as a publicly-traded company makes users feel that Facebook is less accountable to their preferences on privacy and permissions due to its accountability to shareholders to maximize value.

Think about the feelings behind an ordinary Facebook user updating their status to say, in part, "By the present communiqué, I notify Facebook that it is strictly forbidden to disclose, copy, distribute, disseminate, or take any other action against me on the basis of this profile and/or its contents". They're expressing the fear that Facebook is going to disclose their personal thoughts, and exploit them for commercial gain.

You don't solve that level of concern by offering occasional web chats with a Chief Privacy Officer.

Being Of Service

Facebook needs to change its culture to one where it's determined to be of service to users who are worried, even if those users have some misunderstandings about technical details or esoteric legal concepts. Because the fundamental issues of trust and vulnerability are legitimate, and users deserve to have them addressed.

There's also a huge long-term liability for Facebook if these issues of trust aren't addressed. Companies face the wrath of regulators and the vagaries of policy changes not just because of lobbyists and wranglings in the corridors of government, but often because ordinary people have a gut sense that these huge corporations aren't working in their interests. That sentiment can express itself in a million different ways, all of which serve to slow down the innovation of a company, limit its opportunities to reach new audiences, and eventually come to cripple its relevance in the market. Microsoft should offer a sobering example to Facebook of a company that, in addition to breaking the law (which Facebook seems on course to do in a few years with its constantly-shifting policies) had separately earned such mistrust and animosity from the industry and from users that decisive legal action against the company was all but inescapable.

When Facebook went public, Mark Zuckerberg wrote a great letter to investors, which began with a simple statement:

Facebook was not originally created to be a company. It was built to accomplish a social mission — to make the world more open and connected.


We hope to strengthen how people relate to each other.

When Mark says that, I believe him. I do sincerely think that's what he intends to do, and what he hopes for his employees to do. But from the micro-level decisions where a panic over content rights is handled in a perfunctory, dismissive way, to the macro-level where the fundamental negotiation with users over their empowerment as the lifeblood of the service, Facebook has made obvious that they're not culturally ready to meet the mission Mark has laid before them.

It's not too late to change, but Facebook has the obligation to truly embrace empathy for its users. Right now, it's sneaking out the warnings in the dark of night that things are going to get worse before they get better.

Captive Atria and Living In Public

March 5, 2012

The idea of "public space" used to be pretty simple; There were places that we all agreed would be maintained by, and for, the public good. But the past few decades have offered up a valuable, if troubling, experiment with the nature of public space in New York City. For any of us who care about community, whether that's in our cities or on the web, there are some profound lessons to learn.


In 1961, New York City adopted a new zoning program that allowed commercial buildings to exceed the constraints which zoning regulations required of them if they made accommodations for use as Privately-Owned Public Spaces. Fifty years later, the legacy of that decision is documented well on the Department of City Planning website. (On a page which has this wonderful short URL:!)

So, how did this experiment fare? Well, in the words of the city itself:

The results of the program have been mixed. An impressive amount of public space has been created in parts of the city with little access to public parks, but much of it is not of high quality. Some spaces have proved to be valuable public resources, but others are inaccessible or devoid of the kinds of amenities that attract public use. Approximately 16 percent of the spaces are actively used as regional destinations or neighborhood gathering spaces, 21 percent are usable as brief resting places, 18 percent are circulation-related, four percent are being renovated or constructed, and 41 percent are of marginal utility.

In response to the perceived failure of many of these spaces and to community opposition, the types of spaces permitted and their locations have been curtailed in recent years.

Just to highlight that again: only 16% of privately-owned public spaces can be considered successful. By the city's own reckoning, a full 41% are of marginal utility. How complete is the failure? According to all of the research I've been able to do, not a single POPS was used for any of the various #Occupy demonstrations except for Zuccotti Park, though one nearby plaza was used for Occupy planning meetings. (Note: I'd love to be corrected on this.) Imagine: there are ostensibly "public" spaces within the buildings that some of the major financial institutions actually work in, and yet they're so terrible and unusable that even protestors didn't make use of them.

The Beating Heart of the Atrium

Most POPS in Midtown Manhattan take the form of the atrium in an enormous office tower, where the owners post a sign declaring which hours the space is available to the public, and then decorate it with the POPS logo seen above. But there would be precious few New Yorkers who, even if they did recognize that symbol, could tell you what it means.

These public spaces, then are Captive Atria. They're ostensibly "public" spaces which, by nature of being owned by a corporation, are held captive to that company and thus fail in their intended use as public space. Put another way: Government is infinitely more effective and efficient in creating valuable, useful public space than private companies are. The evidence is all over New York City, in the grim, wind-blown pedestrian plazas and captive atria ghost towns which all of us hurry through with hunched shoulders on cold winter days.

What About The Web?

Tellingly, we seldom have discussions about web community in the language of urbanism or urban planning. But what we've seen documented through more than fifty years of experimentation in New York City is that we cannot effectively create public spaces in places that are owned by a company. Yet, we're increasingly ceding our public discourse to platforms and services which exactly mimic the traits of our sterile captive atria in the physical world.

While many in the Occupy movement bemoaned the fact that the private owners of Zuccotti Park had extensive control over what people could do in their space, that control is nothing compared to the typical Terms of Service of a social networking site. Whether it's Facebook, Twitter, Google+ or anything else, no meaningful act of protest would have to be tolerated at all by owners.

But let's put aside protest. What about all the simpler, everyday uses of public space? In captive atria, there are generally no food trucks offering distinctive meals, no performing artists even of the caliber of the musicians that play in the NYC subway, and there's generally such sparse usage that you don't even get the wonderful serendipitous meetings with friends and acquaintances that you get in a true public space.

What we don't realize is that our online public spaces are increasingly being given over to private owners whose spaces share the same weaknesses. It's difficult, if not impossible, to connect to or share with people with whom you haven't declared an explicit relationship. People who you don't follow or befriend or encircle may as well not exist.

More to the point, transgressions of the space, whether political or artistic, are prohibited in practice, even if they aren't always done so in writing. Imagine Improv Everywhere trying to perform its acts of rule-breaking brilliance in the confines of a space that was owned and controlled by a company. Now imagine you wanted to do the same thing online, carrying out an artistic performance which required you to impersonate another person's identity or to falsely claim affiliation with an organization that you don't belong to. In most cases, it simply can't be done.

I care about political protest, sure. But even more often, I care about being inspired by art, and being entertained by comedians and trolls and impersonators and other amusing rule-breakers. I'm happy that New York City has learned enough of a lesson that it's stopped giving license to companies to create POPS, and properly invested in true public spaces. Now I hope we'll take the same lesson to the web, and challenge the big networks to actually change their policies to make some of our shared online spaces truly public. That way, we get heart-warming public creations like this one:

Gaslighting: The Response

November 22, 2011

Well, it seems like my post on how Facebook is gaslighting the web struck a nerve with a lot of folks. I have to give first priority to publishing the responses I've gotten directly from Facebook employees, to be fair to their perspective.

  • Louis Brandy, a Facebook engineer, responded in the comments on my site:

I work at facebook on the team that generates the warning in question (site integrity). This warning appears to me to be a bug and we are currently trying to repro and fix. Continuing, though, to say that the warning is disingenuous is simply not correct. I do not agree with your premise that because you use a social plugin we should automatically whitelist you and exempt you from security checks. Malicious pages do that stuff too.

In this particular case, though, in my opinion so far, this would appear to be a false positive (a bug) from the way the comment widget generates notifications.. Those notification seem to wrongly trip a particular security check.

  • Louis also left what is substantially the same comment on the (surprisingly thoughtful!) Hacker News thread about my post.
  • Christopher Palow, another Facebook engineer emailed me privately to address many of the same issues as Louis. Christopher explained that what he called the "linkshim" (the redirect which handles outbound links) performs a few key functions: It works for spam prevention by preventing access to known spam links, preserves privacy by obscuring your Facebook user ID from potentially being passed as a referrer, and allows referrer logs to show that traffic is coming from Facebook which wouldn't ordinarily happen otherwise if a Facebook user is accessing the site via HTTPS. Christopher offered a detailed perspective on the linkshim redirect which I found interesting, even outside of the context of my particular post:

Every external link clicked on Facebook and sent by Facebook in an email goes through the linkshim (if it doesn't, that's a bug). Each of these links is generated on the fly for the intended viewer and is cryptographically signed for only that viewer. We do this to prevent our linkshim from being abused by spammers as an open redirector. You saw the warning message that occurs when this signature is either missing or you are neither the user who generated the link nor one of that viewer's friends. This happens when our linkshim links get passed around outside of Facebook via IM or email. [Functional example of reproducing this behavior omitted.] In addition to other checks, we added a grab all your friends and check if the signature matches exception in order to mitigate abuse false positives from friends sharing links over IM/email. Only a very tiny fraction of users of the linkshim see the warning you saw.

I feel the language of the warning is pretty benign but I am open to your suggestions on how to improve it. Just keep in mind we have to balance false positives such as the one you saw with the damage that can occur if spammers can exploit our users' trust of Facebook URLs.

  • More compelling to me was this thread on Les Orchard's Facebook profile, where he'd shared a link to my post. In that thread, Mike Shaver offered his perspective on the post. This is particularly notable because Mike is both a (brand new) Facebook employee and a board member for StopBadware. That's an extraordinary combination, and potentially an extraordinary conflict, but Mike's thoughts are worth a read. A highlight:

Facebook is not saying that your site is unsafe, and the text is bog-standard "hey, be careful where you put your password" motherhood and Apple-pie advice. It does not block the load like Google and Mozilla's malware interposition, and the experience is entirely different. Comparing them as you have is frankly fatuous, and I suspect pretty disingenuous as well. Do you really think that FB set out to put that screen up for any reason other than trying to protect users? You're going to be pretty much calling people straight-up liars, based on what they've said publicly about it.

(I'm on the board of StopBadware, and have some idea of what happens to sites when they get on the malware-block list, and what the false positive rate is.)

  • MetaFilter's discussion of my post was also fairly thoughtful, if a bit one-sided, and it was nice to have my ideas discussed on the site without the thread being a referendum on me personally.

I also wanted to address a few key issues that have surfaced since the post first started getting responses:

  • Holy shit, one of the board members of StopBadware works for Facebook! That kind of blew my mind. Now, Mike's a nice guy, and the StopBadware folks are both trustworthy and well-intentioned. But as an industry, we in tech effectively delegate much of our policing to volunteer organizations such as StopBadware, and that leaves the potential for extraordinary conflicts when someone requests (as I did) policing actions against major players which employ members of those organizations.
  • "But you have Facebook comments on this page!" Yep, I do. I'm not some anti-Facebook zealot, and I don't like to make criticisms of companies or products without making a sincere effort to use and understand those tools. I like using Facebook for things like sharing what I'm listening to on Spotify, or to find my friends on Mixel, and I have no objection to it providing services such as commenting in some contexts. It's important to me to communicate that my misgivings about Facebook's relationship with the web is not the rantings of an extremist.
  • "You're saying sites should just be whitelisted and marked as safe simply for using Facebook plugins!" Nope, that's not what I said at all. What I was communicating that given that Facebook is already making the effort to index sites when they use social plugins, they can cross-reference this against databases such as StopBadware which do give feedback on whether a site is safe or not.
  • "These were just honest bugs (or explainable but unfortunate features) on Facebook's part." Let's grant that this is the case for the engineers who work on systems like Facebook's link warning. First, I'm glad if it encourages them to either fix the bugs or update the systems so that spurious warnings are not issued. There is no mechanism by which an ordinary publisher could request such reviews. But second, even if they are just simple bugs the impact is still the same

Overall, I don't ascribe evil or malicious intent to any of the earnest and passionate coders whose responses I've quoted above. But I think some seemingly-innocuous features they work on can work as part of an overall strategy at Facebook that's in tension with the web, and I urge them to consider those implications very broadly whenever possible. All software has bugs, and that's no big deal. Facebook, though, has a unique burden to ensure that it's not accidentally trampling on the web, as an obligation of its dominant position in the web ecosystem, even if that simply means evaluating the potential for bugs or unusual edge cases of features resulting in content on the web being marginalized.

Finally, I am very aware of the privilege that I enjoy by having an audience that both sees and responds to pieces like the one I wrote yesterday. Having had much of my concerns addressed so quickly is gratifying. But to those who think Facebook got a bum rap: The only thing Facebook was facing as a result of my post was the threat of an unnecessary security warning being placed as a gateway to their site. The rest of us face that threat from Facebook every day.

Facebook is gaslighting the web. We can fix it.

November 21, 2011

Facebook has moved from merely being a walled garden into openly attacking its users' ability and willingness to navigate the rest of the web. The evidence that this is true even for sites which embrace Facebook technologies is overwhelming, and the net result is that Facebook is gaslighting users into believing that visiting the web is dangerous or threatening.

In this post I intend to not only document the practices which enable this attack, but to also propose a remedy.

1. You Cannot Bring Your Content In To Facebook

Facebook RSS warning

This warning appeared on Facebook two weeks ago to advise publishers (including this site) that syndicate their content to Facebook Notes via RSS that the capability would be removed starting tomorrow. Facebook's proposed remedy involves either completely recreating one's content within Facebook's own Notes feature, or manually creating status updates which link to each post on the original blog. Remember that second option, linking to each post manually — we'll return to it later.

2. Publishers Whose Content Is Captive Are Privileged

Over at CNET, Molly Wood made a powerful case against the proliferation of Facebook apps that enable ongoing, automated sharing of behavior data after only a single approval from a user. In her words:

Now, it's tempting to blame your friends for installing or using these apps in the first place, and the publications like the Post that are developing them and insisting you view their stories that way. But don't be distracted. Facebook is to blame here. These apps and their auto-sharing (and intercepts) are all part of the Open Graph master plan.

When Facebook unveiled Open Graph at the f8 developer conference this year, it was clear that the goal of the initiative is to quantify just about everything you do on Facebook. All your shares are automatic, and both Facebook and publishers can track them, use them to develop personalization tools, and apply some kind of metric to them.

As Molly's piece eloquently explains, what Facebook is calling "frictionless" sharing is actually placing an extremely high barrier to the sharing of links to sites on the web. Ordinary hyperlinks to the rest of the web are stuck in the lower reaches of a user's news feed, competing for bottom position on a news feed whose prioritization algorithm is completely opaque. Meanwhile, sites that foolishly and shortsightedly trust all of their content to live within Facebook's walls are privileged, at the cost of no longer controlling their presence on the web.

3. Web sites are deemed unsafe, even if Facebook monitors them

As you'll notice below, I use Facebook comments on this site, to make it convenient for many people to comment, and to make sure I fully understand the choices they are making as a platform provider. Sometimes I get a handful of comments, but on occasion I see some very active comment threads. When a commenter left a comment on my post about Readability last week, I got a notification message in the top bar of my Facebook page to let me know. Clicking on that notification yielded this warning message:


What's remarkable about this warning message is not merely that an ordinary, simple web content page is being presented as a danger to a user. No, it's far worse:

  • Facebook is warning its users about the safety of a page which incorporates Facebook's own commenting features, meaning even web sites that embrace Facebook's technologies can be marginalized
  • Facebook is displaying this warning despite the fact that Facebook's own systems have indexed the page and found that it incorporates their own Open Graph information.

To illustrate this second point, I'll include what is a fairly nerdy illustration for those interested. If you're sufficiently interested in the technical side of this, what's being shown is Facebook's own URL linter, as viewed through the social plugins area in the developer console for a site. In this view, it verifies not only that the Open Graph meta tags are in place (minus an image placeholder, as the referenced post has no images), but that Facebook has crawled the site and verified enough of the content of the page to know their own comment system is in place on the page. (Click to view the whole page, with only the app ID numbers redacted.)


How to Address This Attack

Now, we've shown that Facebook promotes captive content on its network ahead of content on the web, prohibits users from bringing open content into their network, warns users not to visit web content, and places obstacles in front of visits to web sites even if they've embraced Facebook's technologies and registered in Facebook's centralized database of sites on the web.

Fortunately, the overwhelming majority of web users visit Facebook through relatively open web browsers. For these users, there is a remedy which could effectively communicate the danger that Facebook represents to their web browsing habits, and it would be available to nearly every user except those using Facebook's own clients on mobile platforms.

This is the network of services designed to warn users about dangers on the web, one of the most prominent of which is Stop Badware. From that site comes this description:

Some badware is not malicious in its intent, but still fails to put the user in control. Consider, for example, a browser toolbar that helps you shop online more effectively but neglects to mention that it will send a list of everything you buy online to the company that provides the toolbar.

I believe this description clearly describes Facebook's behavior, and strongly urge Stop Badware partners such as Google (whose Safe Browsing service is also used by Mozilla and Apple), as well as Microsoft's similar SmartScreen filter, to warn web users when visiting Facebook. Given that Facebook is consistently misleading users about the nature of web links that they visit and placing barriers to web sites being able to be visited through ordinary web links on their network, this seems an appropriate and necessary remedy for their behavior.

Part of my motivation for recommending this remedy is to demonstrate that our technology industry is capable of regulating and balancing itself when individual companies act in ways that are not in the best interest of the public. It is my sincere hope that this is the case.

Further Reading

Many aspects of this conversation are not, of course, new topics. Some key pieces you may be interested in:

  • As I was researching this piece, Marshall Kirkpatrick published Why Facebook's Seamless Sharing is Wrong over on ReadWriteWeb, articulating many of these same concerns. His piece is well worth reading.
  • Albert Wenger of Union Square Ventures makes a strong case for the long-term goal of a network of networks. I fully share his vision here, and hope most in our industry will endorse this idea as well.
  • Molly Wood's excellent look at Facebook sharing which I referenced above is worth reading in its entirety.
  • Blackbird, Rainman, Facebook and the Watery Web was a more optimistic look at how web platforms evolve that I wrote four years ago when Facebook was much less dominant.
  • The Facebook Reckoning a year ago offered a perspective on the values and privilege that inform Facebook's decision-making.
  • My ruminations on ThinkUp and Software With Purpose last week also explored the related danger of Facebook deleting everything you've ever created on their site.

All In Favor

June 9, 2011

By request, a bit of explanation of how and why I favorite things on the internet. (Or favor them. Or like them. Whatever.)

First, where do I favorite? On Twitter, certainly: I love lots of tweets! On Facebook! That's mostly for liking things outside of Facebook, around the web. I like lots of videos on YouTube and on Vimeo, the latter of which probably has the most satisfying like/favoriting animation on the web. I judiciously like things on MLKSHK. I suppose I still favorite things on Google Reader from time to time, which always involves me starring, sharing, +1ing and clicking 10 other buttons in their UI, since I don't really know which one does what. YouTube has both liking and favoriting, too, but somehow that redundancy doesn't bother me as much.

And, perhaps more visibly than anywhere else, I star all kinds of things on Stellar, which is also where many of these favorites get aggregated and shared with others; It's my, erm, somewhat enthusiastic use of favoriting on that service (I'm by far the most prolific star-giver in these early days of the awesome little site) which has inspired the most recent "dude, what the hell?" responses from many of my friends. As of 6 weeks ago, Jason showed me stats where I had about 1/3 more favorites than the next-highest person on the site.

DavoritingWhy am I so prolific with the stars? Well, one part is that I am just an enthusiastic person: I like lots of stuff! There's also social expectation; My favorite (see what I did there?) friend David Jacobs is a master of favoriting and taught me the wonders of the form years ago. In the early days of (now-defunct) Vox, David was specifically called out when the app added favoriting:

By popular demand, we've introduced the ability for users to mark posts, photos, audio, video and books -- from their own blog as well as other Vox blogs -- as favorites. We've nicknamed this feature the "David Jacobs" after friend and Vox user, who, at last count has favorited 1,677 photos on Flickr. It's a great way to keep track of good stuff you've seen on Vox, as well as keep a record of your own things that you particularly like.

Do me a favor

Despite my enthusiasm, my habit of enthusiastically clicking stars and thumbs-up all over the web is not unconsidered. Instead, my intention is fairly consistent, though I'm aware the semantics of these functions are slightly different in all these various services. A few common themes:

  • Acknowledging good work: When someone writes a tweet that makes me laugh or think, or produces a video that's worth the time to watch it, I favorite it or like it as a "reward" of sorts to them. I don't know anyone who doesn't check the number of likes/faves on a work they've made at least some of the time, and that way they know I was rooting for them.
  • Retaining for the future: Favoriting items increases my ability to retrieve them later. I've got Instapaper and Readability and Pinboard all hooked up together so that things I star get saved as bookmarks that I can retrieve later. Similarly, ThinkUp can show me a rough version of the links that were shared in tweets that I've favorited. Basically, I'm more likely to favorite something if I think it's worthwhile enough to return to later.
  • Implicit sharing: These days, this may be my main motivation for favoriting lots of stuff on the web. Truth is, I often miss the curation and editorial fun of the link blog that I used to publish on this site. (Give me a shout if you remember that — it's been seven years since I stopped doing it, old-timer!) By judiciously favoriting good things across the web, I can share them with my friends, assuming they're on services like Stellar and Favstar and Facebook with me.

Now, there are a couple of factors that make my favoriting behavior unusual, compared to normal web users. (Beyond the fact that I probably waste even more time on the web than most people.) First, my social graph is extremely distorted. I have a lot of Twitter followers, so many apps and services that use "popular" Twitter accounts as fodder for link/tweet popularity factor in my favoriting behavior disproportionately. I'm not quite a suggested user on Stellar the way I am on Twitter (since Stellar doesn't have that concept), but I do have an exaggeratedly prominent placement on that site, too, so the impact of my favoriting is amplified.

In short, favoriting or liking things for me is a performative act, but one that's accessible to me with the low threshold of a simple gesture. It's the sort of thing that can only happen online, but if I could smile at a person in the real world in a way that would radically increase the likelihood that others would smile at that person, too, then I'd be doing that all day long.

Further reading

  • ToRead is To Be Human, from 2007, was about the fundamental optimism people have when they tag an article as something they intend to read in the future. Many people use favoriting this way today.
  • An Interview with Paul Bausch that I did on the old Six Apart blog back in 2003. I've assigned the epithet "father of the permalink" to Paul for years, but in reality, just before Paul was implementing permalinks in Blogger, Jason was experimenting with them on I think it's no accident that both are innovating on favoriting, Jason with Stellar and pb with continued experiments (some inane) on MetaFilter. Favoriting is the most fundamental, natural action to perform on the permalink, which is the atomic unit of content on the web.
  • The Power of the Audience, from early last year, was the first time I really explored the idea of favorites as social, gestural feedback for creators. The situation here hasn't gotten much better since then.
  • Actions are the Body Language. Back in 2008, I'd made a page to capture my social actions like favoriting, and wrote a bit about why. (The page of those actions is totally broken now, sadly, but being able to archive those gestures is one of the reasons I'm so passionate about making ThinkUp work well.)
  • Matt Haughey's post on his feedback loops that he relies on online, from early 2010.
  • And finally, last year at Web 2.0 Expo NYC, I asked API head Ryan Sarver why favoriting is an afterthought on Twitter, at 7:27 in this interview video.

I wish there were a website that just had "favorite" (or "like") buttons you could embed, without it being all tied in to all the other crazy stuff Facebook does. But I'd settle for someone hacking ThinkUp to better support archiving my Facebook "likes" so I'd have a record of all the things I enjoy on the web. Actually, what the hell: $500 to the charity of your choice if somebody wants to make that work. Plus, if you tweet about doing it, I'll favorite your tweet.

If You Didn't Blog It, It Didn't Happen

January 4, 2011

Clive Thompson's newest Wired piece argues that the flow of short-form messages as we see on Twitter and Facebook is encouraging longer meditations in other media. I've been thinking about this phenomenon for a while in terms of the impact that it has on me and other bloggers, with the simple premise that I'd like to be writing the content that everyone links to in those media, instead of merely passing around links to other people's work.

I alluded to that concept in the lengthy conversation I had with Clive for the piece, and he captured one of the key points I was trying to make:

“I save the little stuff for Twitter and blog only when I have something big to say,” as blogger Anil Dash put it. It turns out readers prefer this: One survey found that the most popular blog posts today are the longest ones, 1,600 words on average.

Now, while I'd like to self-servingly pretend that everything I say here is "big" in the sense of being important, really what I meant is that some ideas are just bigger than 140 characters. In fact, most good ideas are. More importantly, our ideas often need to gain traction and meaning over time. Blog posts often age into something more substantial than they are at their conception, through the weight of time and perspective and response.

And blogs afford that sort of maturation of an idea uniquely well amongst online media, due to their use of the permalink (permanent link), which gives each idea a place to live and thrive. While Facebook and Twitter nominally provide permalinks as well, the truth is that individual ideas in those flow-based media don't have enough substance for a meaningful conversation to accrete around them.

Felix Salmon touches on this point well in his recent post about the evanescence of Twitter debates. In the particular case he cites, Twitter is the medium that hosted important disclosures that could be material to a case that a current Supreme Court justice has said could impact a future ruling on free speech.

This means that, in an upcoming court case with the highest possible stakes for self-expression in our country, we may be relying on content that will soon be unretrievable by design. (That linked page shows that Twitter will only let you retrieve your last 3200 tweets.) If Kevin Poulsen decides to write 3000 more tweets between now and the time this theoretical case hits the Supreme Court, then we're relying on the (admittedly likely) chance that Twitter, Inc. makes an exception to its policy in order to provide this evidence.

If You See Something, Say Something

But usually, the stakes aren't as high as the future of free speech in America. Sometimes, we just have ideas we're pondering. Maybe we aren't sure of the full implications of something we've noticed, but we want to help catalyze a conversation. It's that sort of brainstorming that led David Galbraith to invent the most popular form of autobiography every created. I get to experience small versions of it myself, as when I noticed a small trend in people's observations about Google lately, which seems to have helped to promote the idea that maybe there has been an inflection point in the evolution of Google's ability to search the contemporary web.

Here's the important thing: The only reason I was able to synthesize those few perspectives is because they were blogged. Certainly, Twitter helped bring those ideas to my attention, and Facebook or any other stream-based service could have played that role as well. But because these points were raised by people I don't always read immediately, the persistence and permanence of their words, as uniquely provided by blogging, is what made it possible for a pattern to emerge.

Capturing those ephemeral moments of observation in a permanent and persistent form is essential for the ideas to mature into something larger. I'd hoped, when I first recommended that everyone consider Twitter a few years ago, that Twitter would emphasize those traits about tweets sent on the service, but until and unless their current design choices change, there's an enormous amount of cultural data that gets lost every day, simply by having been shared through a platform with those constraints.

The Perils of a Low Stress Environment

Now, Twitter and other stream-based flows of information provide an important role in the ecosystem. Perhaps the most important psychological innovation of Twitter is that it assumes you won't see every message that comes along. There's no count of unread items, and very little social cost to telling a friend that you missed their tweet. That convenience and social accommodation is incredibly valuable and an important contribution to the web.

However, by creating a lossy environment where individual tweets are disposable, there's also an environment where few will build the infrastructure to support broader, more meaningful conversations that could be catalyzed by a tweet. In many ways, this means the best tweets for advancing an idea are those that contain links to more permanent media.

Keeping Time

So, if most tweets are too ephemeral to reach their full potential as ideas, what do we do about it? Well, obviously, one big step would be to simply make sure to blog any idea that's worth preserving. It's perfectly fine to tweet about trivialities — I do it all the time! But if you're tweeting about your work, your passion, or something meaningful to you, you owe it to your ideas to actually preserve them somewhere more persistent.

And, of course, I should make a pitch that this is part of the reason I am so enamored of the work the ThinkUp community is doing. A free, thriving, powerful, relatively accessible app that archives Twitter and Facebook updates with a mind towards incorporating them into more persistent and meaningful media is an essential part of the ecosystem. This is especially true as political, social and artistic leaders start to rely on these ephemeral media, without realizing the cultural costs to those choices.

Given enough time, and without substantial changes to the way the big social networks work, if you didn't blog it, it didn't happen. In fact, I first wrote about this idea a bit on Twitter a few years ago. See if you can find it.

Facebook and Skeletons

November 7, 2010

I'm quoted in today's New York Times, talking about how politicians in this year's election have had to confront their pasts, as shared through social networks:

“I think all of us know that politicians would have to confront the Facebook skeletons in their closet, but that it would be in 20 years, not in two years,” said Anil Dash, a technology consultant and pioneer of the blogosphere when it was just beginning in the late 1990s. “By the time the next generation comes into power, they’ll just assume this is how it’s always been.”

I feel pretty solid in saying that we all knew this reckoning was coming; I wrote about it myself in 2002 ("We're all celebrities now, in a sense. Everything that we say or do is on the record. And everything that's on the record is recorded for posterity, and indexed far better than any file photo or PR bio ever was.") and lots of other folks got there earlier than that.

But as I was trying to make clear in the Facebook Reckoning two months ago, this is a problem that disproportionately affects those with fewer social privileges. The rich can often hide their misadventures, and Ivy League graduates can innoculate themselves, as we saw George W. Bush do by calling all of his life before he turned 40 off limits, and as Barack Obama has done by writing a book that mentions the worst of his transgressions so that they'd be boring or considered "old news". Both politicians found great success in having their pasts ignored, if not erased. Frankly, I'm glad for that — I think the tradition of pre-emptive disclosure via analog methods sets a great precedent for others to have their digital pasts ignored as well.

There's also a real danger, though, in the vulnerability that digitally-savvy political candidates have here, that luddite candidates do not. I think it's no coincidence that every single pro-net neutrality candidate lost in last week's elections. There may have been many causes, but if push comes to shove, who's going to be the candidate with an embarrassing Facebook photo: The candidate who is an extensive user of social networks with a long-time history dating back to their young days of poor judgement? Or the one who knows nothing about technology, mistrusts it, and sees it only as a source of potential vulnerabilities? Simply not being afraid of technology may become a political liability if we continue to allow those who resent and fear technology to set the rules of engagement.

There's also the interesting, and consistent, media habit of blaming social networks for every unfortunate indirection that is brought to people's attention, even if social media wasn't involved at all. Take Blake Farenthold (please!). The Texas Republican was photographed in an unfortunate set of duckie pajamas, as illustrated in this brilliant Joe Coscarelli article and slideshow in the Village Voice, which collects all of the damning episodes outlined in the Times story into one perfect piece of linkbait.

But Farenthold didn't post the picture on any social network. As far as we know, no one did. It just got linked directly to the press. And, given enough privilege, that image can be suppressed quite effectively from the most prominent media venues around, just as Farenthold's incriminating picture never appeared in the New York Times. Farenthold won his district by 799 votes.

Call and Response

October 12, 2010

As ever, the best thing about blogging is the conversations it kicks off. Some nice responses to recent posts here and around the web:

  • A few weeks ago I was quoted in the New Yorker talking about Facebook and its impact on culture. In this week's issue of the New Yorker, I pop up again, but this time quoted in Ben McGrath's lengthy profile of Nick Denton. Spoilers: The piece closes with me asking, "Who has more freedom in the media world than Nick Denton?" People seem to like lines like that, as the quote popped up in The NY Times Dealbook blog and elsewhere.
  • At Web 2.0 Expo here in New York last week, I did an interview with Mac Slocum of O'Reilly. While I included the video here in an earlier post, Mac revisited the interview on the O'Reilly Radar blog under the title "Why blogging still matters", focusing on one of the points that came up later in the conversation. It had been a long day with lots of different ideas flowing, so I'd nearly forgotten that we even talked about that, but now I'm pretty glad that part of the conversation was captured.
  • I was a judge in the Apps 4 Africa contest which ended last week with some amazing winners, including my favorite iCow, which came in first place. You can listen to an interview I did with Future Tense about the competition, or check out this video of Secretary of State Clinton congratulating the winners:

  • This past weekend, I attended the Open Web Foo Camp hosted by O'Reilly. While the camp itself is off the record, Scott Rosenberg did an admirable job of documenting one of the key themes of the event — whether the present "open" phase of the web is merely an aberration. I tried to use my access to influential open web advocates at Google, Facebook, LinkedIn, Twitter and other big web companies to push them to make their employers more open and to resist the urge to compromise on their principles despite the understandable pressure they must be under. Hopefully a little friendly urging can give them the support they need to make the right choices.
  • Finally, with ThinkUp well into beta-testing and Expert Labs supporting its first deployment by Code for America, Gina Trapani and I joined John Moore on The Lab for a brief interview about Expert Labs and where ThinkUp is headed.

Okay, that's enough roundup of Other People's Content. We'll return to original content here again shortly.

My Media, It Is So Rich

September 30, 2010

In my blog here, I'm mostly a textual dude. I've made a few little video clips or animated .gifs over the years, but basically, I'm a writer. But today, today! We're going all futuristic streaming internet video with it. If you like it, then maybe I'll do more.

I got to be on The Pipeline, Dan Benjamin's awesome tech interview podcast (subscribe in iTunes, or download the MP3) and join the company of some amazing people that Dan's interviewed. I'm really pleased with how it came out, and if you've got an hour to waste, please do give it a listen. Tip: You can listen at double-speed on your iPod and only waste half an hour.

Then today, I had a great conversation with Ryan Sarver, who's Director of Platform for Twitter, as a keynote Q&A at the Web 2.0 Expo here in New York. We only had a short period of time, but I feel like we covered a lot of really interesting technical questions while considering them in a larger context.

Right after that, we continued the conversation by having Bret Taylor, CTO of Facebook, join Ryan and I. There, I tried to ask broader questions that applied to the efforts of both of these social networking titans.

Finally, I followed up with an interview about our work at Expert Labs, describing the mission a bit and hopefully offering a note of optimism about where Gov 2.0 is headed.

I like to play Words With Friends and Scrabble! Other folks do too. Sometimes I play well.

I can't believe @anildash just played AMELIORATING for 69 points against me. Damn. I'm screwed. than a minute ago via Flickr

Finally, here's Jimmy Fallon and Justin Timberlake with a medley of great moments in hip hop history. I'm not involved in this, but I thought it'd be good if people could see why I like these guys, and also there should be something in this post that I'd actually enjoy watching.


September 27, 2010

Some great responses to, and extensions of, the things I've been writing about lately

  • In response to Forking Is A Feature, Rafe Colburn offers up The cultural implications of forking, rightly pointing out, "Linus Torvalds didn’t set out to change the culture of open source software when he created Git. He was trying to efficiently manage the work being done on the Linux kernel."
  • On a more personal level, Sumeet Jain talks about his first fork as a visceral experience. It's easy to talk about the abstract impact that forking has on culture, but far more profound to talk about the personal elation it can inspire. "When I saw that my tiny sliver of the open source pie was forked, I felt like I’d just shared in one of those excellent post-discovery high-fives."
  • Building on The Facebook Reckoning, Alexandra Samuel wrote The Accidental Online Society, which I found extremely thought provoking:

    It may be fine for the market to pick the winners and losers of the next round of IPOs: for us to vote with our (virtual) feet in choosing whose particular worldview or neuroses will be part of our daily Internet use, and thus to decide which platforms and communities will thrive. But a “vote with your feet” policy is not a great basis for shaping a new set of cultural norms, particularly when so few people feel empowered to make conscious decisions about how to spend their time online, let alone see themselves as shaping a new online society.

  • Revive phoneAbout a year and a half ago, I wrote about launching Last Year's Model. To my delight, the idea is still going strong, and others have explored similar concepts with more focused execution such as the Revive smartphone:

    [U]nlike other electronics, the revive smartphone was developed with re-manufacturing, re-use and recycling in mind. ... The phone itself is designed for easy disassembly allowing it to be recycled easily or simply upgraded through replacing different components. By combining this with simple software upgrades, users can continue to repair their phone rather than throw it out and buy a new one.The concept also includes a membership system that rewards users for keeping their phones longer. ... The backside is covered in a brown leather to reflect the lifespan of the device.

  • That idea of using leather harkens to a key fixation of mine about digital devices: They should break in instead of breaking down. If our mobile devices are about rock and roll, they should be about leather and denim, materials that get better with age, instead of pricey, precious materials that demand reverence from us. I want a device that i own, not one that owns me. It's been almost five years since I first wrote about this type of design as a great way to compete with the iPod/iPhone/iPad juggernaut, and there's still nobody trying that hard, as Joel Johnson illustrates in his great explanation of why he loves costly, flawed, but still endearing wooden iPhone case.
  • Interestingly, many of the lessons in Hospitality and Process are recapitulated more succinctly in this Forbes interview with Warren Buffett and Jay-Z. I've linked to the print version to minimize revenues for the sad-sack magazine that's given a platform to Dinesh D'Souza's idiocy, but this piece is actually worthwhile, and while it purports to be about the financial acumen of these two honorable gentlemen, it's more clearly a story about simple leadership.
  • Finally, if you liked the diagram of the creative process outlined by Danc in his post I linked to in Hospitality and Process, then you'll be happy to know he's hung out his shingle as Spry Fox. Spry Fox follows a deeply collaborative model, where they don't bring all the talented people who build games on staff, but instead rely on a more networked concept where talent assembles for the duration of a project and then are free to work together again in the future. That's exactly how we put together the team we collaborated with at Activate to work on Gourmet Live, and it seems like it's going to become an increasingly popular way to attract the talents of extraordinary people in a way that both fosters collaboration and recognizes that true talents deserve a high degree of flexibility and control over their work and careers.

Blogging is that machine where you can put in a dime and get out a quarter.

The Facebook Reckoning

September 13, 2010

There's a lengthy, excellent profile of Mark Zuckerberg, and by proxy Facebook, in this week's issue of the New Yorker, written by Jose Antonio Vargas. In it, I'm quoted saying about Mark, "If you are twenty-six years old, you’ve been a golden child, you’ve been wealthy all your life, you’ve been privileged all your life, you’ve been successful your whole life, of course you don’t think anybody would ever have anything to hide". That's an accurate quote, but there's even more nuance to my feelings about Facebook than merely remarking on the privilege of its CEO.

First, the requisite disclaimers: I like and use Facebook; I have many friends, including some good friends, who work at the company at all levels of its hierarchy. I've met Mark Zuckerberg a few times, and while we aren't friends, our few interactions have been nothing but cordial. My business partner Michael Wolf famously tried to acquire Facebook during his time at MTV Networks and thinks highly of Mark. The tech projects that I influence, from Gourmet Live to ThinkUp deeply integrate Facebook into their core functions. So I'm not a knee-jerk anti-Facebook reactionary.

The truth is, I care deeply about the culture of the web, and am concerned that many of the decisions Facebook makes are detrimental to its culture, particularly when Facebook inadvertently imposes an extreme set of values on its users without adequately communicating the consequences of those choices.

I'm not the first to raise these issues, particularly in the context of Facebook's stance on privacy. The cover of Time magazine a few months back was about Facebook's privacy issues. Mark responded with a lengthy and somewhat vague response to the concerns, indicating that he realizes the seriousness of the challenge these issues pose for the company. At the time, a scrappy upstart efforts called Diaspora* captured the imagination of those who are frustrated by Facebook's repeated inability to address these issues and raised nearly $200,000 from thousands of donors who hoped to sponsor a significant challenge to Facebook's domination of large-scale social networking. And of course The Social Network, the massive movie based on Facebook's early founding, is only two weeks from release.

But actually, I don't care that much about privacy.

I started blogging when I was younger than Mark is today, and have shared a lot more information publicly about every aspect of my life than he ever has. It's been eight years since I wrote about privacy through identity control, and the key point there seems as relevant today as it did then:

We're all celebrities now, in a sense. Everything that we say or do is on the record. And everything that's on the record is recorded for posterity, and indexed far better than any file photo or PR bio ever was. It used to be that only those who chose career paths that resulted in notoriety or celebrity would face having to censor themselves or be forced to consciously control the image that they project.

What I do care about is this company advocating for a pretty radical social change to be inflicted on half a billion people without those people's engagement, and often, effectively, without their consent. As we saw with the rollout of Facebook's user names feature, the tech industry is very poorly equipped to talk about complex issues of identity and strongly prefers to talk about companies and features instead of communities and choice.

Because, let's be clear, Facebook is philosophically run by people who are extremists about information sharing. Though I choose to talk about my politics, or my identity, or my medical history or my personal relationships, I can do so primarily because I have the privilege to do so thanks to my social standing, wealth, and the arbitrary fact of being born in the United States. I also have an identity that isn't considered offensive or off-putting enough to face serious repercussions.

But what if I weren't my own boss? What if my family couldn't accept parts of my identity? What if I weren't technologically savvy enough to know how to engage with all of the choices about public sharing that Facebook forces me to understand? What if it were important to my own personal identity that public representations of me be colored purple instead of blue, as on Facebook? It's easy to say all of our choices and all the aspects of our identity can be shared if we don't face any serious social or personal consequences for doing so. But most of us are not that fortunate.

I'd say today's story obliquely covers that as well.

Colors don’t matter much to Zuckerberg; a few years ago, he took an online test and realized that he was red-green color-blind. Blue is Facebook’s dominant color, because, as he said, “blue is the richest color for me—I can see all of blue.”

As it turns out, the way we can all express ourselves on Facebook today is literally constrained by the limits of what Mark Zuckerberg can see. I've been in environments that were constrained in similar ways; The first time I entered the Harvard Club here in New York City to visit with a friend, I felt very acutely the implicit judgments of an environment where the fact that I don't have a college education was considered a relevant way to judge my identity. And though I use Facebook, I don't ever forget that it was conceived as a private club for members of the Ivy League as well.

Perhaps by engaging more with its users in an honest way about its radical stance on public sharing, and by clearly articulating the social costs that can arise from that stance, Facebook can become as truly inclusive as it strives to be.

The Twitter API is Finished. Now What?

December 18, 2009

Update: We've got some results already! Joseph Scott at Automattic mentions in the comments that he's added RSD support for the Twitter API to I should also make clear that I am very confident that we'll be building apps on top of this API at Expert Labs, so insofar as I'm the Director of the labs, I've got a vested interest in seeing efforts around an open API succeed.

Twitter's API has spawned over 50,000 applications that connect to it, taking the promise of fertile APIs we first saw with Flickr half a decade ago and bringing it to new heights. Now, the first meaningful efforts to support Twitter's API on other services mark the maturation of the API as a de facto industry standard and herald the end of its period of rapid fundamental iteration.

From here, we're going to see a flourishing of support for the Twitter API across the web, meaning that the Twitter API is finished. Not kaput, complete. If two companies with a significant number of users that share no investors or board members both support a common API, we can say that the API has reached Version 1.0 and is safe to base your work on. So now what?

How We Got Here

Like a lot of folks, I've been thinking out loud and pondering the future of Twitter and open web APIs pretty much all year. Some key ideas have bubbled up:

The Pushbutton Web:

[A]ny site or application can deliver realtime messages to a web-scale audience, using free and open technologies at low cost and without relying on any single company like Twitter or Facebook.

The Web Way vs. The Wave Way

  • Upgrades to the web are incremental.
  • Understanding new tech needs to be a weekend-sized problem.
  • There has to be value before everybody has upgraded.
  • You have to be able to understand and explain it.

Those posts from this summer show that the ideas behind the Twitter API's "overnight" ubiquity have been kicking around in developer circles for months, if not more than a year. Finally, though, we have shipping examples of broad adoption of an API that's lightweight and suitable for today's most interesting applications. It's not just that Twitter's realtime, though of course that is compelling, but also that these APIs are simple enough for weekend hackers to build interesting projects on, and that they're easy to implement even on mobile devices and in almost any programming language.

So, today, we have support for the Twitter API from Twitter (of course), WordPress and Tumblr. I know I saw folks working on this for TypePad's free service when I was at Six Apart, so I'd assume they just wanted to finish OAuth support before supporting it as well. (See below.)

Of course, I don't need to make any suggestions to developers about what to do with these APIs — I'm sure the gears in everybody's heads are turning about cool new applications to build. Instead, I'd like to make a series of suggestions for the entire Open Twitter API ecosystem, based on what we've learned from past successes and failures in APIs around blogging.

What Server Developers Should Do

  • Please please please support OAuth: It's egregious that the newest implementations of the Twitter API are stil encouraging people to share their passwords with third-party sites. Five or ten years ago, this was common practice in APIs because we didn't have better options. Twitter started out using shared passwords, but mercifully has started to bring OAuth support online. But for new services to be encouraging the horrible practice of users entering their passwords into every application willy-nilly is just unacceptable. I think we have a two-week window or so within which the new services supporting the Twitter API could announce their intention to support OAuth and really catalyze client developers into doing the wrong thing, but I fear we may lose another generation of API evolution to this terrible practice. If just one or two services announce intent around OAuth by the end of the year, client developers will follow — if you use WordPress or Tumblr, encourage your service provider to do this. (This is usually where I'd insert a dozen examples of how sharing passwords screws users, services, and the ecosystem, but I know that developers often just use shared passwords because they're lazy. Do the right thing, guys. The client devs will follow along.)
  • Support Really Simple Discovery: The RSD format isn't sexy by today's standards, but grew organically out of some smart thinking from when blogging APIs were at the same state of maturity as today's tweeting APIs. Instead of reinventing the wheel, developers should look at supporting RSD and looking for something like a "tweetsapi" endpoint for these new services. That way, any arbitrary site can advertise that it supports the Twitter API, or even future versions of an open MetaTweets API. Pay attention to which APIs are listed as "preferred".
  • Think about overloading of source: The source element of status updates in the Twitter API is very interestingly open-ended, and supports use of URLs. Instead of merely advertising your client app, smart use of rel attributes and URLs here could help bootstrap some very interesting new potential.

What Client Developers Should Do

  • Support RSD: Same logic as above.
  • Start sharing parsing libraries: Client devs going to be doing a lot of duplicate work to parse out URLs and usernames and hashtags and maybe even slashtags. But almost every scripting language supports some similar variation on regular expressions, and if you're using that method to tease out meaning from short messages, then lighten your burden by sharing the load. John Gruber's work to share his URL parsing rules should be a model for a dozen other GitHub projects — compete on features and execution, but not on these fundamental interpretations of text.
  • Build in the big services, but support the little ones: You'll naturally want to offer menu options for users of the big, centralized hosted services. But (perhaps as part of supporting RSD), you should allow for all of us to have arbitrary Twitter API endpoints on our own domain names — this is good for the web!

What Every Developer Should Do

  • Think about piping Twitter API endpoints together: I think it will be common for some kinds of applications that support the Twitter API to be both clients and servers, supporting piping content through, and perhaps applying transformations to the updates. This idea of daisy-chaining services together is likely only going to happen if a lot of parts of the infrastructure support OAuth well, but has the potential to be truly revolutionary if the ecosystem allows it to happen.
  • Start looking at people's firehoses: Twitter's firehose of all status updates is about to be broadly available for developers, I know about the free TypePad firehose from my time at Six Apart, and I think WordPress will sell you access to theirs, but I haven't yet been able to find a reference for one for Tumblr. No matter — we should assume that free, open versions of these are coming, and start to figure out how to encourage similar collaboration around the reading side of things, now that the writing side of things is getting hashed out.
  • Consider adopting a "+2 Rule": The natural inclination right now for geeks of a certain type is to start dreaming up new standards bodies, or how they can participate in the Open Web Foundation to make a Super Awesome Twitter API Evolution Committee. Here's my recommendation: Don't. Don't do any of that shit, and don't run off to make membership badges for the Treehouse Club quite yet. Instead, just iterate and ship. Keep making new apps and see what you can do to stretch the limits of the existing methods and structures. I love the new geocoding and contributor aspects of the Twitter API, but as I said at the top of this post, I think the period of rapid iteration on the core Twitter API is ending, as new efforts going forward will have to reach consensus.

The good news is, consensus around evolution of the Twitter API can happen simply by saying to each other, "If two application developers who share no common investors or board members can reach agreement around an extension to the API, and between them they have a significant enough number of users to be relevant, then we should all just adopt their work."

This is important because it reframes the conversation from being about technical merits, and all the boys who like to play with APIs always think they know what's "better". I'm sure if I wanted to waste an afternoon, I could tell you a dozen ways in which the Twitter API could be "improved". But guess what? That shit does not matter. Adoption matters, and I'm heartened by the fact that people seem to be getting that.

So, get to work! Please give me feedback if I'm wrong or being stupid about one of my recommendations, but if not, then just start hacking. Stop encouraging people to share passwords, start encouraging services to share tweets, and let's all join in a hearty session of finger-pointing and mockery in Facebook's general direction for their sense of Not Invented Here having overshadowed their opportunity, because they could have really clearly done an "embrace and extend (and extinguish)" on the Twitter API if they hadn't wanted to make their own system a year ago, and now they've lost that power.

Finally, thanks a lot to Dave Winer for essentially inspiring a lot of players in blogging to move towards embracing the Twitter API. Sure, lots of us had the idea, and I've spent a lot of times in meetings arguing for this stuff across the industry, and Automattic and Tumblr and others were brave enough to embrace it. But I don't think anybody's done more to publicly advocate for an open Twitter API than Dave. I'm glad we've evolved as a community to the point where these kinds of breakthroughs aren't the contentious, immature shitfests they used to be.

Preconceived Notions and The Web As Water

August 6, 2009

I've really been enjoying the response to my recent blog posts — here are some more thoughtful replies.

Rafe Colburn, one of my favorite bloggers for a decade now, followed up my Apple and secrecy post with "Apple vs. my preconceived notions":

In one scenario, this is a bubble of sorts. Apple may be doing OK now, but they’re headed for a big crash when people get sick of their behavior. In another scenario — one that I think is, sadly, more likely, Apple continues as they are, adjusting when it must to address reality, but only in the most minimal way.

I've also really been enjoying watching Dave Winer's work recently. In the past we were both too young and stubborn to realize we're amused by a lot of the same things (There's my refrain of "We hate most in others that which we fail to see in ourselves" again!) but these days it is just plain entertaining to watch Dave go. My amusement is amply covered in "Anil's belly laugh", which mentions my response to Dave's latest bit of hacking. As I mentioned on my Twitter account, I also recorded an episode of the Bad Hair Day podcast with Dave and Marshall Kirkpatrick last week.

Speaking of podcasts, This Week in Google is a new one featuring Leo Laporte, Jeff Jarvis and Internet Hero Gina Trapani. This week, they had a very nice look at The Pushbutton Web towards the end of the show. I'm delighted how many people have told me they found that post valuable or useful in talking about this whole area of innovation. Since I'm a lousy coder, writing blog posts like that is the most helpful thing I can do.

Finally, as it's come up in several contexts lately, it's probably worth repeating the key point of a post I wrote two years ago, which attracted some attention then but is probably even more relevant today. The core concept is about "The Watery Web":

It's not true to say that Facebook is the new AOL, and it's oversimplification to say that Facebook's API is the new [MSN] Blackbird, or the new [AOL] Rainman. But Facebook is part of the web. Think of the web, of the Internet itself, as water. Proprietary platforms based on the web are ice cubes. They can, for a time, suspend themselves above the web at large. But over time, they only ever melt into the water. And maybe they make it better when they do.

Thanks, as always to people who've responded to what I've written, and especially to all of those who've taken these posts as starting points and expanded the ideas into some truly inspiring creations.

Call me "Nostradashus"!

July 31, 2009

From my Facebook Usernames post on June 10:

July 31, 2009: MySpace announces MyAddress, a feature for providing more control over the URL where your MySpace profile appears. Instead of constraining users to a few choices as Facebook does, MySpace gives users very broad control over what kind of address they can have. As a result, users pick web addresses that exactly match their obscure handles on the service, instead of using their real names.

From TechCrunch today, talking about MySpace's announcement for July 31 (emphasis mine):

Here’s what else is nice: Because MySpace has had so-called vanity URLs since its inception (unlike Facebook, which just rolled out the feature), you can use those as your email address with the new MySpace Mail. So for a page that resides at, the email would be, for example. And, if you don’t like the vanity URL you currently have, MySpace is giving you the opportunity to change it to something else (assuming it’s available). This would also change your vanity URL for your profile.

I love the tech industry. I really do.

All Around The Web

July 13, 2009

There have been a lot of great conversations around and about some of my recent posts; Here are some highlights.

My post about Google's Microsoft Moment seems to have really struck a nerve. First amongst the responses, from my perspective, is prominent Googler Matt Cutts' "Why Googlers should read Anil Dash's post. The open-mindedness and willingness to take constructive criticism that Matt shares with a number of his colleagues at Google (I'd also highlight Karen Wickre, who helps lead Google's efforts in blogging and on Twitter) are going to be the factor that decides whether or not Google falls prey to the dangers outlined in that essay. Matt concludes his comments with a simple, and inspiring exhortation:

Googlers, ask yourself how you can help make another one of those moments where you’re proud to work at Google. I think those moments are a great way to keep from becoming just another large company. And if Googlers are open to posts like Anil Dash’s, the web is tell us tons of things it wants us to do, or how to do them better.

Some other notable conversations around these ideas popped up as well:

  • The presciently-named (but independent) Google Operating System blog offers up Google's Changing Corporate Culture.
  • Ex-Googler, current FriendFeeder and all-around good guy Kevin Fox takes issue with some of my points in Google's Apple Moment. Kevin raises the point that a lot of Googlers did: It's okay for Google to have two different operating systems because they serve two different markets. I don't disagree — I did ask in my original essay "If the keyboard works with my fingers instead of my thumbs, I should use Chrome OS and not Android?" and folks at Google have already responded to me privately with, in effect, "Actually, that might not be such a bad way to put it..." My point, though, was not that it doesn't make good technical sense to have these systems. Rather, that sort of roadmap complexity makes it hard for casual outside observers to believe that their needs are being put ahead of the company's platform ambitions. I'll chalk up the lack of clarity there to my own poor editing and the fact that John Gruber highlighted that bit on Daring Fireball, which may have put more focus on what was a relatively minor point.
  • I loved, and totally agree with, Mini-Microsoft's Microsoft Has Turned The Corner. This makes explicit what was part of the subtext of my essay: Even Microsoft doesn't do this kind of shifty crap anymore, if they can help it. And to their credit, Microsoft since Ray Ozzie's ascension has also seemed to regain their ambition and clarity around creating innovative products. I'm not sure if that's correlation or causation, but it's good to see regardless, and this is a post well worth reading in full.
  • One of my favorite bloggers, Mike Masnick of TechDirt, asks Has Google Reached The Perception Tipping Point? The post consists of the single word "Yes." Okay, not really, but it's still thoughtfully argued and especially highlights Google's recent track record in the area of intellectual property and DRM, which is TechDirt's strongest suit.
  • Finally, a couple more mentions in bigger media: BusinessWeek's Rob Hof offers up a critical look at Google's strategy, which is a welcome change from most mainstream press that tend to slavishly puff up any pronouncement of this scale that comes out of the tech industry. Similarly, Alex Pham at the LA Times puts the Chrome OS story in the context of Microsoft's Office 2010 announcement today. Matt Asay has an even more skeptical take over at CNET. And finally I thought MG Siegler's brief post about the back-and-forth between me and Matt Cutts offered up a nice perspective on the perils and potential of this inflection point in Google's evolution.

Here's a two-fer: Chris Anderson's CNN Commentary on Google, Microsoft, and Free. Chris ruminates on whether the tech giants' habit of entering new markets with free products funded by the obscene margin they make in their primary lines of business is going to face legal scrutiny in the future. Recommended if you liked either Google's Microsoft Moment or Free Criticism, Science After Data and Airport Books.

Reason mag's Tim Cavanaugh had an amusing riff that referenced that post of mine from the other day: Resolved: The New York Times Should Be Staffed By Volunteers, Like Meals On Wheels. I thought it was a fun read, at least.

And if you're seeking out even more comment on these topics, Silicon Alley Insider has a pretty fun thread in response to my Free Criticism post, along with a slightly more inane one in response to last month's post about The Future of Facebook Usernames.

Finally, some stuff that's actually related to my day job:

  • Tony Dearing at has a really smart take on a conversation we had about what that site is doing to make a real community-focused local news website. I think the current team has the best chance at success of any of the dozens of similar efforts I've seen over the past several years.
  • In a similar vein, Ken Edwards has a detailed look at what it's taken to build the new BG Views community at Bowling Green State University. It's always fun to watch a project like that from afar and get to see a new community take off.

Thanks to everyone for great comments on my previous posts, and even more for the inspiring conversations that have happened around these topics. And a specialy thanks to the many of you who've shared links to these pieces on Twitter: @padmasree, @timoreilly were instrumental in kicking off the broader conversation around the recent Google post, and it was really gratifying to see @wilw find a quote in my Free Criticism essay that really seems to have struck a nerve.

Exclusive: The Future of Facebook Usernames

June 10, 2009

The whole world A small number of super-geeky obsessives is abuzz over the upcoming launch of Facebook Usernames, an exciting new feature that will let you put some parts of your name into a web address.

Since its announcement yesterday, there's been a lot of excited discussion of the feature, but in a exclusive I can exclusively report this exclusive look at the future of the feature. We'll also cover how the feature's rollout will be covered by the technology trade press and the mainstream press.

June 13, 12:01am: Facebook launches Facebook Usernames. The gold rush is on!

June 13, 12:01:45am: The first completely irrational, highly unlikely theory about how Google indexes Facebook Usernames is emitted from the ass-end of the SEO industry.

June 13, 12:02am: An enterprising and mischevious nerd who is definitely not me squats on the username of a notable tech trade reporter like Michael Arrington.

June 13, 12:06am: The Facebook username system starts getting overloaded with new registrations, but their tech team clears it up in 20 or 30 minutes, for a total period of slowness of about 35 minutes.

June 13, 12:15am: A first wave of "It's alive! Go get your name!" posts go up on various technology blogs, noting that the service is running a little bit slow. None of these posts mention that you can also register a real domain name that you can own, instead of just having another URL on Facebook.

June 13, 12:45am: TechCrunch discovers that one of its writers can't get his preferred spelling for his name, and notices that registrations in the system are running a bit slow. A Twitter search reveals four other people discussing the same problems, and one person that can't get to the feature at all. The phrase "The Facebook Username debacle" is first used, and becomes the preferred sobriquet for the feature forevermore. 70% of commenters mention that "Facebook Username" can be abbreviated "FU", and each thinks he is the first to think of it.

June 13, 1:00am: #FUFacebook becomes a Trending Topic on Twitter. People who are presently whining about how expensive it is to buy a new iPhone because they bought a new iPhone last year will have the chance to see how obnoxious and overprivileged they look, but will not take the opportunity.

June 13, 9:00am: The first mainstream coverage of the feature happens in the New York Times, which includes a one-line mention of the launch in a lengthy feature about Twitter's Verified Accounts. The story includes a colorful illustration of Kanye West, but omits any mention that you can also register a real domain name that you can own, instead of just having another URL on Facebook.

June 13, 12:01pm: Twelve hours after launch, a passionate and vitriol-filled flame war erupts amongst web protocol nazis about exacly which 300-series HTTP header should be used to redirect from the old /profile.php?id=500012896 URLs to the new system. Mark Pilgrim writes an overwrought essay on the topic, and 300 Ubuntu users on netbooks use their free hand to Digg the post. For these nerds, "The Facebook Debacle" refers to the improper headers used on the redirects, instead of the few minutes of difficulty in registering names.

June 13, 12:01pm: Within twelve hours of launch, the OpenID community will quietly reach out to Facebook, asking about their plans to have Facebook Usernames become an OpenID provider. Facebook will decline to comment, Simon Willison will write a thoughtful and persuasive essay about the benefits to Facebook if they were to embrace such a thing, and Andy Baio will politely link to it on Waxy Links. Months later, Facebook will actually implement the feature. For this community, this cordial and fruitful exchange will be referred to "The Facebook Debacle".

June 13, 3:00pm: I tweet a link to my post about owning your identity online. The few folks who read it seven years ago nod in agreement, and everyone else considers reading the short URL to be equivalent to reading the post.

June 13, 4:04pm: A white guy named David discovers every variation of his name on Facebook is already taken, and finally reconsiders the condescending contempt he's always had for black people who give their kids unique names. This tiny bit of racial reconsideration is the only unequivocally good news to come out of the Facebook Usernames launch.

June 15, 8:00am: A short and punchy Monday morning story about Facebook Usernames appears on USA Today's website, omitting any mention of the word "debacle", but dwelling heavily on the preponderance of URLs with "Hussein" in them. This vestige of the Presidential elections, which briefly convinced college kids that changing their middle name on a website was a form of political activism, is promptly interpreted as an Al Qaeda sleeper cell movement by most of the paper's print readers.

June 15, 9:00am: In its opening weekend, between four and five million people (or between two and three percent of Facebook's ostensible population) will have registered Usernames for themselves. Tech pundits will say "everyone has a Facebook Username now" and refer to that assertion as an article of faith in future posts about identity. It will not be until 2012 that Facebook supports the full range of diacritical marks and international characters that let the other 5.5 billion residents of Earth use their name as a username, but this fact will go unreported.

June 15, 11:00am: In response to the growing buzz on TechMeme about "The Facebook Debacle", Mark Zuckerberg posts on Facebook's blog with the news that the company has created the Facebook Username Dispute Resolution Community. This group is tasked with creating a policy for arbitrating who can get what names, how conflicts between different people's usernames are resolved, and how to report squatting of usernames. The post omits any mention that you can also register a real domain name that you can own, instead of just having another URL on Facebook. Over the course of its 18-month existence, the FUDR Community will attract thousands of comments, 80% of which ask for The Old News Feed back, and 85% of which contain one or more typos or deviations from standard spellings of English words.

June 15, 1:00pm: LinkedIn posts a thinly-veiled but very smart update on their company blog that happens to mention in passing that they've had friendly usernames as an option for URLs for years, and that it's more likely you want to show your professional profile to the world as the first Google result for your name. The post omits any mention that you can also register a real domain name that you can own, instead of just having another URL on LinkedIn.

June 15, 1:30pm: The Google Profiles team will write a post that features a bad pun in the headline, ostensibly serving to announce some minor recent feature update, but in reality just trying to remind people that hey, you can get a Google URL. The post omits any mention that you can also register a real domain name that you can own, instead of just having another URL on Google.

June 15, 2:00pm: An enterprising young web hacker will realize that there are 24 items in this list, which means that if you add in a free space, you can very easily turn this post into a 5×5 Facebook Username Bingo Card. Combined with the Creative Commons license on this blog, it makes for a fun idea and a Flickr Pool pops up for people to show the FU Bingo cards they've generated.

June 15, 4:00pm: The first web-savvy celebrity in Hollywood will hold a meeting with their marketing team about what it will take to get their preferred username. During this meeting, the smartest person in the room will try to explain the difference between a profile page and a fan page, why there are different processes for getting vanity URLs for each, and why a person or brand doesn't have control over all the fan pages that can be created about them. That person will be ignored by everyone else for the duration of the meeting. The issue will be ignored by Facebook for nearly a year.

June 16, 10:00pm: The guys release a service that lets you sign in with your Facebook Connect account and automatically find what variations of your name are available as real domain names. While the feature is cool and works well, the team struggles to get press coverage for the launch, since it's predicated on the idea that you can register a real domain name that you can own, instead of just having another URL on Facebook.

June 19, 9:00am: The Bureau of Labor Statistics will announce the unemployment numbers for May, showing a loss of 660,000 jobs, with 1/3 of them being white-collar jobs. Coincidentally, 220,000 unemployed professionals will realize to their horror that their Facebook profile now ranks above their LinkedIn profile if a prospective employer googles them, and that they have no idea how to use Facebook's privacy settings.

July 31, 2009: MySpace announces MyAddress, a feature for providing more control over the URL where your MySpace profile appears. Instead of constraining users to a few choices as Facebook does, MySpace gives users very broad control over what kind of address they can have. As a result, users pick web addresses that exactly match their obscure handles on the service, instead of using their real names.

February 15, 2010: Microsoft launches a similar URL service for usernames, providing friendly URLs for millions of people on Windows Live and XBox Live, and providing the feature to more people in one day than Facebook has succeeded in delivering usernames to in eight months. Because the announcement goes out on President's day, and because it's Microsoft, nobody really notices except for a two-line mention on Mashable, half of which is a joke about Bing. Both Microsoft's own announcement and the Mashable post omit any mention that you can also register a real domain name that you can own, instead of just having another URL on

October 31, 2010: AOL has an internal meeting about providing friendly URLs to users of AIM and Bebo, and make a bold decision to put it on their 18-month roadmap.

I hope you find this overview of the future timeline of Facebook Usernames useful to understand where this exciting feature is going in the future, how our industry will adapt and respond to this sort of innovation, and how our tech trade press will hold the powerful company's feet to the fire as this sort of capability becomes mainstream in the years to come.

And oh hey, add me as a friend on Facebook! Or become a fan of mine! Or something.

DRM and Friends

January 19, 2009

This one's been kicking around in my head for a while, and maybe you can all help me understand it. With any contemporary social networking site, I can control who has access to the things I share, and I can update or change or revoke the relationships that enable that access at any time.

For example, I can share a photo on Flickr with just my friends, or a post on Vox with just my family, or display my profile on Facebook to just my contacts. And then, if somebody ceases to be my friend, I can change their status and they no longer have access to that information. It's a unliateral, technologically enforced restriction, and circumventing the restriction would be tantamount to hacking and likely to get you banned from any of these services.

So, with all of that being said, how are privacy settings on social networks different than DRM restrictions placed on media content files from companies? Is it because I'm not a corporation? Is it because the DRM technology is provided by Flickr or Facebook instead of by Apple's iTunes or Microsoft's WIndows Media? Is it because I only (theoretically) grant permissions to dozens or hundreds of people, instead of millions?

This is a genuine question, because it's something I'm not sure I know how to articulate. I can certainly identify the difference in intent, but I am not sure I can explain the difference in definition. Feel free to comment here, or post a link or reply to @anildash on Twitter and I'll collect the best explanations I get.