Wednesday
Jun172009
Google Wave Is Better For The Environment
June 2009
Google Wave is the future of networked communication. Well, maybe. If a lot of people embrace the technology and make it common place. There are lots of barriers though, fear of a new interface, businesses where most people use e-mail like software are slow to change and sheer laziness because e-mail is "good enough". There's lots of talk about the potential of Google Wave Apps and work flow but I had an interesting thought about a very practical side-effect of Google Wave and a great reason to adopt this software. It's good for the environment.
I will be upfront and admit that my math is awful and I'm taking a few liberties with my knowledge of complex systems. Please forgive any mistakes.

E-mail is an old system. It involves sending packets of information from one server to another. From one hard drive to another hard drive. Each person keeps a copy of their mail and the response. If multiple people are copied on an e-mail, like all business correspondence, then each person has a copy of every response on their hard drive. So if 8 people have a 30 mail conversation about an internal project, there are 240 copies of pieces of the conversation on 8 machines or inboxes. In my office, we all "reply with history" so people can keep track of where we were in the conversation. Even one word answers. At 1MB average per mail (history adds up), that's 240MB of replicated data sitting on hard drives. If your company is like mine, 20 exchanges about a project over several months is not unheard of. That's 4.68GB of replicated data on one company's servers. A medium size company might have 100 projects a year like this. That's 468.75GB a year. That's not including video files, images, PPT documents and the other goodies that need sharing. Which is why Google decided to re-look e-mail I suppose.

Google Wave is different to e-mail. At it's simplest there is only one copy of the conversation on the company server. The 8 users would access the mail but it would be a common document. There is no replication of the history of the conversation. There is a history time line function, but that's simply a memory of what came when. So if the same 30 part conversation as the e-mail example had to happen and 1MB of history was accumulated, there would only be 1MB stored on the server instead of 240MB. With 20 conversations about a project over several months there would be 20MB of data stored versus 4.68GB. At 100 projects a year, the company would have to find space for 2GB of Wave storage versus the 468.75GB of e-mail. That's 0.426% of the data storage needs of e-mail.

