Active Facebook Users By Country

Since I last posted numbers on Facebook's user base six week ago, the company has added close to 20 million active users.

I've had a few requests for detailed numbers by country so I quickly assembled an update for each of the regions shown above.

(continue reading)

Why Aneesh Chopra is a Great Choice for Federal CTO

The news has now been leaked that President Obama intends to nominate Aneesh Chopra as the nation's first Chief Technology Officer. The Federal CTO will be an assistant to the President, as well as the Associate Director of the White House Office of Science and Technology Policy. He will work closely with Vivek Kundra, the recently-named Federal CIO, to develop and implement the President's ambitious technology agenda.

According to one background document I was given access to, the White House describes the relationship between the CIO and CTO roles as follows:

The responsibilities of the CIO are to use information technology to transform the ways in which the government does business. The CTO will develop national strategies for using advanced technologies to transform our economy and our society, such as fostering private sector innovation, reducing administrative costs and medical errors using health IT, and using technology to change the way teachers teach and students learn.

Some in Silicon Valley have hoped for one of their own, a CTO with a deep technology pedigree and ties to the technology industry. For example, the Techcrunch coverage leads with the title Obama Spurns Silicon Valley. This is a narrow view.

I've been working for much of the past year to understand what many have been calling Government 2.0, and in that process, Chopra has been one of those who have taught me the most about how we can build a better government with the help of technology. He is an excellent choice as Federal CTO, for many reasons:

1. Chopra has been focused for the past three years on the specific technology challenges of government. Industry experience does little to prepare you for the additional complexities of working within the bounds of government policy, competing constituencies, budgets that often contain legislative mandates, regulations that may no longer be relevant but are still in force, and many other unique constraints. In his three year tenure as Secretary for Technology for the Commonwealth of Virginia, Chopra has demonstrated that he has these skills. In fact, last year, the National Association of State Chief Information Officers ranked Virginia #1 in technology management.

2. The role of the CTO is to provide visionary leadership, to help a company (or in this case, a government) explore the transformative potential of new technology. Try a few of these Virginia technology initiatives on for size:
   • the first officially-approved open source textbook in the country, the Physics Flexbook.
   • integrating iTunes U with Virginia's state education assessment framework;
   • the Learning Apps Development Challenge, a competition for the best iPhone and iPod Touch applications for middle-school math teaching;
   • a Ning-based social network to connect clinicians working in small health care offices in remote locations;
   • a state-funded "venture capital fund" to allow government agencies to try out risky but promising new approaches to delivering their services or improving their productivity;
   • a lightweight approval and testing process that allows the government to try out new technologies before making a full, expensive commitment.

3. Chopra demonstrates a deep understanding of the idea that the government is an enabler, not the ultimate solution provider. From the list of initiatives above, you can see that Chopra grasps the power of open source software, Web 2.0, user-participation, and why it's better to harness the ingenuity of a developer community than to specify complete top-down solutions. In a conversation with me a couple of months ago, he expressed his enthusiasm for the idea of a "digital commonwealth," a recognition that technology can help us to come together as a society to solve problems and create value through common effort. (See my post yesterday, The Change We Need: DIY on a Civic Scale.)

   This digital commonwealth approach can be seen in Virginia's approach to rural broadband. The Virginia Information Technology Agency has developed a "broadband toolkit" that fosters cooperation between public agencies and private companies, identifying the location of public sector radio towers that can be used for free by broadband providers in order to reduce their costs, and areas with zoning rules that allow for public sector use of private radio towers.

   The digital commonwealth reflects an understanding of the dynamics that have led to technology successes like Google Maps, Facebook, Twitter, and the iPhone app store: the platform provider creates enabling technology, "rules of the road," and visibility for participants, and then gets out of the way, leaving room for third parties to create additional value. This is a great model for all future government technology efforts.

4. Chopra understands that government technologists need to act more like their counterparts in Silicon Valley. As Micah Sifry notes in the TechPresident blog, quoting from a Governing magazine article about the Virginia venture capital experiment:

   "More important, and more unusual for the bureaucrats," says Governing, "he gives them permission to fail. You can't innovate, Chopra tells them, without taking a gamble every now and then." He adds, "We need to fundamentally change the culture of government in which change is measured in budget cycles to one in which change is measured in weeks or months."

