Archives for category: Musings

Photo Attribution: Will Clayton

Happy Birthday, BookGlutton! You were but a glimmer in our eye in Fall of 2006. A few months later, when the two of us started working on you full time (Jan 07), we knew we were doing something exciting – after all, who had heard of social reading then? In the last four years we’ve built a lot. We’ve seen the industry change right before our eyes. We were in private beta when the Kindle came out. The iPhone was brand new. We were early.

Looking at things from a startup perspective, early isn’t always positive. In truth, we would have done better to build less and start later – but then we wouldn’t have experimented as much. We spent a lot of time building for laptops, wishing tablets would finally happen. We had to build our own social network from the ground up because Facebook didn’t have an API (and then pivot when it did). And we had very little to base our interface on…so we made most of the user experience up as we went along.

What we built at BookGlutton includes:

BookGlutton grew to become a huge system, and has given us plenty of opportunities to geek out. Our initial plan was clear: we just set out to build a reading system with social features. As we moved through the process we found that, to do this, we needed to build a social network to use it…and then a publisher’s system, a content repository, etc. Not everything we built has been a resounding success, but we have learned about all the different aspects of digital publishing and where it intersects with the web in unique ways. Buy us a beer sometime…we can talk about it for hours!

    Over the years we’ve seen some cool uses of the site:

  • People in Iceland embedding Dracula with BookGlutton’s widget and reading it together.
  • Teachers in Phoenix using BookGlutton to teach English as a Second Language (ESL).
  • Japanese classrooms using it to read Jane Austen.
  • Grandparents forming groups with grandkids and leaving them notes.
  • NYU students logging on at midnight to meet as a class to prepare for class.
  • Authors embedding the BookGlutton widget on their websites and leaving comments inside for their readers.
  • Soldiers using it to read with people back home.

It’s been a good ride. We recently launched a new user-funnel with some social gaming aspects and tight Facebook integration (yes, I should send a newsletter out about it). With ebooks taking off, more people are starting to see things our way. We’re excited to see where that leads us next. Aaron and I have launched a separate endeavor, ReadSocial, which brings what we’ve learned about social reading to other reading systems. BookGlutton still has great things in store…

Thanks to all the people who’ve used and supported BookGlutton over the years!

-Travis
travis at bookglutton dot com

Advertisement

In the foggy avenues of outer San Francisco, where the strange musky odor of the towering Eucalyptus trees along Park Presidio permeates the air, Brewster Kahle hosted a conference for a small number of people deeply interested in the convergence of books and the Web. The conference, called Books in Browsers, was heavy with talk of “social reading.”

Not once did anyone mention “social publishing.” But I’ve come to believe that we need to think about this concept before we turn so much attention to “social reading.”

So what does “social publishing” mean? I did a quick search and found no formal definition, but I did find this:

http://billboardsandcavedrawings.wordpress.com/2009/10/28/what-the-hell-is-social-publishing/

That includes, if you scroll down the page, a definition from one person I would consider authoritative on the topic, Richard Nash. From Loudpoet’s (Guy LeCharles Gonzales) interview:

“‘Social (publishing)’ is taking the book and making it much easier to have a conversation with the book and its writer, and have conversations around the book and its writer.”

This is a decent definition that gets at certain key activities in the business of social publishing. The problem is I don’t think Richard’s intent was to define social publishing, but to define the term “social” as it applies to publishing. That’s different than the concept I’m trying to define.

Put simply, social publishing is concerned with everything that happens around a book after it has been sold.

To most people, this just doesn’t sound radical. But to those familiar with the publishing industry as it stands represented today by the largest American publishing houses, it should sound revolutionary. Because, you see, most publishers, especially those bound up most by the business of printing, packaging and shipping books, don’t care what happens to a book after it’s sold. Other people in publishing care — authors, editors, agents, publicists, etc. But when we say “publisher” we really mean the entity which is in the business of publishing things. Whether it’s one guy or one large company, the fact of the business is that the end goal of each book is to be sold. That’s as far as the process goes. And that’s the big problem today.

Social publishing is the natural evolution of publishing as a business. It encompasses the Web and all new digital distribution platforms, including the way people read and discover on them. It includes social reading, which is really just reading, an act that has always been social. Social publishing requires a deep interest and study of what happens to a text after it is disseminated — how readers interact with it, how they share it, how they copy it, how they talk about it — and it requires action arising from that deep study.

