Tag Archives: Google Reader

Bean Counters and Ecologists

[So many things in my drafts, but this one should be quick.]

Recently met someone who started describing their restaurant after calling it a “café”. The “pitch” revolved around ethical practices, using local products, etc. As both a coffee geek and ethnographer, my simple question was: “Which coffee do you use?” Turns out, they’re importing coffee from a multinational corporation. “Oh, but, they’re lending us an expensive espresso machine for free! And they have fair-trade coffee!”

Luckily, we didn’t start talking about “fair trade”. And this person was willing to reflect upon the practices involved, including about the analogy with Anheuser-Busch or Coca-Cola. We didn’t get further into the deeper consequences of the resto’s actions, but the “seed” has been planted.

Sure, it’s important to focus on your financials and there’s nothing preventing a business from being both socially responsible and profitable. It just requires a shift in mindset. Small, lean, nimble businesses are more likely to do it than big, multinational corporate empires…

…which leads me to Google.

Over the years since its IPO, Google has attracted its share of praise and criticism. Like any big, multinational corporate empire. In any sector.

Within the tech sector, the Goog‘ is often compared with Microsoft, Facebook, Twitter, and Apple. All of these corporate entities have been associated in some people’s minds with some specific issue, from child labour and failure to protect users’ privacy to anticompetitive practices (the tech equivalent of free fridges and espresso machines). The issues are distinct and tech enthusiast spend a large amount of time discussing which one is worse. Meanwhile, we’re forgetting a number of larger issues.

Twitter is an interesting example, here. The service took its value from being at the centre of an ecosystem. As with any ecosystem, numerous interactions among many different members produce unexpected and often remarkable results. As the story goes, elements like hashtags and “@-replies” were invented by users and became an important part of the system. Third-party developers were instrumental in Twitter’s reach outside of its original confines. Though most of the original actors have since left the company, the ecosystem has maintained itself over the years.

When Twitter started changing the rules concerning its API, it shook the ecosystem. Sure, the ecosystem will maintain itself, in the end. But it’s nearly impossible to predict how it will change. For people at Twitter, it must have been obvious that the first changes was a warning shot to scare away those they didn’t want in their ecosystem. But, to this day, there are people who depend on Twitter, one way or another.

Google Reader offers an interesting case. The decision to kill it might have been myopic and its death might have a domino effect.

The warning shot was ambiguous, but the “writing was on the wall”. Among potential consequences of the move, the death of RSS readers was to be expected. One might also expect users of feedreaders to be displeased. In the end, the ecosystem will maintain itself.

Chances are, feedreading will be even more marginalized than it’s been and something else might replace it. Already, many people have been switching from feedreading to using Twitter as a way to gather news items.

What’s not so well-understood is the set of indirect consequences, further down the line. Again, domino effect. Some dominoes are falling in the direction of news outlets which have been slow to adapt to the ways people create and “consume” news items. Though their ad-driven models may sound similar to Google’s, and though feedreading might not be a significant source of direct revenue, the death of feedreaders may give way to the birth of new models for news production and “consumption” which might destabilize them even further. Among the things I tag as #FoJ (“Future of Journalism”) are several pieces of a big puzzle which seems misunderstood by news organizations.

There are other big dominoes which might fall from the death of Google Reader. Partly because RSS itself is part of a whole ecosystem. Dave Winer and Aaron Swartz have been major actors in the technical specifications of RSS. But Chris Lydon and people building on calendar syndication are also part of the ecosystem. In business-speak, you might call them “stakeholders”. But thinking about the ecosystem itself leads to a deeper set of thoughts, beyond the individuals involved. In the aftermath of Aaron Swartz’s premature death, it may be appropriate to point out that the ecosystem is more than the sum of its parts.

As I said on a service owned by another widely-criticized corporate empire:

Many of us keep saying that Google needs to listen to its social scientists. It also needs to understand ecology.

Sharing Tool Wishlist

