Joho the BlogAugust 2014 - Joho the Blog

August 28, 2014

The problem with civility

Talk about “civility” on the Internet always makes me a little nervous. For a bunch of reasons.

First, I generally try to be civil, but I’d hate to see a Net that is always and only civil. Some rowdiness and rudeness is absolutely required.

Second, civility as a word feels like it comes from a colonial mentality, as if there are the civil folks and then there are the savages. I’m not saying that’s what people mean when they use the term. It’s just what I sometimes hear.

Third, civility is so culturally relative that demanding that someone be civil can actually mean, “Please play by our rules or you shall be removed from the premises!” Which is I guess what gives rise to my second reason.

Fourth, civility seems to be more about the form of interaction, the rhetoric of the interchange. That’s fine. But given a preference, I’d be hectoring people about dignity, not civility. You can be civil without according someone full dignity. If you treat someone with dignity, the civility — and more — will follow. For example, you’ll actually listen. (Note that I fail at this frequently.)

Fifth, civility and dignity are not enough to make the Net the place it ought to be. I would love to see being welcoming taken as a core value for the Best Net, that is, for the Web We Want. Welcoming the stranger is one of the originary traditions of the West, from Abraham inviting strangers into his tent, to the underlying theme of The Odyssey. (Another of our originary traditions: killing or enslaving strangers.) In embracing the stranger, we accord them dignity, we recognize our differences as something positive, and we humble ourselves. So, given a choice, I’d rather hear about a welcoming Net than a merely civil one. (Here’s a shout-out to the new Pew Internet study that reports that we’re not welcoming unpopular views on social media.)

Point five-and-a-half is: Just as welcoming precedes civility, safety precedes welcoming. This is a half point not because safety is a half point but because the outstretched welcoming hand entails reassuring the stranger that she is safe. And more than safe. Safety is essential, but it is obviously nowhere near enough.

Let me be clear, though. When I talk about “the Net,” I’m being misleading. The entire Net is not going to be characterized by any one set of values. And we don’t need the entire Net to be welcoming, civil, and a place where all are treated with dignity. (Safety is a different matter.) But we do need more of the Net to be welcoming, civil, and dignifying. And we absolutely need the networks where power and standing develop to go far beyond civility.


August 25, 2014

Have social networks replaced groups?

Maxim Weinstein responded in an email to my post about what the social structure of the Internet looked like before Facebook, making the insightful point that Facebook meets the four criteria Clay Shirky listed for social software in his 2003 keynote at eTech. Here are the four with Max’s comments appended:

1. Provide for persistent identities so that reputations can accrue. These identities can of course be pseudonyms.
2. Provide a way for members’ good work to be recognized. < "Like" buttons, sharing
3. Put in some barriers to participation so that the interactions become high-value. < have to accept friend requests
4. As the site’s scale increases, enable forking, clustering, useful fragmentation. < pages

Max goes on to note some nuances. But his comment, plus a discussion yesterday with Andrew Preater, a library technologist at the Imperial College of London, made me think how little progress we’ve in fact made in supporting groups on the Net.

For example, Clay’s post from 2003 marvels at a “broadband conversation” in which the participants communicated simultaneously by conference call, through a wiki, and through a chat, each from a different source. Since 2003, there are now services that bundle together these different modalities: Skype and Google Hangouts both let a group talk, video, chat, and share documents. (Google Docs are functionally wikis, except without the draft>compile>post process.) So, that’s progress…although there is always a loss when disparate services get tightly bundled.

What’s missing is the concept of a group. As my 2003 post said, members of a group know they’re members of a group with some persistence. Skype and Hangouts let people get together, but there are no tools there for enabling that configuration of people to persist beyond the session. Groups are important because they enable social ties to thicken, which means they’re especially useful now to mitigate the Brownian motion of sociality on the Internet.

Likewise, Facebook, Google Groups, Twitter, and the other dominant forms of “social software” (to use the term from 2003) are amazing at building social networks. At those sites you can jump into borderless networks, connecting to everyone else by some degree. That’s pretty awesome. But those sites do not have a much of a concept of a group. A group requires some form of membership, which entails some form of non-membership. Usually the membership process and the walls that that process forms are visible and explicit. This isn’t to say that groups have to have a selection committee and charge dues. A group can be widely open. But the members need to be able to say “Yeah, I’m part of that group,” even if that means only “I regularly participate in that open discussion over there.” A group is a real thing, more than the enumeration of its members. If all the members leave, we have to be able to say, “There’s no one in that group any more. Too bad.”