Since I’m still working out my definition of cloud publishing, I will also add that cloud publishing is most definitely a form of social publishing, and perhaps the best example of it. Cloud publishing is social publishing that dates its birth in 1993. If you think about this, and think about the digital-only production, distribution and consumption chain of the Web and the different motivations for publishing there and the interesting things that happen to content after it’s published there, then you’ll see everything that traditional publishers need to learn.

Those who date their enterprise earlier than that would do well to realize that what happens in, around and on the pages of a book after it’s sold are definitely matters of concern for future business.

Aaron’s presentation at Books in Browsers had 3 fundamental points, and 2 product announcements, so I’d say he pulled his weight among the heavies of publishing present at the Internet Archive last week. It was an impressive guest list, and in truth we were honored to be presenting. His presentation, The World Wide Web (of Books?), is embedded below. I felt these were the three most important concepts:

  • The future requires a new kind of publisher, the Cloud Publisher, who asks “What else can we charge for?” This is a common way for people with web-development backgrounds to approach new markets – what can we create a market for using new technology? Think Foursquare. Think Twitter. It particularly makes sense when facing the Gorgon of online publishing and distribution.
  • Communities are different than Audiences. The ideal community for a book may not align with its current audience. This explains why some retail chains can’t make the jump to community, and why communities are best built from the ground up. This will be a blog post in itself, but it’s worth mentioning here.
  • There are many layers that will live on top of social books, including the metadata layer, hyperlinked layer, and, you guessed it, the social layer.

-Travis Alber

As a designer, you conceive your design with the core values of a project in mind; you strive to reflect the ideas and feelings behind it. Contrary to that, the first lesson in web development is always separate your design from your code. It’s important that projects be flexible. A myriad number of screen sizes and devices mean the “presentation layer” should be designed to change, particularly when you use web technology. Moreover, partnerships will impact your design.

Aaron and I have been making websites for 15 years, so we get that. Most people don’t know it, but what we’ve built at BookGlutton is flexible in many ways. Easiest to change is the look and feel. Over the years we’ve had a number of conversations about offering our “BookClub in a Can,” the ability to export the social experience to other sites, so they can curate their own book clubs. Business considerations and content deals ultimately kept these projects from launching, and BookGlutton remained a destination site. But it’s fascinating to see how associating the reading experience with a different brand affects your relationship to it.

ANSWERBAG

ANSWERBAG

GOODREADS

Skinning the Reader takes almost no time at all. However, it changes the experience significantly. The Reader takes on the trappings of that community.

TOR

ELLE

All the mockups listed here preserved the buttons and layout, but even that can change. It makes for interesting consideration. Sometimes these mockups were presented in meetings; sometimes the discussion ended prematurely. See more skins, as well as the original BookGlutton design on Flickr.

A good reason to go digital?

Bed Bugs at the NY Public Library

I moved to NYC four months ago, and not a week goes by without a warning about the bed bug epidemic. Beware movie theaters! Avoid used-book stores! Leave abandoned furniture where it lies! I hear all these warnings, and I often think of the library.

I’m a library person. Growing up, I spent rainy Saturdays wandering the poorly lit stacks of vintage sci-fi. I loved it. When I was planning my move, I specifically thought about the New York Public Library. I imagined myself beating the summer heat in a cool corner, flipping though a book I surreptitiously happened upon.

With all the hype, I haven’t visited the library at all. It’s a shame. I’m sure the library is doing everything it can to combat the outbreak. Maybe all my information is hearsay and conjecture. Either way, considering my options has made me aware of one benefit digital books have over their print counterparts: they’re bug-free. (Well, at least the infectious-kind.)

One last note: since I work in the start-up world, I’m obligated to break my moratorium on movie theaters this weekend, in order to see The Social Network (even if I have to stand up the whole time). I’d imagine the library is only a matter of time.

Rueda Bench