5. Chopra is a practical innovator. He's not chasing technology for its own sake. I like this quote from a recent Federal Computer Week story:

   Understanding the process or service is always the most important factor, with technology running second. “Service sector innovation is the most important question,” Chopra said. “I’m not as excited about whether or not it’s emerging technology.”

   In my own conversations with Chopra over the past few months, this focus on "service sector innovation" has seemed particularly fertile. Our economy increasingly consists of service jobs. Improving the effectiveness of those jobs is one of the great challenges of the 21st century. Chopra wants to put technology to work to make us better at health care, at education, at creating a vibrant economy. These are also, incidentally, the goals of the Federal CTO job, as described in one briefing document I reviewed:

   One of the primary responsibilities of the CTO will be to leverage American ingenuity generally and new technologies in particular as engines for job creation and economic growth. The CTO’s priorities will include expanded use of technology to boost broadband access, reduce health care costs, enable novel job-producing industries, remove barriers to technological progress, and create a more transparent and interactive government.

6. Chopra has a real focus on measurement, and on figuring out what really works. For example, the social network for remote health care workers mentioned above was the result of data showing an unusually high turnover rate for these workers. As I once wrote, in If Google Were a Restaurant,

   Web 2.0 (or "Live Software", as Microsoft has so insightfully called it) depends on creating information feedback loops. This is the practical plumbing that makes possible Web 2.0 systems that get better the more people use them.

   If we are truly to remake America's economy with the aid of technology, as the Obama administration has promised, we need to embrace the culture of transparency and feedback. The Federal transparency initiative is a central part of the plan. While there's a long way to go, the stimulus.gov initiative, to report on the progress of Federal stimulus spending, is a critical step in building the electronic nervous system that will help us to understand what we're spending, where it's going, and what we're getting for all that money. Under Chopra's leadership, Virginia has been in the forefront of driving stimulus transparency down to the state level. stimulus.virginia.gov was one of the first state-level stimulus sites, and has served as a model for other states.

7. Chopra has specific expertise in Health Care IT. This is one of the most critical areas where we need to see technology innovation in the coming years. Unless we can get Moore's Law working in health care, it will eventually bankrupt our already-tottering economy. $19 billion has been allocated to Health Care IT in the stimulus package. We need someone who can help us spend it wisely!

8. Chopra is incredibly charismatic. This is essential in a role that depends on persuasion rather than outright authority. As Sean Garrett said in an excellent post on the 463 blog:

   I highly recommend watching a good portion of the video below. It's from this year's Congressional Internet Caucus conference in September.

   Chopra may not be a Valley guy, but Silicon Valley is going to like him a lot. He's energetic, insightful and can speak the language (again, watch the video). He's no bureaucrat.

   And, just because you didn't previously work for a chip company or an Internet start-up doesn't mean that you "are not a tech guy" as I just read another blog. Chopra spent a bulk of his career seeing technology in action (for better or worse) in his work in the health care industry and knew that it could and should do better to bring change to the massive sector.

   I couldn't agree more. Aneesh Chopra is a rock star. He's a brilliant, thoughtful change-maker. He knows technology, he knows government, and he knows how to put the two together to solve real problems. We couldn't do better.

Four Short Links: 17 Apr 2009

Twitter (not THAT story, though), semantics, gardening, and netbook supercomputers:

1. Retweet Radar -- the phrases showing up in heavily retweeted posts. This is another feature that should be incorporated into desktop clients. Three of the top 10 terms as retweeted by the General Public are "Ashton", "CNN", "followers"; if I wanted to read this drivel, I'd buy US Magazine. The point of software with a social network is to let me swerve the extreme blandness of mass culture that makes me want to poke sporks into my eyes just to have something I cared about. (via zephoria's delicious stream)
2. I Am Machine Tag and So Can You -- This post explains how you can use machine tags with your next web app or even your blog. With Machinetag, a jQuery plugin, you’ll be able to search and display machine tagged content as trees faster than Colbert can crack a quip. Well … maybe not that fast. Machine tags are Namespace:Predicate=Value tags that provide semantic information in a machine-readable fashion, they're part of the rapid semantic weight-gain program that geeks have put the Web on. (via foe's delicious stream)
3. Robots Feed and Water Tomatoes (NZ Herald) -- self-service Botanicalls on wheels.
4. FAWN -- Fast Array of Weak Nodes, a cluster built from low-power netbook CPUs. Using a cluster of the same processors that normally show up in netbooks and similar mobile devices, researchers have created a powerful server architecture that draws less power than a lightbulb. (via Roger Dennis)