If the walls around the group don’t include and exclude the same people for each member, then it’s a network, not a group. Not all of your friends are my friends and vice versa. But everyone in the Chess Club is in the Chess Club. The Chess Club is a group. Your friends and my friends on Facebook are part of a social network. Not that’s there anything wrong with that.

Now, I realize in saying this I am merely expressing my Old Fartdom. “Why, in my day, there were groups and not all these little networks of people with their twittering and their facial books.” The evidence for this is the generational divide on email. Email remains my most important social software for all the reasons that The Kids have moved to Facebook: email goes to the people I choose, is slower, results in semantically sequential threads of call-and-response, and is archived. But I especially like email because mailing lists are crucial to my social and intellectual life. I have been on some for over twenty years. Most of what I know about the Internet comes from the lists I’m on. I’ve reconnected with some of my academic philosophical roots via a mailing list. Mailing lists are so important to me because they are online groups.

So it’s entirely possible, in fact it’s probable, that the Internet has not made a lot of progress supporting groups because our culture no longer values groups. We’ve gone from Bowling Alone to Twitch Bowls 300. Old-timers like me — even as we celebrate the rise of networks — should be permitted a tear to dampen our dry, furrowed skin.


August 22, 2014

The social Web before social networks: a report from 2003

The Web was social before it had social networking software. It just hadn’t yet evolved a pervasive layer of software specifically designed to help us be social.

In 2003 it was becoming clear that we needed — and were getting — a new class of application, unsurprisingly called “social software.” But what sort of sociality were we looking for? What sort could such software bestow?

That was the theme of Clay Shirky’s 2003 keynote at the ETech conference, the most important gathering of Web developers of its time. Clay gave a brilliant talk,“A Group Is Its Own Worst Enemy,” in which he pointed to an important dynamic of online groups. I replied to him at the same conference (“The Unspoken of Groups”). This was a year before Facebook launched. The two talks, especially Clay’s, serve as reminders of what the Internet looked like before social networks.

Here’s what for me was the take-away from these two talks:

The Web was designed to connect pages. People, being people, quickly created ways for groups to form. But there was no infrastructure for connecting those groups, and your participation in one group did nothing to connect you to your participation in another group. By 2003 it was becoming obvious (well, to people like Clay) that while the Internet made it insanely easy to form a group, we needed help — built into the software, but based on non-technological understanding of human sociality — sustaining groups, especially now that everything was scaling beyond imagination.

So this was a moment when groups were increasingly important to the Web, but they were failing to scale in two directions: (1) a social group that gets too big loses the intimacy that gives it its value; and (2) there was a proliferation of groups but they were essential disconnected from every other group.

Social software was the topic of the day because it tried to address the first problem by providing better tools. But not much was addressing the second problem, for that is truly an infrastructural issue. Tim Berners-Lee’s invention of the Web let the global aggregation of online documents scale by creating an open protocol for linking them. Mark Zuckerberg addressed the issue of groups scaling by creating a private company, with deep consequences for how we are together online.

Clay’s 2003 analysis of the situation is awesome. What he (and I, of course) did not predict was that a single company would achieve the position of de facto social infrastructure.

When Clay gave his talk, “social software” was all the rage, as he acknowledges in his very first line. He defines it uncontroversially as “software that supports group interaction.” The fact that social software needed a definition already tells you something about the state of the Net back then. As Clay said, the idea of social software was “rather radical” because “Prior to the Internet, the last technology that had any real effect on the way people sat down and talked together was the table,” and even the Internet so far was not doing a great job supporting sociality at the group level.

He points out that designers of social software are always surprised by what people do with their software, but thinks there are some patterns worth attending to. So he divides his talk into three parts: (1) pre-Internet research that explains why groups tend to become their own worst enemy; (2) the “revolution in social software” that makes this worth thinking about; and (3) “about a half dozen things…that I think are core to any software that supports larger, long-lived groups.”

Part 1 uses the research of W.R. Bion from his 1961 book, Experiences in Groups that leads him, and Clay, to conclude that because groups have a tendency to sandbag “their sophisticated goals with…basic urges,” groups need explicit formulations of acceptable behaviors. “Constitutions are a necessary component of large, long-lived, heterogenous groups.”

Part 2 asks: if this has been going on for a long time, why is it so important now? “I can’t tell you precisely why, but observationally there is a revolution in social software going on. The number of people writing tools to support or enhance group collaboration or communication is astonishing.”