Sitting in Union Square Park this morning, watching as drops from yesterday’s deluge were made into rain again by breezes in the canopy, catching the sunlight as they fell, I tried to resist the urge to look to the bench at my left, where some guy seemed to want everyone to know how much fun he was having with his music. “Oh yeah!” he kept exclaiming, “CCR! Creedence Clearwater. Born on the Bayou.” And started bobbing and making guttural noises which sounded not quite like the bass line and rhythm of that song.

I really just wanted to watch the shining drops that kept falling in the center of the park whenever a breeze came up, but he kept exclaiming louder, and soon all I could focus on was his aggressive enthusiasm for music I couldn’t hear.

I thought, if I shift to the far end of my bench to give him some distance, he might calm down. But this action seemed to encourage him.

Whenever you encounter someone like this in New York, you run through a threat assessment first. Might they stab you? Are their hands empty? Do they look capable of strangling someone? I ran through the possibilities in my head, medicalizing his behavior, coming to all kinds of rational conclusions as to what might ail him, leaning toward something typically harmless like Asperger’s, and finally, as he burst out with an even louder “CCR! Oh yeah, I can’t believe I’m listening to Rock N Roll Music,” and as I looked across at a man in commando garb, doing boxing routines, and another man, mostly toothless, pouring a beer into a plastic cup he’d pulled from the recycling, I thought, “Oh yeah. Oh yeah is right. They’re all just maniacs.”

It’s never wrong when you find yourself surrounded by maniacs to ask yourself what exactly you’re doing in the same place at the same time. The truth is, I was sitting there obsessing, in my own way, on the idea that has consumed us for four-and-a-half years now, that the act of picking up a book to read is an important event that implicitly connects you to the other readers of that book AT THAT MOMENT. At its most far out, the notion that no matter how obscure the book, that finally we might have an efficient way to know that we’re not alone in sitting down to read it, that the connection may now be made explicit, whether we take action through it, or simply become aware of it via, say, the arrival ding of another reader. At the very least, we should be able to ANNOUNCE it in some way, if we want. Don’t call it a “check-in,” or you’ll get immediate backlash from people, at least in this city. Whatever we decide to call it — paragraph ping, book ack, page status — it’s that moment when you let your circle of trusted connections know that you’re engaging with something permanent. After all, books have the same kind of permanence that locations do, even though their actual locations move around. Their interiors are worlds in themselves, full of solid reference points that change either very little or not at all. If you check into the third paragraph of a chapter of Faulkner, it’s as likely to change as a particular piece of bedrock in Central Park. Conversely, twenty years from now, what good is it to know that you checked into your local Starbucks?

Maniacs exaggerate simple truths about human nature. There’s a part of us, when we engage with something we like — whether it’s queueing up CCR or Kanye, or opening a copy of Go Tell It On The Mountain or Song of Myself or the Bible — that rejoices in the idea of having other people know. No one can say that they have never, when listening to music or looking at art or reading a great story, thought to themselves “Oh yeah! I can’t believe I’m experiencing this! I want people to understand that this experience is worth having!”

This is normal. Otherwise, these things wouldn’t move us in the first place.

I don’t know why I’ve become so intent on this idea, but I’m probably going to keep struggling with it until I get it right. And I’m well aware that in the last three years, everyone else has become interested in it, and there are plenty of implementations of things that attempt to make this idea reality. But I haven’t yet seen one that gets it right. Even my own. I wish I could convey it better with words, but I think the only expression of this that will open people’s eyes is actual execution and delivery.

Add this into the mix as one more theory on the future of the Book. Following the evolution of current distribution channels along to an interesting and somewhat sustainable outcome, and forgetting the notion that printed paper pages will somehow endure, let’s suppose that “bird books” and landlocked books continue to exist in harmony, except with landlocked books being essentially shells of what we think of as paper books.

Propelled along by Moore’s Law, the landlocked book sheds its paper interior, which is also the bulk that makes it so costly to ship and produce, and gains instead a slim flat panel display, mounted on a cardboard structure to give it a certain width. This may be the day such a display becomes cheaper to produce than its packaging — 7 cents, to be inexact.

The system contained on the chip in such a device is harder to predict. Perhaps it will be KindleOS, or iPhoneOS, or Android. It doesn’t matter to anyone, because you won’t download other books onto it, or jump on the web, or even be online. It will be engineered to deal with one specific book. If that book has video, it will be compiled to handle that, or if it needs to pull in web feeds, it will have basic network capability. Etcetera.