The following is an edited version of a wishlist I had been keeping on the side. The main idea is to define what would be, in my mind, the “ultimate social bookmarking system.” Which, obviously, goes way beyond social bookmarking. In a way, I even conceive of it as the ultimate tool for sharing online content. Yes, it’s that ambitious. Will it ever exist? Probably not. Should it exist? I personally think so. But I may be alone in this. Surely, you’ll tell me that I am indeed alone, which is fine. As long as you share your own wishlist items.

The trigger for my posting this is that someone contacted me, asking for what I’d like in a social bookmarking system. I find this person’s move quite remarkable, as a thoughtful strategy. Not only because this person contacted me directly (almost flattering), but because such a request reveals an approach to listening and responding to people’s needs that I find lacking in some software development circles.

This person’s message served as a prompt for my blogging this, but I’ve been meaning to blog this for a while. In fact, my guess is that I created a first version of this wishlist in 2007 after having it on my mind for a while before that. As such, it represents a type of “diachronic” or “longitudinal” view of social bookmarking and the way it works in the broader scheme of social media.

Which also means that I wrote this before I heard about Google Wave. In fact, I’m still unclear about Google Wave and I’ll need to blog about that. Not that I expect Wave to fulfill all the needs I set up for a sharing tool, but I get the impression that Google is finally putting some cards on the table.

The main part of this post is in outline form. I often think through outlines, especially with such a type of notes. I fully realize that it may not be that clear, as a structure, for other people to understand. Some of these bullet points cover a much broader issue than what they look like. But the overall idea might be fairly obvious to grasp, even if it may sound crazy to other people.

I’m posting this to the benefit of anyone who may wish to build the killer app for social media. Of course, it’s just one man’s opinion. But it’s my entitled opinion.


What do we share online?

  • “Link”
  • “Page”
  • Identified content
  • Text
    • Narrative
    • Contact information
    • Event description
  • Contact information
  • Event invitation
  • Image
  • Recording
  • Structured content
  • Snippet
  • Access to semi-private content
  • Site’s entry point

Selective sharing

  • Archiving
  • Cloud access
Individually shared
  • “Check this out”
  • Access to address book
  • Password protection
  • Specialization/expertise
  • Friendship
Group shared
  • Shared interests (SIG)
  • Collaboration (task-based)
Shared through network
  • Define identity in network
  • Semi-public
  • Publishing
  • Processed
  • Reading lists


  • Active reading
  • Anchoring text
  • Ad hoc list of bookmarks
  • “Empty URL”
    • Create container/page
    • Personal notes


  • To read
  • To blog
  • To share
  • To update
  • Projects
    • GTD
    • Contexts
  • Add to calendar (recognized as event)


  • Manage lists of links
  • Prioritize
  • Easily group

Social aspects of sharing

  • Gift economy
  • Personal interaction
  • Trust
  • Hype
  • Value
  • Customized

Cloud computing

  • Webware
  • “Online disk”
  • Without download
  • Touch devices
  • Edit online

Personal streaming

  • Activities through pages
  • Logging
  • Flesh out personal profile


  • “Folksonomy”
  • Enables non-hierarchical structure
  • Semantic fields
  • Related tags
  • Can include hierarchy
  • Tagclouds define concept map

Required Features

Crossplatform, crossbrowser

  • Browser-specific tools
  • Bookmarklets
  • Complete access through cloud
Keyboard shortcuts
  • Quick add (to account)
  • Vote
  • Bookmark all tabs (à la Flock)
  • Quick tags

Related pages

  • Based on social graph
  • Based on tags
  • Based on content
  • Based on popularity
  • Pointing to this page

Quickly enter links

  • Add in place (while editing)
  • Similar to “spell as you type”
  • Incremental search
  • Add full link (title, URL, text, metadata)


  • Prevent linkrot
  • Prepare for post-processing (offline reading, blogging…)
  • Enable bulk processing
  • Maintain version history
  • Internet Archive