The Web was getting very very big by 2003 and Clay points says that “we blew past” the “interesting scale of small groups.” Conversation doesn’t scale.

“We’ve gotten weblogs and wikis, and I think, even more importantly, we’re getting platform stuff. We’re getting RSS. We’re getting shared Flash objects. We’re getting ways to quickly build on top of some infrastructure we can take for granted, that lets us try new things very rapidly.”

Why did it take so long to get weblogs? The tech was ready from the day we had Mosaic, Clay says. “I don’t know. It just takes a while for people to get used to these ideas.” But now (2003) we’re fully into the fully social web. [The social nature of the Web was also a main theme of The Cluetrain Manifesto in 2000.]

What did this look like in 2003, beyond blogs and wikis? Clay gives an extended, anecdotal example. He was on a conference all with Joi Ito, Peter Kaminski, and a few others. Without planning to, the group started using various modalities simultaneously. Someone opened a chat window, and “the interrupt logic” got moved there. Pete opened a wiki and posted its URL into the chat. The conversation proceeded along several technological and social forms simultaneously. Of course this is completely unremarkable now. But that’s the point. It was unusual enough that Clay had to carefully describe it to a room full of the world’s leading web developers. It was a portent of the future:

This is a broadband conference call, but it isn’t a giant thing. It’s just three little pieces of software laid next to each other and held together with a little bit of social glue. This is an incredibly powerful pattern. It’s different from: Let’s take the Lotus juggernaut and add a web front-end.

Most important, he says, access is becoming ubiquitous. Not uniformly, of course. But it’s a pattern. (Clay’s book Here Comes Everybody expands on this.)

In Part 3, he asks: “‘What is required to make a large, long-lived online group successful?’ and I think I can now answer with some confidence: ‘It depends.’ I’m hoping to flesh that answer out a little bit in the next ten years.” He suggests we look for the pieces of social software that work, given that “The normal experience of social software is failure.” He suggests that if you’re designing social software, you should accept three things:

  1. You can’t separate the social from the technical.
  2. Groups need a core that watches out for the well-being of the group itself.
  3. That core “has rights that trump individual rights in some situations.” (In this section, Clay refers to Wikipedia as “the Wikipedia.” Old timer!)

Then there are four things social software creators ought to design for:

  1. Provide for persistent identities so that reputations can accrue. These identities can of course be pseudonyms.
  2. Provide a way for members’ good work to be recognized.
  3. Put in some barriers to participation so that the interactions become high-value.
  4. As the site’s scale increases, enable forking, clustering, useful fragmentation.

Clay ends the talk by reminding us that: “The users are there for one another. They may be there on hardware and software paid for by you, but the users are there for one another.”

This is what “social software” looked like in 2003 before online sociality was largely captured by a single entity. It is also what brilliance sounds like.

I gave an informal talk later at that same conference. I spoke extemporaneously and then wrote up what I should have said. My overall point was that one reason we keep making the mistake that Clay points to is that groups rely so heavily on unspoken norms. Making those norms explicit, as in a group constitution, can actually do violence to the group — not knife fights among the members, but damage to the groupiness of the group.

I said that I had two premises: (1) groups are really, really important to the Net; and (2) “The Net is really bad at supporting groups.”

It’s great for letting groups form, but there are no services built in for helping groups succeed. There’s no agreed-upon structure for representing groups. And if groups are so important, why can’t I even see what groups I’m in? I have no idea what they all are, much less can I manage my participation in them. Each of the groups I’m in is treated as separate from every other.

I used Friendster as my example “because it’s new and appealing.” (Friendster was an early social networking site, kids. It’s now a gaming site.) Friendster suffers from having to ask us to make explicit the implicit stuff that actually matters to friendships, including writing a profile describing yourself and having to accept or reject a “friend me” request. “I’m not suggesting that Friendster made a poor design decision. I’m suggesting that there is no good design decision to be made here.” Making things explicit often does violence to them.

That helps explains why we keep making the mistake Clay points to. Writing a constitution requires a group to make explicit decisions that often break the groups apart. Worse, I suggest, groups can’t really write a constitution “until they’ve already entangled themselves in thick, messy, ambiguous, open-ended relationships,” for “without that thicket of tangles, the group doesn’t know itself well enough to write a constitution.”

I suggest that there’s hope in social software if it is considered to be emergent, rather than relying on users making explicit decisions about their sociality. I suggested two ways it can be considered emergent: “First, it enables social groups to emerge. It goes not from implicit to explicit, but from potential to actual.” Second, social software should enable “the social network’s shape to emerge,” rather than requiring upfront (or, worse, topdown) provisioning of groups. I suggest a platform view, much like Clay’s.