The binding, hard cover, and jacket will look and feel just exactly as book readers would expect it to look — and no print book designers will be harmed in this evolution, they will all just become jacket designers. The thickness of the packaging will even allow for a spine, so you can continue to clutter your shelves with these shiny objects, and when you want to read, select your title by looking at spines, pull one out and sit down and read in your cozy chair just as if you were reading an old fashioned print book, sans Kindle, sans iPad, sans anything that remotely feels like a “device.”

So the Holdout Theory posits that, since publishers and hardware manufacturers both have enough vested interest in distribution methods they already understand, rather than ones they can’t seem to figure out, that creating a future like this is a matter of deliberately holding back the evolution of the ethereal, un-landlocked, “bird book” in favor of one that ships and sits on retail shelves and feels like an object and not an intangible bunch of data.

I have to admit, it’s not too bleak a picture, to imagine that one day we will have both the iTunes or the Netflix of digital books as well as an option to buy something very object-like, even if it’s just a package with a machine inside. After all, it’s working pretty well for software manufacturers.

Those who follow the tech world probably spent yesterday afternoon anticipating the big announcement at Twitter, which turned out to be a few new features, slightly different UI, and a bunch of improvements on the back end that no one can really see.

Ninety million tweets a day is nothing to cough at, but it’s no surprise we’re seeing major feature-convergence between Twitter and Facebook. The one thing in common seems to be the experience of sharing and talking about media. From links to videos to pictures, anything and everything we come across online can now have a near real-time stream of global conversation associated with it. Except books.

Twitter got on this trend by adding a pane on the right hand side of the tweet stream where embedded media can be viewed without ever leaving the site or missing new posts to the stream itself. The only thing missing, which most tech people probably don’t notice or care about, is books. You can see excerpts from articles and web pages, or watch videos pulled in from YouTube, or see shared images, but it seems odd that one of our most interesting, vibrant and compelling forms of media is missing. Why can’t we embed an excerpt from a book in our tweets, and have it display in the right hand pane for our associates to comment on? What do we blame for this omission? Lack of user demand? DRM? Formats? Lack of available content?

It’s not true that book content is lacking online. Amazon’s Look Inside preview, Google Books, Feedbooks, the list of sites with full and partial books available in browsers goes on. And plenty of small technology companies (like us) are making books fully integrated with the Web, giving each paragraph its own URL. Smart people have built software that unpacks and renders Epub files right in the browser. Epub itself is an encapsulation of Web technology. So why should books lag so pitifully far behind other forms of media, to the point that they’re completely ignored by one of the most important communication tools we’ve invented in recent years?

People may not know that they want book content to be seamlessly integrated with the rest of the Web, but once it’s there, they’ll see a new dimension to what the Web actually can be, and they’ll never want it to go away. The permanence of books is something entirely fresh among the billions of temporary URLs meant to last only a short time. How useful it would be to allow them to start accruing social capital in the form of Twitter and Facebook discussions, the way we’re already doing with other forms of media! That kind of data, built up over time, will stay relevant much longer than the latest Tweet stream about the latest YouTube meme.

The answer seems to require an entire book to explain. My gut feeling, after having struggled through discussions with publishers, is that not enough important authors, agents, and publishers want to see this happen. They see no value in it, and are simply afraid of the consequences. Publishing is an old and powerful empire in decline, and stupidity reigns supreme among the top decision makers. Couple that with a willful ignorance and contempt of Web technology, and you have a deliberate sabotage of an almost perfect container for human thought, while in the meantime other media and technology advance in step to further the irrelevance of our beloved Book.

It’s quite possible that we’ll see, over the next fifty years, a strain of thinking we could call “Web thought” overtake what might be called “Book thought,” eventually eliminating it completely. The idea that any work created by an individual needs to be monumental and self-contained is already under attack, and generations to come might consider it a fairly primitive concept worth ignoring in the name of progress. Some people, especially among Web-savvy communities, already think this way.