The Change We Need: DIY on a Civic Scale

I've been working a lot lately to imagine what Government 2.0 might look like. One of the most inspiring and thought-provoking stories I've read recently might not look like a Gov 2.0 story, but it is: Island DIY: Kauai residents don't wait for state to repair road.

Their livelihood was being threatened, and they were tired of waiting for government help, so business owners and residents on Hawaii's Kauai island pulled together and completed a $4 million repair job to a state park -- for free.

In fact, governments, like corporations, are vehicles for collective action. We pay a government, or a business, because it's an efficient way to tackle projects that are larger than a single person or group of friends can take on. But let's not forget that we ourselves are the raw material of collective action.

Traditional communities still remember how to do a barn raising. Those of us who spend our time on the internet celebrate wikipedia, but most of us have forgotten how to do crowdsourcing in the physical world.

The internet provides new vehicles for collective action. A lot of people pay attention when social media is used to organize a protest (as with the recent twitter-fueled protests in Moldova.) But we need to remember that we can organize to do work, as well as to protest!

Especially striking in the story are the cost and time-savings:

"It would not have been open this summer, and it probably wouldn't be open next summer," said Bruce Pleas, a local surfer who helped organize the volunteers. "They said it would probably take two years. And with the way they are cutting funds, we felt like they'd never get the money to fix it."

And if the repairs weren't made, some business owners faced the possibility of having to shut down....

So Slack [owner of a kayak tour business in the park], other business owners and residents made the decision not to sit on their hands and wait for state money that many expected would never come. Instead, they pulled together machinery and manpower and hit the ground running March 23.

And after only eight days, all of the repairs were done, Pleas said. It was a shockingly quick fix to a problem that may have taken much longer if they waited for state money to funnel in....

"We can wait around for the state or federal government to make this move, or we can go out and do our part," Slack said. "Just like everyone's sitting around waiting for a stimulus check, we were waiting for this but decided we couldn't wait anymore."

Now is the time for a renewal of our commitment to make our own institutions, our own communities, and our own difference. There's a kind of passivity even to our activism: we think that all we can do is to protest. Collective action has come to mean collective complaint. Or at most, a collective effort to raise money.

What the rebuilding of the washed out road in Polihale State Park teaches us is that we can do more than that. We can apply the DIY spirit on a civic scale.

Aneesh Chopra, the Secretary for Technology of the Commonwealth of Virginia, recently told me why he liked the term "commonwealth" better than "state": commonwealth emphasizes the value that we create by coming together. Technology provides us with new ways to coordinate, new ways to govern and to regulate, but we should never forget that these are merely means. The end is a better society. And that starts with us.

We need to rediscover government as an enabler, not a solution provider; as a platform for our own innovation, a lever for our own work, not as the deus ex machina that we've paid to do for us what we could be doing for ourselves.

If you know of other great civic DIY stories, let me know. I want to feature technology in my Government 2.0 activism, but I also want to feature the simple DIY spirit.

Legally Speaking: The Dead Souls of the Google Booksearch Settlement

Guest blogger Pamela Samuelson is the Richard M. Sherman Distinguished Professor of Law and Information at the University of California, Berkeley, as well as a Director of the Berkeley Center for Law & Technology and an advisor to the Samuelson High Technology Law & Public Policy Clinic at Boalt Hall. She has written and spoken extensively about the challenges that new information technologies pose for traditional legal regimes, especially for intellectual property law.

This piece will appear in the July 2009 issue of Communications of the ACM. Readers may also be interested in the slides from Pam's recent presentation, "Reflections on the Google Book Search Settlement."

Google has scanned the texts of more than seven million books from major university research libraries for its Book Search initiative and processed the digitized copies to index their contents. Google allows users to download the entirety of these books if they are in the public domain (about 1 million of them are), but at this point makes available only “snippets” of relevant texts when the books are still in copyright unless the copyright owner has agreed to allow more to be displayed.

In the fall of 2005, the Authors Guild, which then had about 8000 members, and five publishers sued Google for copyright infringement. Google argued that its scanning, indexing, and snippet-providing was a fair and non-infringing use because it promoted wider public access to books and because Google would take out of the Book Search corpus any digitized books whose rights holders objected to their inclusion. Many copyright professionals expected the Authors Guild v. Google case to be the most important fair use case of the 21st century.