Automatic processing

  • Tags
  • Summary
  • Wordcount
  • Reading time
  • Language(s)
  • Page structure analysis
  • Geotagging
  • Vote

Thread following

  • Blog comments
  • Forum comments
  • Trackbacks
  • Pings


  • Archiving
  • Prepare for import
  • Maintain hierarchy
  • Tag
  • Category
  • Recently used
  • Shared
  • Site homepage
  • Blogroll
  • Blogs
  • Other services
  • HTML
  • RSS
  • OPML
  • Widget
  • Comments
  • Tags
  • Statistics
  • Content

Offline processing

  • Browser-based
  • Device based
  • Offline archiving
  • Include content
  • Synchronization

Microblogging support

  • Laconi.ca/Identi.ca
  • Twitter
  • Ping.fm
  • Jaiku

Fixed/Static URL

  • Prevent linkrot
  • Maintain list for same page
  • Short URLs
  • Automatically generated
  • Expansion on mouseover
  • Statistics


  • Use of resources
  • Identify
  • Privacy
  • Unnecessary for basic processing
  • Sticks (no need to login frequently)
  • Access to contacts and social graph
  • Multiple accounts
    • Personal/professional
    • Contexts
    • Group accounts
  • Premium accounts
    • Server space
    • Usage statistics
    • Promotion
  • Support
    • OpenID
      • As group login
    • Google Accounts
    • Facebook Connect
    • OAuth


  • Web history
  • Notebook
  • Blogging platform
  • Blog editor
  • Microblogging platform
  • Logbook
  • General purpose content editor
  • Toolbar
  • URL shortening
  • Address book
  • Social graph
  • Personal profile
  • Browser
    • Bookmarks
    • History
    • Autocomplete
  • Analytics
  • Email
  • Search
    • Online
    • Offline

Related Tools

  • Diigo
  • WebCitation
  • Ping.fm
  • BackType
  • Facebook share
  • Blog This
  • Link This
  • Share this
  • Digg
  • Plum
  • Spurl
  • CoComments
  • MyBlogLog
  • TwtVite
  • Twistory
  • Windows Live Writer
  • Magnolia
  • Stumble Upon
  • Delicious
  • Google Reader
  • Yahoo Pipes
  • Google Notebook
  • Zoho Notebook
  • Google Browser Sync
  • YouTube
  • Flock
  • Zotero

Relevant Blogposts

Google for Educational Contexts

Interesting wishlist, over at tbarrett’s classroom ICT blog.

11 Google Apps Improvements for the Classroom | ICT in my Classroom.

In a way, Google is in a unique position in terms of creating the optimal set of classroom tools. And Google teams have an interest in educational projects (as made clear by Google for Educators, Google Summer of Code, Google Apps for schools…).
What seems to be missing is integration. Maybe Google is taking its time before integrating all of its services and apps. After all, the integration of Google Notebook and Google Bookmarks was fairly recent (and we can easily imagine a further integration with Google Reader). But some of us are a bit impatient. Or too enthusiastic about tools.

Because I just skimmed through the Google Chrome comicbook, I get to think that, maybe, Google is getting ready to integrate its tools in a neat way. Not specifically meant for schools but, in the end, an integrated Google platform can be developed into an education-specific set of applications.
After all, apart from Google Scholar, we’re talking about pretty much the same tools as those used outside of educational contexts.

What tools am I personally thinking about? Almost everything Google does or has done could be useful in educational contexts. From Google Apps (which includes Google Docs, Gmail, Google Sites, GTalk, Gcal…) to Google Books and Google Scholar or even Google Earth, Google Translate, and Google Maps. Not to mention OpenSocial, YouTube, Android, Blogger, Sketchup, Lively

Not that Google’s versions of all of these tools and services are inherently more appropriate for education than those developed outside of Google. But it’s clear that Google has an edge in terms of its technology portfolio. Can’t we just imagine a new kind of Learning Management System leveraging all the neat Google technologies and using a social networking model?