Someday the majority of authors might simply consider themselves “Web authors” who don’t want to be contained and aren’t concerned with the permanence of their own work as much as they are concerned about making a lasting contribution to the hive. As an aspiring author myself who has completed many short stories, two novels, and other works I consider things that stand on their own, attributable only to me, and as a reader who appreciates great writing that also stands on its own, I don’t want to see this happen, and I think I speak for a lot of people on that point. But as a technically savvy person, a programmer and web designer, I see it happening already. And I see it manifested in the rapid advance of companies like Facebook and Twitter. Ultimately, I think the responsibility falls into the hands of the users of these services: if they don’t see books as a potentially vital and important part of the Web, the Web will replace them with something else. And if publishers continue to assert that books can remain relevant while disconnected from the rest of the flow of human thought, discourse and experience, then they too will be replaced.

To download the Web and put it into an e-book file, you’d need to download some 550 billion documents. You’d need authorization for all of those, since only 25 billion or so are publicly indexed. You’d need at least a 100,000-terabytes of RAM and a specialized meta-search engine that would act as both a table of contents and index.

You’d need a reading system that could support many different content types, beyond even what a standard browser supports. Some kind of e-book operating system would be in order, something that combined all the capabilities of Unix, Windows and Mac OS X into a web browser interface.

And you’d need bandwidth. Anything that took slower than a week to download all 91,000 terabytes would be too slow. Everything would have radically changed by then, and you’d have to re-download it.

Until we get the technology to do that, it’s safe to say that the Web is not an e-book. It’s something different than a book altogether. But I think it’s also safe to say that books are still excellent vehicles for the kind of things we find on the web. Just as a photograph is a record of a moment in time, full of information that probably changed and shifted the split second after it was taken, a book is a container that creates permanent value from impermanent data.

It’s nice to think of the Web as an entity that strengthens its connections over time, builds permanence within its constantly changing layers, takes its own photographs. But the nature of interdependence and constantly shifting connections makes it a poor medium to capture itself.

This is why books, even as they become more dependent on the Web, will benefit from their encapsulation and fixity. Books could become the perfect snapshots of the Web.

A browser’s cache, something like a book, ends up storing a variety of documents that, in total, represent pathways of interest for a particular user: tours of individual sensibility through a vast maze. A digital book platform could be likewise be an editor’s tool for downloading, storing and collecting the Web. An entirely new publishing industry could spring up from culled and curated content bound together into digital editions, each connected to each other, reflective of the Web and connected to it when possible, but not fatally part of it. It would be a web of books capturing the temporal flashes most deserving of permanence.

Perhaps such an ecosystem will become the best alternative to downloading everything. Who will build a tool to make it happen?

There’s a new service out there that allows anyone to send in their paper books, whole boxes of them, and get them fully digitized and OCRed, where they can then be accessed in a personal archive in a multitude of digital formats.

Doesn’t this sound great? I’ve got these old Bantam Classic paperbacks–pages yellowed, glue desiccated–and I’d love to send those in and have them forever as files in the cloud, transferrable to any device I want. There’s something inviting about shipping out all that silverfish food and a week later seeing it pop up in the cloud.

The only problem is that this service is not for consumers, it’s for publishers. And it’s not likely that Google will offer it to us, ever. The likely outcome will be that eventually every mouldering tome in our decrepit paper collections will already have been scanned and available — and we’ll have to pay for it again to get it that way. We’ll still have all this decaying paper and not know exactly what to do with it.

If there was any sense in the publishing industry at all, there would be some big publisher or distributor who marketed permanent backups of your paper in the cloud. With all the rights, plates, and digital masters, there would be no laborious unbinding and scanning to cut into profits. And surely there are enough people feeding a $50B sector to ensure a pretty large number of lifetime subscribers. This would be a new, renewable source of revenue for thirsty giants. And unlike the pulping of newly minted titles, this would be some kind of sweet vengeance on the first sale doctrine, as used copies were destroyed and taken off secondhand markets forever.

But the problem with that scenario is that big publishing, when it comes to digital distribution, tries to force the print process and model on it, over and over.

Which is why they’re like the kid on the playground who loses a fight slowly, getting up every time and blindly trying the same moves that got him knocked down. This is despite the fact that they’re outnumbered: Google is punching them in the face while Amazon holds them and Apple gives them a wedgie, and still they don’t seem to learn. How much more milk money will be lost? How much longer do we have watch this happen?