Even with 20 times more Wave data, it would still only be 40GB (8.5%). Let's assume Google Wave only manages to cut 90% of the replication data of e-mail, that's still 90% fewer servers and 90% less energy consumption (simplistically). I think it'll be much better than that. Fewer hard drives means less toxic landfill and fewer raw materials used. Fewer servers means less stress on the power grid. The software makes a smaller carbon footprint that anything before it.
I have no idea if Google planned this, but by reconsidering e-mail they have saved themselves some cash and become better world citizens. Google runs giant server farms around the world and as they expand their services I assume they need to increase their cloud storage ability, basically lots of servers. By changing to their own Wave software they could bring their own voracious resource needs under control. Its good business for Google, and the rest of us, to spend less on technical infrastructure.
I work for a large multinational advertising company. We share hundreds of thousands of video files, documents, images and text every day. We could cut our e-mail carbon footprint by up to 99% by simply changing to e-mail software that is Open Source. That's incredible. I wish it were that simple at a global corporate level, the system hates change, but there's a better way to work on its way and its time to plan for an upgrade.
I would encourage everybody who cares about the environment and good software to bring this to the attention of their companies (it's Open Source, they can customise for their own needs) and use it at home. Perhaps my math is vastly incorrect, but I doubt it's 99.5% wrong.
Download the PDF chart
1 Wave (1MB) x 30 Updates x 8 Recipients (1 copy) = 30MB per Wave
I will be upfront and admit that my math is awful and I'm taking a few liberties with my knowledge of complex systems. Please forgive any mistakes.

E-mail is an old system. It involves sending packets of information from one server to another. From one hard drive to another hard drive. Each person keeps a copy of their mail and the response. If multiple people are copied on an e-mail, like all business correspondence, then each person has a copy of every response on their hard drive. So if 8 people have a 30 mail conversation about an internal project, there are 240 copies of pieces of the conversation on 8 machines or inboxes. In my office, we all "reply with history" so people can keep track of where we were in the conversation. Even one word answers. At 1MB average per mail (history adds up), that's 240MB of replicated data sitting on hard drives. If your company is like mine, 20 exchanges about a project over several months is not unheard of. That's 4.68GB of replicated data on one company's servers. A medium size company might have 100 projects a year like this. That's 468.75GB a year. That's not including video files, images, PPT documents and the other goodies that need sharing. Which is why Google decided to re-look e-mail I suppose.

Google Wave is different to e-mail. At it's simplest there is only one copy of the conversation on the company server. The 8 users would access the mail but it would be a common document. There is no replication of the history of the conversation. There is a history time line function, but that's simply a memory of what came when. So if the same 30 part conversation as the e-mail example had to happen and 1MB of history was accumulated, there would only be 1MB stored on the server instead of 240MB. With 20 conversations about a project over several months there would be 20MB of data stored versus 4.68GB. At 100 projects a year, the company would have to find space for 2GB of Wave storage versus the 468.75GB of e-mail. That's 0.426% of the data storage needs of e-mail.

Even with 20 times more Wave data, it would still only be 40GB (8.5%). Let's assume Google Wave only manages to cut 90% of the replication data of e-mail, that's still 90% fewer servers and 90% less energy consumption (simplistically). I think it'll be much better than that. Fewer hard drives means less toxic landfill and fewer raw materials used. Fewer servers means less stress on the power grid. The software makes a smaller carbon footprint that anything before it.
I have no idea if Google planned this, but by reconsidering e-mail they have saved themselves some cash and become better world citizens. Google runs giant server farms around the world and as they expand their services I assume they need to increase their cloud storage ability, basically lots of servers. By changing to their own Wave software they could bring their own voracious resource needs under control. Its good business for Google, and the rest of us, to spend less on technical infrastructure.
I work for a large multinational advertising company. We share hundreds of thousands of video files, documents, images and text every day. We could cut our e-mail carbon footprint by up to 99% by simply changing to e-mail software that is Open Source. That's incredible. I wish it were that simple at a global corporate level, the system hates change, but there's a better way to work on its way and its time to plan for an upgrade.
I would encourage everybody who cares about the environment and good software to bring this to the attention of their companies (it's Open Source, they can customise for their own needs) and use it at home. Perhaps my math is vastly incorrect, but I doubt it's 99.5% wrong.
Download the PDF chart
UPDATE: It has subsequently occurred to me that I failed to factor in the Google Wave time line functionality (what that does is capture each state of the Wave so that you can go back in time to see how it unfolded, grew, edited etc.) I suppose each state would require a total save of the e-mail, so it wouldn't be a 95% saving of space, it would be something like:
1 Wave (1MB) x 30 Updates x 8 Recipients (1 copy) = 30MB per Wave
vs
1 E-mail (1MB) x 30 Updates x 8 Recipients = 240MB per exchange
Which shows Google Wave would use about 12.5% of the hard drive storage of E-mail (not 0.43%).
10 Comments | |
Permalink | tagged
carbon footprint,
change,
comparison,
e-mail,
economics,
energy,
environment,
google wave,
green,
movement,
save,
versus 














Is Dripbook Aptly Named?
I'm updating this blog post after a few e-mails with Dripbook. They are a group of people trying very hard to make an excellent service. Most of my reasons for writing this post could have been dealt with better communication on their website. I suppose that's been done by now.
Photographers, illustrators, hair stylists etc are typically a little crap at keeping their websites maintained, if they exist at all. I appreciate any efforts to help these busy creative people show their work to the world. Dripbook is one of those efforts. I found out about them through a comment in one of the Virb art groups and Mashable have written about them too. I'll check anything out and it seemed like a good project. Easy portfolio tools combined with a social network aspect to help you connect and promote. So I sent them an application. I had to apply because... they're pulling the exclusivity card as a marketing stunt really. I said I'm handsome and make nice work and sent them my portfolio site (ironically). Thank goodness I was let in or my street cred would have collapsed like an underfed model. The feature I wanted to explore was their ability to publish to third party sites. Widgets that create a bit of code that refers to your dynamically updated portfolio instead of you having to create the books on your own site. I use viewbook.com for a site I built for a photographer which does that exactly. Unfortunately I never did get to trying that feature.
Most of Dripbook is fine even if it's a bit dull in the design stakes (a web 2.0 phenomenon apparently). The upload of images was easy enough, the networking idea is a good one. After I uploaded I found that my images came out looking soft. Which is odd considering they were sized down for web use and were sharp, black and white images when they left my desktop. Even that I could figure out given enough patience.
My irritation is that the site is not recognizing that I have "published" a book of drawings. It says it's published. But it's not visible to anyone else it seems. I've tried every "publish" button three times and now I'm bored. If you can't publish, you can't promote and then the social network is useless.Turns out that because I put a "Mature" marker on my book because it contained drawn nudity, I encountered a legal fix:
A fact that would have been good to know a few days ago.
Not wanting to spend any more time on the site I figured that I'd cancel my hard won account and focus my efforts on other tasks, like my real job. Except I can't find anywhere to cancel, suspend, deactivate, kill my account. Really. I've looked pretty hard. The FAQ neatly ignores the fact that anyone would be brazen enough to leave their services. I wonder what happens when you buy a premium account ($9 per month)?
Dripbook have informed me that they hadn't got to that detail yet. It'll be done now.
Dripbook is in Beta phase which may excuse any screw ups and my decision to leave their site is based on a few personal impressions, not only some basic technical glitches. The site is slow, I don't like their presentation options and I don't like their design.
I
'd leave, but I can't.ps. Turns out that no one had ever asked to leave. I have that dubious honour. My apologies, Dripbook, for being that guy.I have been deleted. After the short e-mail chat with Dripbook I appreciate that I was rather harsh on their Beta site. I only wish they had been a bit more forthcoming with how Beta they were. I mean, who doesn't have a delete account button? If you think I was a putz let the comments fly.