I, too, ask why social software was a buzzword in 2003. In part because the consultants needed a new topic, and in part because entrepreneurs needed a new field. But perhaps more important (I suggested), recent experience had taught us to trust that we could engage in bottom-up sociality without vandals ripping it all to part. This came on the heels of companies realizing that the first-generation topdown social software (e.g., Lotus Notes) was stifling as much sociality and creativity as it was enabling. But our experience with blogs and wikis over the prior few years had been very encouraging:

Five years ago, it was obvious beyond question that groups need to be pre-structured if the team is to “hit the ground running.” Now, we have learned — perhaps — that many groups organize themselves best by letting the right structure emerge over time.

I end on a larger, vaguer, and wrong-er point: “Could we at last be turning from the great lie of the Age of Computers, that the world is binary?” Could we be coming to accept that the “world is ambiguous, with every thought, perception and feeling just a surface of an unspoken depth?”



August 17, 2014

fadeOut, fadeIn jQuery-style

Time for another in my series of occasional posts over-explaining simple programming tasks that took me longer to figure out than they should have.

Let’s say you’re writing a bit of JavaScript and want to fade the text of a component out, change the text, and fade it in. Assume you’re using jQuery to handle the fades. Assume that the component has an ID of “fader” and you want its initial text of “First” to be replaced by the text “Second.” Ok?

Here’s the simple HTML:

<div id="fader">First</div>

With jQuery, you fade an element out by first selecting the particular element. which you can do by putting its ID in quotes and prefixing it with a #: $("#fader"). Then you tell that element what method you want to execute, which in this case is the jQuery “fadeOut” command, with a duration expressed in microsecondsmilliseconds. Put ’em together and you get the simple-but-powerful jQuery statement: $("#fader").fadeOut(500);. Likewise for the fadeIn command.

If you’re me, the first thing you’ll try will be:


function fadeMe(){









Click here to give it a try on the following sample text:


That’s not right. At least in my browser (Chrome). Instead of fading out “First” and fading in “Second,” the word “Second” fades out and then in. Presumably that’s because Javascript isn’t waiting for jQuery to complete the fadeout before moving to the instruction to substitute “Second” for “First” as the element’s text.

So here’s a way that works. (Note that I’m not saying it’s the best or right way. If it’s worse than that, if it’s actually the wrong way, please leave a comment and I’ll link to it at the top of his post. Thanks!)


function fadeMe(){


$(“#fader”).fadeOut(500, function(){









Click here to to try it on the text below:


The difference is that the second way adds a function to the jQuery’s fadeOut command that is invoked only after the fadeOut is completed. That function changes the text of the element and fades it in.

(Click here to reset both examples.)

(PS: I created the tables for the code by pasting it in here.)

Comments Off on fadeOut, fadeIn jQuery-style

August 16, 2014

Reason #554 we need gigabit Internet connections

Despite the claims of some — and unfortunately some of these some run the companies that provide the US with Internet access — there are n reasons why we need truly high-speed, high-capacity Internet access, where n = everything we haven’t invented yet.

For example…

If we had truly high-speed, high-capacity Internet access, protesters in Ferguson might have each worn a GoPro video camera, or even just all pressed “Record” on their smartphones, and those of us not in Ferguson could have dialed among them to see what’s happening. In fact, it’s pretty likely someone would have written an app that treats co-located video streams as a single source to be made sense of, giving us fish-eye, fly-eye perspectives anywhere we want to focus: a panopticon for social good.

Comments Off on Reason #554 we need gigabit Internet connections

August 15, 2014

From Berkman: Zeynep and Ethanz on the Web We Want

This week there were two out-of-the-park posts by Berkman folk: Ethan Zuckerman on advertising as the Net’s original sin, and Zeynep Tufecki on the power of the open Internet as demonstrated by coverage of the riots in Ferguson. Each provides a view on whether the Net is a failed promise. Each is brilliant and brilliantly written.

Zeynep on Ferguson

Zeynep, who has written with wisdom and insight on the role of social media in the Turkish protests (e.g., here and here), looks at how Twitter brought the Ferguson police riots onto the national agenda and how well Twitter “covered” them. But those events didn’t make a dent in Facebook’s presentation of news. Why? she asks.

Twitter is an open platform where anyone can post whatever they want. It therefore reflects our interests — although no medium is a mere reflection. FB, on the other hand, uses algorithms to determine what it thinks our interests are … except that its algorithms are actually tuned to get us to click more so that FB can show us more ads. (Zeynep made that point about an early and errant draft of my commentary on the FB mood experiment. Thanks, Zeynep!) She uses this to make an important point about the Net’s value as a medium the agenda of which is not set by commercial interests. She talks about this as “Net Neutrality,” extending it from its usual application to the access providers (Comcast, Verizon and their small handful of buddies) to those providing important platforms such as Facebook.

She concludes (but please read it all!):

How the internet is run, governed and filtered is a human rights issue.

And despite a lot of dismal developments, this fight is far from over, and its enemy is cynicism and dismissal of this reality.

Don’t let anyone tell you otherwise.

What happens to #Ferguson affects what happens to Ferguson.

Yup yup yup. This post is required reading for all of the cynics who would impress us with their wake-up-and-smell-the-shitty-coffee pessimism.

Ethan on Ads

Ethan cites a talk by Maciej Ceglowski for the insight that “we’ve ended up with surveillance as the default, if not sole, internet business model.” Says Ethan,

I have come to believe that advertising is the original sin of the web. The fallen state of our Internet is a direct, if unintentional, consequence of choosing advertising as the default model to support online content and services.

Since Internet ads are more effective as a business model than as an actual business, companies are driven ever more frantically to gather customer data in order to hold out the hope of making their ads more effective. And there went out privacy. (This is a very rough paraphrase of Ethan’s argument.)

Ethan pays more than lip service to the benefits — promised and delivered — of the ad-supported Web. But he points to four rather devastating drawbacks, include the distortions caused by algorithmic filtering that Zeynep warns us about. Then he discusses what we can do about it.

I’m not going to try to summarize any further. You need to read this piece. And you will enjoy it. For example, betcha can’t guess who wrote the code for the world’s first pop-up ads. Answer:   Ethan  .

Also recommended: Jeff Jarvis’ response and Mathew Ingram’s response to both. I myself have little hope that advertising can be made significantly better, where “better” means being unreservedly in the interests of “consumers” and sufficiently valuable to the advertisers. I’m of course not confident about this, and maybe tomorrow someone will come up with the solution, but my thinking is based on the assumption that the open Web is always going to be a better way for us to discover what we care about because the native building material of the Web is in fact what we find mutually interesting.


Read both these articles. They are important contributions to understanding the Web We Want.

Comments Off on From Berkman: Zeynep and Ethanz on the Web We Want

August 12, 2014

[doggerel] Great Blue

Because it’s August and I’m at a lake:

The great blue is such an ungainly bird
that “heron” should be an explainly word.

It flaps so slow as it takes to the air
I could beat it by climbing stairs.

It’s great, it’s blue, it’s a little absurd.
A pile of sticks became a bird.


Robin Williams was a mensch

I admired Robin Williams even though he wasn’t exactly my cup of tea as a comedian. But, he was obviously brilliant, and by all reports was humble and kind. We need to celebrate people who turn down every opportunity to act like assholes.

Here’s just one example. Robin Williams met Christopher Reeve at Julliard and the two remained close friends. When Reeve became paralyzed, Williams stayed by him, a source of laughter and hope. From what I’ve heard, you could not have asked for a better friend.

It makes me all the sadder that Robin Williams just couldn’t carry on with his extraordinary, difficult, and very human life.


August 9, 2014

Tim Berners-Lee’s amazingly astute 1992 article on this crazy Web thing he started

Dan Brickley points to this incredibly prescient article by Tim Berners-Lee from 1992. The World Wide Web he gets the bulk of the credit for inventing was thriving at CERN where he worked. Scientists were linking to one another’s articles without making anyone type in a squirrely Internet address. Why, over a thousand articles were hyperlinked.

And on this slim basis, Tim outlines the fundamental challenges we’re now living through. Much of the world has yet to catch up with insights he derived from the slightest of experience.

May the rest of us have even a sliver of his genius and a heaping plateful of his generosity.


Saturday songify fun

I find this recycling of culture to be fascinating. Or, to be more precise, the recycling of culture is culture. No recycling, no culture. Anyway, I’m mainly blogging these because each is fun in its own way.

These are in chronological order, but you might want to start out by going backwards. [August 24 2014: Chrome decided to start autoplaying these. Ack! So I’ve replaced the embedded versions with links. Sorry!]

The original kid’s interview

The interview songified

The Gregory Brothers sing the songification

(I am a massive Gregory Brothers fan.)

Comments Off on Saturday songify fun

Next Page »