This column argues that the proposed settlement of this lawsuit is a privately negotiated compulsory license primarily designed to monetize millions of orphan works. It will benefit Google and certain authors and publishers, but it is questionable whether the authors of most books in the corpus (the “dead souls” to which the title refers) would agree that the settling authors and publishers will truly represent their interests when setting terms for access to the Book Search corpus.

Orphan Works

An estimated 70 per cent of the books in the Book Search repository are in-copyright, but out of print. Most of them are, for all practical purposes, “orphan works,” that is, works for which it is virtually impossible to locate the appropriate rights holders to ask for permission to digitize them.

A broad consensus exists about the desirability of making orphan works more widely available. Yet, without a safe harbor against possible infringement lawsuits, digitization projects pose significant copyright risks. Congress is considering legislation to lessen the risks of using orphan works, but it has yet to pass.

The proposed Book Search settlement agreement will solve the orphan works problem for books—at least for Google. Under this agreement, which must be approved by a federal court judge to become final, Google would get, among other things, a license to display up to 20 per cent of the contents of in-copyright out-of-print books, to run ads alongside these displays, and to sell access to the full texts of these books to institutional subscribers and to individual purchasers.

The Book Rights Registry

Approval of this settlement would establish a new collecting society, the Book Rights Registry (BRR), initially funded by Google with $34.5 million. The BRR will be responsible for allocating $45 million in settlement funds that Google is providing to compensate copyright owners for past uses of their books.

More important is Google’s commitment to pay the BRR 63 per cent of the revenues it makes from Book Search that are subject to sharing provisions. The revenue streams will come from ads appearing next to displays of in-copyright books in response to user queries and from individual purchases of and institutional subscriptions to some or all of the books in the corpus. Google and the BRR may also develop new business models over time that will be subject to similar sharing.

One of the main jobs of the BRR will be to distribute the settlement revenues. The money will go, less BRR’s costs, to authors and publishers who have registered their copyright claims with BRR. Although the settlement agreement extends only to books published prior to January 5, 2009, BRR is expected to attract authors and publishers of later-published books to participate in the revenue sharing arrangement that Google has negotiated with BRR.

(continue reading)

A Telling Map of Job Losses

Slate's Moneybox has an interactive map that shows job creation and loss throughout the US for the past two years. Watching it flow through each month's up and down definitely made the employment situation in the country clearer to me. Like any great visualization image and the legend make it very clear what's happening. Here's Slate's explanation of how they created this:

Using the Labor Department's local area unemployment statistics, Slate presents the recession as told by unemployment numbers for each county in America. Because the data are not seasonally adjusted for natural employment cycles throughout the year, the numbers you see show the change in the number of people employed compared with the same month in the previous year. Blue dots represent a net increase in jobs, while red dots indicate a decrease. The larger the dot, the greater the number of jobs gained or lost.

The country begins a awash with blue (job growth) in January 2006:

By February 2009 job loss looks like:

Slate is using readily available public data, but presenting it in a much more digestible form than what you see in this table of similar data from the Labor Department:

The table is good for diving in to see a specific data point, but the map draws us out and shows us a larger story in motion. I hope that story goes back to blue soon.

At Where 2.0 in May we will hear from a number of speakers who create these types of maps. Matthew Ericson of the New York Times will discuss the maps they used in their election coverage and Michal Migurski of Stamen Design will be explore data sources for maps. Registration is still open; you can use whr09rdr for 25% off.

Four short links: 16 Apr 2009

China, databases, storage, and git:

1. China's Complicated Internet Culture (Ethan Zuckerman) -- summary of Rebecca McKinnon's talk at the Berkman Internet Center. Democracy is complex and hard to transition to, online democracy doubly so. Rebecca questions the widespread but unjustified belief that the Great Firewall of China is all that separates Chinese citizens from the empowered liberty of the West, and lays out the tangled state of affairs in China's political Internet. Despite the rise of web video, “no one has managed to organized an opposition party on the web,” Rebecca points out. “There’s no Lech Walenza, no religious movement - Falun Gong has been squished pretty thoroughly.” (via cshirky's delicious stream)
2. Drop ACID and Think About Data -- Bob Ippolito's talk from PyCon about the things you can do easily when you foresake the promises of ACID. More in the ongoing reinvention of databases for the needs of modern web systems. (via cesther's Twitter stream)
3. The Pogoplug -- The Pogoplug connects your external hard drive to the Internet so you can easily share and access your files from anywhere. We're accumulating terabytes of storage at home, where it's very useful to all the computers in the home. This offers an easy way for non-technical civilians to make these drives useful outside the home as well. There are many possibilities for Interesting Things in the massive storage we're accumulating. (via joshua's delicious stream)
4. Gitorious -- open source (AGPLv3) clone of github. (via edd's delicious stream)

Waiting for the Billionth Download

Over the next week, the iTunes App Store is set to record its billionth download, an impressive milestone given that it launched less than a year ago. Granted the actual usage of most apps is spotty. To mark the event, I'm updating a few charts that I produced for previous posts.

Slightly over 35,000 apps have appeared in the U.S. app store. Over 31,000 were available in the last week alone, about 78% of which were PAID apps:

(continue reading)

Where 2.0 Preview - Building the SENSEable City

Much of the information we have about how cities work (or don't) comes through direct, intentional observation and study--but could we learn as much or more by mining the data that citizens generate in their day-to-day lives, through cell phone traffic and internet usage? That's one of the questions that Andrea Vaccari, a research associate at the MIT SENSEable City Lab, is trying to answer. Andrea will be speaking on the research that the SENSEable City Project is doing at the O'Reilly Where 2.0 Conference in May.

James Turner: So why don't you start a little bit by talking about what the charter of the SENSEable City Lab is?

Andrea Vaccari: Sure. The SENSEable City Lab is a recent initiative; a new initiative of the Massachusetts Institute of Technology which focuses on studying how digital technologies are evolutionizing the way we live in cities. And, therefore, how we can leverage these technologies; how we can make use of it through understanding how cities are using it; how we can design better cities. And then we can create cities that are more sustainable, more livable and automatically more efficient.

JT: A lot of data that governments gather about cities -- the example I think of is the little things they put across the roads to find out traffic going over a road, but that's almost like just a point source data. Can you compare that to the kind of data that you're able to extract through the records you can get access to?

AV: Sure. The problem with past data in all aspects of the urban planning and social studies is that the data is usually punctual, so it refers to very specific points in space and also in time. And that's because the methods that were used to gather this information were very expensive. They required either to deploy infrastructures or to employ people to count manually cars, people, vehicles. And, therefore, it was impossible to have a real-time flow of information. What we are trying to do is to leverage the pervasive systems that enhance our cities today. And I'm referring to telecommunication networks, wireless networks, transportation systems or any other sort of digital system that interacts on a daily basis -- on a real-time basis -- with the citizens. What happens is that with these systems, interactions between the user and the system creates logs of their activity. And these logs can be used to understand the urban dynamics, to understand how people move in living cities and how cities themselves evolve in time.

JT: Now, you showed me some of the examples of the datasets that you've been playing with, and it seems like largely it's cell phone data and wifi data and then secondarily, things that are more voluntary like Flickr uploads.

AV: Yes.

JT: Wifi data you can pretty much get to a hotspot. And as Google has demonstrated with cell phone data, you can get fairly good positioning. But what kind of resolution do you get out of say cell phone data?

AV: Sure. The resolutions that we get for the cell phone is aggregated at the antenna level. So we don't get information about the individuals because we strongly respect privacy. And what we basically know is how many calls, how many text messages, how much traffic is served by each antenna in a city. And, of course, we know the position of the antenna and we can estimate the coverage of these antennas. So we can fairly understand what are the dynamics going on in the area of coverage. But, again, we don't get information about individuals.

(continue reading)

Ignite Show: Monica Guzman on Being an Awesome News Commenter

This week's Ignite Show features Seattle PI reporter Monica Guzman. She's spent most of her career writing for online properties and she's been able to watch learn what makes for a good conversation around a news item. As someone who also spends a lot of time publishing content online I can appreciate Monica's thoughts on good commenters and hearing some of what she deals with makes me very appreciative of our readers and how you add to the conversations on our site.

The Ignite Show is also available on iTunes.

Practical Tips for Government Web Sites (And Everyone Else!) To Improve Their Findability in Search

In an earlier post, I said that key to government opening its data to citizens, being more transparent, and improving the relationship between citizens and government in light of our web 2.0 world was ensuring content on government sites could be easily found in search engines. Architecting sites to be search engine friendly, particularly sites with as much content and legacy code as those the government manages, can be a resource-intensive process that takes careful long-term planning. But

• Assessing who the audience is and what they're searching for
• Ensuring the site architecture is easily crawlable

Use XML Sitemaps
Create XML Sitemaps that list all the pages on the site and submit them to the major search engines.

Why is this important? Many government sites have poor information architecture. Ideally each page of the site should have at least one link to it. This helps users navigate the site and helps search engines find all of the pages. Long term, these sites should revamp their navigational structure so that at least one link exists to every page. Since that may take some time to implement, an XML Sitemap can function in the meantime to provide a list of all pages for search engines to crawl.

Government sites have already made great progress in search by using XML Sitemaps.

The Energy Department's Office of Science and Technology (OSTI) implemented XML Sitemaps protocol with great success. "The first day that Yahoo offered up our material for search, our traffic increased so much that we could not keep up with it,' said Walt Warnick, OSTI's director.

If possible, provide an HTML sitemap as well, which provides a browsable navigation to site visitors. Below is a good example of a browsable HTML sitemap on nih.gov:

Don't block access to content
Make all content available outside of a login, registration form, or other input mechanism. Search engine crawlers can't access content behind a login or registration. If the content requires the visitor to enter an email address or otherwise provide input before accessing it, it won't show up in search results.

(continue reading)

Where 2.0 Preview - Tyler Bell on Yahoo's Open Location Project

Location can be a vague concept to pin down. To a surveyor, location means latitude and longitude accurate to a few millimeters, while to a cab driver, a street address would be much more useful. If you're German, I can tell you that I live in the United States. To a Californian, I live in New Hampshire. And to someone from Manchester, I live in Derry. Unfortunately, the way that location is currently stored and presented online is both non-uniform and frequently at a level of precision inappropriate for the end-user. That's part of what Open Location is trying to fix. Tyler Bell, who took his doctorate from Oxford to Yahoo, is currently the product lead for the Yahoo Geo Technology Group. At O'Reilly's Where 2.0 Conference, he'll be discussing Open Location.

James Turner: So first off, can you describe what the Geo Technologies Group does?

Tyler Bell: The Geo Technologies Group at Yahoo oversees all technologies that relate to geography and geographic information. So it's largely self-evident. But this is what I mean by that: it's really we own and oversee the maps and mapping technologies. So the visualizations and placements of geographically informed data. We also own user location technologies. So here, we're dealing with different methods of detecting user location, managing user location, and ensuring that users receive geo-relevant results whenever they log onto Yahoo or use a Yahoo service. And then lastly, we have something which is slightly more esoteric. It's called the Geoinformatics Group. And that's the organization which uses geography to inform data. And we do this without ever showing a map. So it's really how we add value and power to information wholly based upon where things are and where our users are.

JT: That's like returning relevant search information to what you know about the user's location.

TB: That's correct. That's the end product of search groups consuming the geo technologies services on the back-end. But what we also need to do is actually organize the geographic information. So instead of searches, they're the specialists at Yahoo about matching user intent to the results that are returned; it's our job on the Geoinformatics Group, for example, to say that when a user queries against Springfield or they're searching for Springfield, which of the countless Springfields in the United States, in the world do you mean? So we need to be able to recognize that this is a place. We need to identify all of the places of a particular place name. And then we need to be able to do a so-called geo-geo disambiguation to ensure that when you mean Springfield, when you mean Campbell, when you give us a city name, which is otherwise nonspecific, we are very likely to return the most direct and accurate results.

(continue reading)

Recent Posts

• Four short links: 15 Apr 2009 | by Nat Torkington on April 15, 2009
• Ignite Seattle Line-up | by Brady Forrest on April 14, 2009
• Four short links: 14 Apr 2009 | by Nat Torkington on April 14, 2009
• Four short links: 13 Apr 2009 | by Nat Torkington on April 13, 2009
• Tweenbots: Cute Beats Smart | by Brady Forrest on April 11, 2009
• Four quick posts: 11 April 2009 | by Marc Hedlund on April 11, 2009
• Becoming Location Aware: Where 2.0 Early Registration Ending 4/13 | by Brady Forrest on April 10, 2009
• AT&T; Fiber cuts remind us: Location is a Basket too! | by Jesse Robbins on April 10, 2009
• Where 2.0 Preview - Pelago's Jeff Holden on Creating Stories Out of Your Life | by James Turner on April 9, 2009
• Four short links: 9 Apr 2009 | by Nat Torkington on April 9, 2009
• Four short links: 8 Apr 2009 | by Nat Torkington on April 8, 2009
• PhoneGap, the Mobile Platform Democratizer | by Brady Forrest on April 8, 2009