Educational contexts do have some specific requirements. Despite Google’s love affair with “openness,” schools typically require protection for different types of data. Some would also say that Google’s usual advertisement-supported model may be inappropriate for learning environments. So it might be a sign that Google does understand school-focused requirements that Google Apps are ad-free for students, faculty, and staff.

Ok, I’m thinking out loud. But isn’t this what wishlists are about?

How Can Google Beat Facebook?

It might not be so hard:

As I see it, the biggest shortcoming of social-networking sites is their inability to play well with others. Between MySpace, Facebook, LinkedIn, Tribe, Pownce, and the numerous also-rans, it seems as if maintaining an active presence at all of these sites could erode into becoming a full-time job. If Google can somehow create a means for all of these services to work together, and seamlessly interact with the Google family, then perhaps this is the killer app that people don’t even realize they’ve been waiting for. Google gives social networking another go | Media Sphere – Josh Wolf blogs about the new information age – CNET Blogs

Some might take issue at Wolf’s presumption. Many of us have realised in 1997 that the “killer app” for social networking services is for them to work together. But the point is incredibly important and needs to be made again and again.

Social Networking Services work when people connect through it. The most intricate “network effect” you can think of. For connections to work, existing social relationships and potential social relationships need to be represented in the SNS as easily as possible. What’s more, investing effort and time in building one’s network relates quite directly with the prospective life of SNS. Faced with the eventuality of losing all connections in a snap because everybody has gone to “the next thing,” the typical SNS user is wary. Given the impression that SNS links can survive the jump to “the next one” (say, via a simple “import” function), the typical SNS user is likely to use the SNS to its fullest potential. This is probably one of several reasons for the success of Facebook. And Google can certainly put something together which benefits from this principle.

Yeah, yeah, Wolf  was referring more specifically to the “synchronisation” of activities on different SNS or SNS-like systems. That’s an important aspect of the overall “SNS interoperability” issue. Especially if SNS are important parts of people’s lives. But I prefer to think about the whole picture.

Another thing which has been mentioned is the connection Google could make between SNS and its other tools. One approach would be to build more “social networking features” (beyond sharing) into its existing services. The other could be to integrate Google tools into SNS (say, top-notch Facebook applications). Taken together, these two approaches would greatly benefit both Google and the field of social networking in general.

All in all, what I could easily see would be a way for me to bring all my SNS “content” to a Google SNS, including existing links. From a Google SNS, I would be able to use different “social-enabled” tools from Google like the new Gmail, an improved version of Google Documents, and the Blogger blogging platform. Eventually, most of my online activities would be facilitated by Google but I would still be able to use non-Google tools as I wish.

There’s a few tools I’m already thinking about, which could make sense in this “Google-enabled social platform.” For one, the “ultimate social bookmarking tool” for which I’ve been building feature wishlists. Then, there’s the obvious need for diverse applications which can use a centralised online storage system. Or the browser integration possible with something like, I don’t know, the Google toolbar… 😉

Given my interest in educational technology, I can’t help but think about online systems for course management (like Moodle and Sakai). Probably too specific, but Google could do a wonderful job at it.

Many people are certainly thinking about advertisement, revenue-sharing, p2p for media files, and other Google-friendly concepts. These aren’t that important for me.

I can’t say that I have a very clear image of what Google’s involvement in the “social networking sphere” will look like. But I can easily start listing Google products and features which are desperately calling for integration in a social context: Scholar, Web History, Docs, Reader, Browser Sync, Gcal, Gmail, Notebook, News, Mobile, YouTube, Ride Finder, Blog Comments, Music Trends, University Search, MeasureMap, Groups, Alerts, Bookmarks…

Sometimes, I really wonder why a company like Google can’t “get its act together” in making everything it does fit in a simple platform. They have the experts, the money, the users. They just need to make it happen.

Ah, well…