techcafeteria

Yesterday I joined my frequent collaborators John Kenyon and Susan Tenby at the Marin Nonprofit Conference, where we presented a 90 minute panel on nptech, from servers to tweets. John deftly dished out the web strategy while Susan flooded us with expert advice on how to avoid social media pitfalls. I opened up the session with my thesis: You have too many servers, even if you have just one”. I made the case that larger orgs can reduce with virtualization tech and smaller orgs should be moving to the cloud. The crowd in Marin was mostly from smaller orgs, so I focused the talk more on the cloud option, and that’s where I got all of the conversation going. My goal with the slides was to do a semi “ignite”, given that I only had 25 minutes and I value the Q&A over the talking head time.

Photo by smemon

Facebook announced that, on October 3rd, our profiles will all turn into “Timelines” that describe our lives (as Facebook knows them) in a glossy, magazine like format. And, as of right now, you can enable magazine apps (for WaPo and Guardian, more to come) that will randomly post what you’re reading to your wall without asking your permission first.I have two thoughts on this:

First, I feel sorry for the early adopters. I came to Facebook late, long after I had reason to distrust Zukerberg and co, in response to the cajoling of some of my more notorious nptech friends. I never believed that anything I posted there was private, and I had been well trained in online reputation management by my prior years of activity on bulletin boards, Usenet, mailing lists and Twitter. For many of you, all of your early mistakes are about to be unearthed and offered for everyone to see, from new friends that you’ve made since you got your FB voice modulated, to advertisers who are eager to know that, three or four years ago, you were really into SpongeBob.

Second, this new API feature that allows an app to post your activity when it wants strikes me as the epitome of anti-social networking. I really appreciate that I can peruse my wall and see articles, pictures and clips that my friends, co-workers and family thought I might like to see. This is, perhaps, the biggest boon and focus of social networking: curated sharing. It’s not random; it’s not based on a metric; it’s based on someone I like enough to call a friend saying “I found this worthwhile”. But, were I to install the WaPo app, it would decide which articles I want to share with my community for me. So I might click on some very boring report on a White House policy effort, or a review of some TV Show that I’m checking to verify that I was right to ignore it, and WaPo will happily tell my friends that I’m reading about this or that. This sucks the value out of social networking and turns me into a spammer.

Reports came in today that Spotify, the popular online music service, now defaults to posting every song that you listen to to your FB profile. If I have twenty friends who listen to Spotify all day and do this, I’m afraid that I’ll never bother to read my FB feed again. It’s cool if you’re listening to that awesome Gillian Welch cover of Radiohead’s “Black Star” and want to share the occasion; it’s not if you follow it up with the Hall and Oates hit, the Eddie Veder Beatles cover and the Indigo Girls or Beyonce or Five for Fighting song that follows. I’m not THAT interested.

So Facebook is apparently about to take sharing into the realm of spamming, and make all of us the perpetrators. Nice move…

For the three of you that noticed we were unavailable yesterday, my normally drama free (and wind-powered) hosting service, Canvas Dreams, had a nasty power failure and moved my domains to a new server. Since I follow what I consider to be a best practice of managing my DNS with a separate company from my hosting service (I’ve had to many unreliable hosting service experiences prior to finding Canvas Dreams), my site didn’t survive the transfer without a DNS update and, as usual, this all happened while I was out of town on a business trip. We’re back today.

In the Bay Area and still wrestling with the concepts of cloud computing? NTEN has you covered with a Cloud Computing mega event on Monday, August 29th. I’ll be presenting, along with such luminaries as Holly Ross, Allen Gunn, Donny Shimamoto and more.

And, finally, a bit of bragging about something I’m really excited about: we now have solar panels installed at our home (making this a very green blog indeed). We took a leasing deal from highly-rated Sungevity that should significantly reduce our energy costs along with our carbon footprint. Bill Gates might think home solar is a fad for the wealthy, but, hey, I work at a nonprofit and I not only can afford it, it will save me money. The picture above is our roof with the last panel being installed.

Geoff Livingston of NPTech Strategic consulting firm Zoetica held a little contest yesterday, and I won a copy of his book. The challenge? Explain, convincingly, why Google’s latest attempt at social networking, Google+, is not just a shiny object. Or why it is one. I chose the former, here’s my winning post:

Here’s my take on why, after the shininess fades, Google+ will still be an active social network.

First, they’ve learned from mistakes, theirs and others. They learned a lot from the failed Wave and Buzz projects, making privacy front and center; doing uncharacteristically flashy UI design (even stealing one of the Apple guys to do it); and not being too heavy-handed in the rollout. They are leveraging the Google App ecosystem, as Buzz tried to, but this seems like a cleaner and more serious effort—instead of just pasting a social network onto GMail, they’re incorporating apps like Picasa into it. Those of us already drinking the Google Koolaid (and they say that Google Apps is a high priority) will find it very useful (as opposed to redundant, as Buzz largely was).

The biggest lesson they learned was to not let people stream pollute as easily as they could on Buzz. I maintain that Buzz is a great platform for communications. It’s the ultimate cross between a blog and blog comments that could foster great conversations and raise the art of information sharing, if we didn’t have to wade through 20,000 redundant tweets to get to the good stuff. Google opened a floodgate of noise there, and too many users—including very good friends of mine—were happy to add to the din.

Second, they’ve created something compelling. It out-Facebook’s Facebook for interpersonal sharing and it can stretch to Twitter functionality. What’s powerful here is that, unlike Facebook, where targeting subsets of your friends requires advanced knowledge of the platform and a lot of patience, this interface makes it easy to either have an intimate chat or broadcast info widely. It’s easy to follow strangers that I’m not really interested in conversing with, at the same time that I can have deep talks with my close friends. They really got it right with Circles—friend/follower management on FB and Twitter is ridiculously kludgy in comparison. So, unlike Wave, which was too obtuse, and unlike Buzz, which wasn’t compelling, this is elegant and compelling. It wins people over.

Third, they’ve nailed SEO. The early adopters are raving about the hits it’s generating and the great statistics available. That’s going to be a more sticky draw than the shininess.

Most of all, they’ve emulated the cool Facebook stuff while shedding all of the annoyances. You can friend strangers here without over-sharing with them. You can +1 a commercial entity (or NPO) without inviting them to flood your stream with ads. You can tell your best friend something without sharing it with your mom. And that’s all easy; there’s no complicated help screen or multi-level privacy settings to contend with. It just works.

This is a public service announcement (aka rant) intended for IT product and service reps. In a nutshell:

If your spam and cold calls haven’t resulted in a business relationship, tracking me down personally on LinkedIn, Twitter or Facebook won’t work either.

Let’s be clear: it’s not a secret that I have purchasing responsibility for IT at my company, and my business contact info is easy to find (or purchase). Mind you, I don’t hire companies based on their ability to locate that information and email or call me. I hire consultants and purchase products based on the recommendations in my communities. So cold contacting me might be inexpensive and easy for you to do, but all it tells me is that you don’t respect my time or privacy and you can’t sustain your business based on quality and word of mouth. Two strikes against you, whereas, before you cold-contacted me, you had none.

But, in failing to spam me into a relationship, taking it to LinkedIn or the contact form here is taking your pathetic and unprofessional approach to marketing into a whole new realm of sleaziness and creepitude. Cold-contacting me at my business email or on my business phone is annoying and pathetic, but far more appropriate that tracking down my personal, non-business addresses and contacting me at those. It’s called stalking.

I’m looking at you, Server Technologies. The fact that you’ve spammed me in the past does not mean that we have an established business relationship, as your LinkedIn invite falsely indicates.

And local IT Recruiters 58 and Foggy—you take the cake. Within two minutes, out of the blue, you cold-called my work number, emailed me personally via this blog, and sent me a LinkedIn invite. That was so over the top annoying that I not only will never do business with you, I’ll make sure that all of my professional acquaintances are warned away.

Because I seriously question what a company that violates my privacy as a means of introduction would do if I actually relied on them and dealt with them financially. Ethical behavior? Not a safe thing to assume. Professionalism? Already in the toilet.

Social networks offer a great avenue for the type of business promotion that works for me—word of mouth. Sincere recommendations from people who think you’re good at what you do because they’ve used your products or services. You can foster my business by doing well enough with your current customers that they will speak well of you online. You can also demonstrate your expertise by publishing materials and distributing them on Slideshare and other public repositories (including your web site, of course). If you put your energy into establishing your credentials, instead of shoving your uncertified opinion that you’re great into every channel that you can reach me through, you’ll get a shot at my business. But using these networks to harass and annoy potential customers is incredibly stupid and short-sighted.

Following is a guest post from Jon Loomer, offering a different perspective on Facebook’s privacy changes.

Jon Loomer’s career has evolved from overseeing Fantasy Basketball product, content, marketing and promotion for the National Basketball Association to his current position as VP of Strategic Marketing for a non-profit. His focus is on social media strategy, Facebook and mobile development. You can follow him on Twitter @JonLoomer or read his blog focused on the subject of baseball atTippingPitches.blogspot.com. The following opinions are his only and do not reflect those of his affiliations.

It took a few weeks, but internet rage over Facebook’s Like button and latest privacy ramifications is in full swing. Bloggers swinging at Facebook’s knee caps with aluminum bats seem to outnumber those who come to CEO Mark Zuckerberg’s defense 20:1. And if a blogger does post a defense, duck and cover as soon as you hit “publish” because the rage will bubble up from the comments section.

So when Peter asked me if I’d be interested in writing a guest post on his blog in defense of Facebook’s changes, I had mixed emotions. On one hand, I’m absolutely flattered that he’d ask. On the other, I’m uncomfortable taking a hugely unpopular stand. The position is so unpopular that it ventures into “controversial” territory. Can I post anonymously?

I’m not a controversial dude. And any controversial opinions I have, I tend to keep relatively private, restricted to my inner circle.

But here’s the irony: I share these “controversial” opinions on Facebook. And I only share them with a small group of friends by using lists. But to the outer circle, I’m a harmless guy without much flare for the dramatic.

You must be outraged!

I may avoid controversy, but Facebook feeds off of it. Everywhere I turn, I read another blog telling me how angry I should be with Facebook’s dangerous disregard for my privacy. And because of this, a small part of me is trying to convince the rest of me that I, too, need to be outraged. But I can’t conjure up the energy.

The Utility of Facebook
First a little background on me as a Facebook user. I’ve used Facebook since it rolled out to the non-student public in 2006. My company partnered with Facebook on an application for that initial launch. So I’ve been there from “the beginning.”

And I’ve also been there through a multitude of changes, some vertical and some lateral. No matter how major the changes were, they were controversial. And the uproars increased as the Facebook population screamed past 100, 200, 300 and 400 Million.

This undoubtedly has something to do with my lack of rage now. I’ve become numb to the anger. Whether it’s a Facebook change or any other controversial revelation, I try to remain level headed. Before I react negatively to Facebook’s changes in particular, I try them out for a while. Think about the end game and why they’d make the change. And when I read a rumor about how Facebook is going to charge a monthly fee, or that they allow pedophiles to access my profile, I research first.

While I haven’t agreed with every change Facebook has made, I still recognize that they have made gradual improvements over the course of the past four years that have resulted in a much better overall product. The navigation is vastly improved, and I have far greater control now over who sees what and when.

Sure, some things (name, profile photo, gender, current city, networks, friends, pages) are available to the public now. But these are not things that bother me. You could already pull up photos of my handsome mug (here, here, here and here) by running a Google search. I’d hope my gender is obvious. And although I did scale down my pages after they became publicly viewable, I am now comfortable sharing those interests with anyone who cares.

After that, I’ve always used my privacy settings. Status by status, link by link, photo by photo, I pick and choose my audience. There are times when I keep what I share to a small audience of “Good Friends.” There are others when I share with all of my friends, some of whom I don’t know. And still others, I’ll feel the need to share with “Everyone,” as in—shudder—everyone on the Internet.

But I also use Twitter. I maintain a blog. So there are certain things I’m used to sharing with everyone. And when I share with the world, I have a reason for doing so.

It’s because of this control that I find Facebook extremely useful. I can contact just about anyone from my 500+ connections in an instant. I can promote my blog or share my son’s lemonade stand to raise money for childhood cancer research. Or I can simply goof off casually with friends. But it’s all controlled.

I also control what it is that third party developers see and what my friends can share about me. Developers can access everything that is already available to the public (which isn’t a whole lot), and my friends can’t share much more than that about me either. So I leave enough available for most useful applications to work, but without giving away more than I am comfortable.

The New Features
So all that said, Facebook rolled out a few features recently that were said to impact my privacy. I personally found them to be brilliant. I knew there would be backlash (there always is), but I admit I didn’t expect anything at this scale.

The Like Button: This addition has essentially made millions of web pages an extension of Facebook. The collage of my friends’ faces acts as a welcome mat at the front door of sites that are new to me. My friend likes this? Let me check it out. My friend says I should go to this restaurant? Not a bad idea. These are things that I would have otherwise seen on Facebook, but now I see them at the source to provide more relevance.

Not only is the Like button good for me as a user, but it is also good for me from the business side—both on my blog (loosely defined as a business) and my organization’s web pages. I’ve quickly realized that users are much more inclined to click a Like button than go through the process of retweeting or even sharing through Facebook. It’s easy. It’s awesome.

Instant Personalization: Policies aside (we’ll get to this later), I love the idea. I can go to Pandora and immediately access music that I like or my friends like. I can go to Yelp and immediately find a restaurant that they recommend. There is so much to like here. It makes the web a warmer, more social, and more relevant place.

Updated Privacy Settings: This has caused a stir, but it really wasn’t a problem for me. As I mentioned before, I’ve always been on top of my privacy. So when the new privacy settings were rolled out, I took my time to make sure everything was set up the way I wanted. While some may claim that Facebook pulled a fast one on us, it’s not as if this was done discretely without you knowing. You were forced to go through the new settings and verify. Might it have been a bit overwhelming? Maybe. But if you care about your privacy like I do, it’s something you should understand.

Community Pages: This one has been run more on the down low because it is a beta product. Thousands of community pages have been created by Facebook and some general pages have been converted (often to the dismay of the administrator). Unlike the typical Facebook page, there is no admin control (at least for now) of the community page. It is, apparently, intended to be a wiki of some sort, with information fed by people’s content who like the page. It’s not clear yet what value, if any, these pages have, but the usage is likely to evolve.

The Confusion
Part of Facebook’s problem is that this new Facebook-centered web can be a bit startling at first. When you go to another website, you don’t expect to see a list of your Facebook friends who like something. You don’t expect a website you did not previously visit to know what you like and don’t like to make recommendations. But people need to simply look at the web as an extension of Facebook, particularly when using social plug-ins. Instead of viewing that your friend likes an ESPN article in your Facebook feed, you see it on ESPN.com. It’s not as if the world can see this information. What you see is different than what I see. And your privacy settings still apply, which may not be immediately obvious.

There is also confusion because there are very few blogs and articles being written on this subject that equally weigh the issue. Many make it seem as though all of our private content is at risk; that no matter how we adjust our privacy settings, everything is available to the world. They are biased towards negativity and rage because that’s what brings traffic. We are told to either delete our Facebook profiles or simply put them on lock-down, preventing everyone from seeing anything, disallowing instant personalization, and blocking as much information from third parties as possible.

The reality, at least as far as I can tell, is that the latest changes won’t harm you if you are already on top of your privacy settings and careful about what you share. But based on the media coverage, it would be easy for someone to overreact and go with the flock.

Show Me
This is my biggest problem with the outrage over Facebook’s changes: Almost everything I read is in abstract terms. Please, show me the danger of Facebook’s changes. You’ve probably seen this example of Facebook users who have told the world, knowingly or not, that they have cheated on a test. Well, I can do the same with Twitter users. What’s the point?

Maybe I should feel bad for people who unknowingly publish embarrassing information about themselves for the world to see, but I don’t. For many reasons.

First, let’s not fall for the claim that Facebook made this radical change from closed to open overnight. The latest change did allow search engine indexing of your public profile (if you kept the box checked to allow it) or of that information you shared with “everyone,” but keep in mind that the former definition of “everyone” was all users on Facebook. So you went from sharing embarrassing photos and information about yourself to 400 Million people to the entire world. Eh.

And again, Facebook forced us—all of us—to confirm our privacy settings. Did you ignore them? If you did, should I feel bad for you? Eh.

I understand that I don’t represent all Facebook users, and that’s a very good argument for anyone opposed to the changes. Most people do not spend the time refining their privacy. And many may simply be confused by the settings.

Still, if you’re confused, just restrict everything as much as possible. I keep seeing stats on number of settings and options, but if you just set everything to “Friends” (and your friends truly are your friends), you’ll be fine. Assuming, of course, you’re still careful about what you share.

Everyone needs their own global privacy policy, and this goes beyond Facebook. When you share, do so with the understanding that, even with the best possible settings, any friend can simply copy and paste your status; or save and repost your photo; or simply post a photo or story about something you did. No privacy settings can prevent stupid activity from being seen. It will eventually get out.

That said, I am leaving the door open slightly for the possibility that Facebook has given others far more access to my private life than I know. If this is the case, show me. Show me the application that could potentially harm me.

The Policies
While I enjoy using Facebook and am not in the “delete my profile” community, I admit that I’m not all that comfortable with the entire path that Facebook has taken. I enjoy the new features and am fine with the current privacy settings. However, I do think that they need to be better at communicating changes. They need to be better at communicating, from page to page, what is viewable and what isn’t. Go above and beyond to explain the user’s privacy. Smack them in the face with what audience they are sharing. While I do think Facebook has done a better job at communicating changes than they are given credit, they need to do more.

And I also agree that opt-ins instead of opt-outs are the best policy, particularly with a potentially controversial change. If you are so sure someone is going to want something, first make the compelling argument. Encourage them to check it. Show them what they’re missing if they don’t.

Even so, I firmly believe that putting too much focus on Facebook takes away the important focus on the user’s responsibility to do everything they can to protect themselves. As mentioned before, users needed to agree to each change. We need to be vigilant and understand the ramifications. And if you are too lazy to do the research to understand it, at the very least you need to be more careful about what you post.

How Facebook Can Get Out of this Mess
Just as I am not completely in Facebook’s corner on some of their policies, I also see ways for them to get out of this PR firestorm. While I don’t have much sympathy for the ignorant user, Facebook is still responsible for communicating that these are positive changes.

If I were Facebook, I’d do the following:

• Put a My Privacy: Who Sees This? link on Community Page by “Related Posts by Friends”


• Put a My Privacy: Who Sees This? link within social plug-ins, where feasible


• Put a My Privacy: Who Sees This? link on “trusted third party” sites that implement instant personalization


• Provide video and commentary explaining some of the changes, answering the criticisms, showing the user why the changes are good for them, and acknowledging that those changes are not for everyone, providing an easy explanation of how to protect themselves


• Provide regular webinars or tours on features and use of lists to everyone, not just those with the proper page connections


• Make Instant Personalization opt-in

The last item may be the trickiest since users have already technically opted in to instant personalization when they went through their new privacy settings for the first time. But considering this project is technically a pilot, there’s no need to automatically opt everyone in. Do what they did before. Bring up a box explaining what instant personalization is. Provide videos. Explain why it is good for them. Explain potential risks. Shoot down conspiracies. And then force the user to check the box if they want it.

In Conclusion
While I am not surprised by user backlash as a result of the most recent Facebook changes, I did not expect this level of outrage from mainstream media and technically savvy, intelligent people. With that in mind, it is important that we all do the following:

• Research and understand the benefits and risks involved


• Weigh those risks and benefits with the way that each person uses Facebook


• Understand and actively utilize Facebook’s privacy settings


• Establish a global “privacy setting,” understanding that if we are concerned about privacy we should always be careful about what we share

In the end, it’s personal. These changes are likely to affect me differently than they do you. Maybe Facebook is just too much of a hassle for you. Maybe Facebook does not offer enough benefit to you to actively manage a sometimes confusing control panel of privacy settings. Maybe you do have reason to be outraged. But I don’t believe this feeling is universal. We all need to rationally weigh the risks and benefits and decide what is best for us.

Big changes are happening at Facebook, and they mean that what you do and say, on and off of Facebook, is now being more heavily tracked and more broadly shared. If you think that your Facebook data is somewhat private—e.g., shared only with friends and people you specify—you are wrong.

Facebook announced dramatic changes in their service at their annual “F8” conference on Wednesday. Facebook used to be a network where you could establish semi-private communities with family, friends and like-minded sets of people. Now it’s an internet-wide info-sharing platform that can keep your friends, and the businesses and advertisers that Facebook partners with, fully briefed on all of your internet-based activities and opinions.

The biggest announcement was the introduction of the Open Graph and the new “Like” buttons for the web at large. Yesterday, you could only “like” or “fan” something that appeared on Facebook’s web site. Now you can “like” things anywhere that the social graph and like buttons are implemented. What you “like” will be shared with Facebook, your Facebook friends, and all of the applications you subscribe to on Facebook, and, depending on your Facebook privacy settings, the world at large.

Also this week, and all of a sudden, despite what you might have confirmed a few months ago when Facebook started this paradigm shift, your likes, interests and job history are now Google searchable. That’s right: even if you went in and flagged them as private, your only way to protect this information, as of yesterday, is to remove it (and wait a month for it to fall out of Google’s cache).

Online privacy is a relative concept

Much of the Facebook privacy that we lost wasn’t real privacy to begin with, because any time you add an application (such as a quiz), that application’s developers have complete access to your entire Facebook profile. Worse, anytime a friend invites you to use an application, that application gets access to your profile. You don’t have to lift a finger to have data that you’ve marked as private shared with strangers; you just have to have friends on Facebook who aren’t thinking that, by inviting you to compare movie favs, they’re telling a complete stranger your gender, age, birthdate, job history, sharing all of your photos and publishing your wall to them.

Why “Love it or leave it” is unfair

I have friends who are somewhat blaze about all of this. After all, nobody put a gun to my head and ordered me to join Facebook. I just got so many requests from friends and family that I caved. And, once I caved, I connected to a bunch of “blast from the past” friends, extended family, former co-workers and current associates. So, now have a real investment in Facebook as a social connector. Sure, if I don’t like these changes, I can just delete my account and be done with it. But I’m throwing away far more than just a social network profile—I’m tossing out my connection to my communities of friends, family and professional associates, who are now expecting me to be on Facebook with them.

I could decide that I don’t like the policies of my local utility company, too, and just cancel my service. But the services they provide enable other services that I want/require as well—such as light, heat, computing, communication. Leaving Facebook wouldn’t be as extreme as canceling power services, but, with 40 million users and climbing, Facebook is like a utility in many people’s lives, and it supports services in such a way that relationships beyond our relationship with the service provider are centered there.

Change Management

This is what is so dishonest about CEO Mark Zuckerberg’s repeated assertion that Facebook is only following the direction of the Internet as an open sharing platform. He is right abut the trend. But this is the equivalent of saying that the trend is now for baggy pants and see-through tops, so all of your clothing has been swapped out in accordance with the trend. The internet is all things to all people, and there are plenty of places on it where privacy and closed community are the norm. Just because the internet is becoming more open, it doesn’t mean that Internet users need to be dragged into this new era.

It all boils into “Opt Out” vs. “Opt In”, and respecting rather than walking all over your customers. Facebook began with an assumption of privacy; changes in that assumption should be acknowledged by each user before they are enacted. Facebook could have easily developed their platform in ways that give users the choice of having open or private profiles. Instead, they’ve simply switched our private data to public without asking if that compromises our security, reputation or preferences. And it doesn’t escape my notice that there’s great money to be made in having more personal info about what I like and who I share that information with.

What you should do if this concerns you

If you went in and verified/altered your Facebook privacy settings a month or two ago, you should make another visit ASAP. Facebook has turned it around. Beth Kanter has a good write-up on what has changed. If you have any custom Facebook Pages, look out there as well—even if you’ve set profile data to private, if you link to any of your profile info from a Facebook page, it will default back to public. Whatever you do with your privacy settings, most of your basic profile data is now public and there is no option to make it private. So review your employment history, “about” and likes sections to make sure that it only has data that you don’t mind sharing with Google searchers and every advertiser on earth.

It all boils down to this

Facebook is now like Twitter and Google, with even less options for privacy than those big public networks offer. This doesn’t have to be a bad thing, it’s just a very different thing, and the crime here is mostly that “F8” and “social graph” are not terms that the vast majority of the 40 million Facebook users are paying any attention to. If you’re reading this, you know better, so you can set your profile up with information that you don’t mind being in the public domain, and you can decide if you’re willing to “like” things on the internet and, thereby, expose yourself and your Facebook community to the demographic analysis and actions that will ensue. I won’t be abandoning Facebook over this, but I’m very restrictive in my use of it, and will continue to approach it with great caution.

We’re all back from the Nonprofit Technology Conference, where nine of the ten Idealware bloggers congregated, along with some 1,440 of our peers in the nptech community. What a gas! NTC, as we call the conference, is what high school would have been like if everyone had been a member of the popular clique. The combination of peer education and celebration of our common interest in saving the world with heart and technology make for an exuberant occasion. And I can’t say enough about the awe and appreciation I have for Holly, Anna, Annaliese, Brett, Sarah and Karl, and the amazing event that they recreate year after year for us.

But, enough gushing. One of my (many) rants regards my concern that, although the biggest group of people that we call “nptechies” are the ones who support technology in their organizations, our biggest nptech conferences focus heavily on social media and the web (NTC, Netsquared, and now SXSW). It is true that the advent of social media and the interactive web is spawning a revolution in the way that we do advocacy and fundraising. But there is no less of a revolution in our server rooms, where virtualization, cloud computing and wireless devices are changing the entire way that we manage and deliver applications.

Our System Administrators, Support Specialists and Accidental Techies need to share in the peer support that can inform their efforts and help them feel more connected, both to their missions and the broader community. This year, in deference to a throat getting hoarse from ranting, I took a first stab at addressing this gap.

The Tech Track

The tech track was conceived as a six session “mini” track; five of the proposed sessions made the cut. The topics went from the basics to the broad overview:

• Tech Track 1: Working Without a Wire (But With a Net): Dealing with Wireless Networks, Laptops, and Cell Phones


• Tech Track 2: Proper Plumbing: Virtualization and Networking Technologies


• Tech Track 3: Earth to Cloud: When, Why and How to Outsource Applications


• Tech Track 4: Budget vs Benefits: Providing Top Class Technology in Constrained Resource Environments


• Tech Track 5: Articulating Tech: How to Win Friends and Influence Luddites.

Joining me in these sessions were fellow blogger Johanna Bates of OpenIssue, Matt Eshleman of CITIDC, Tracy Kronzak of Applied Research Center, John Merritt of the San Diego YMCA, Michelle Murrain of OpenIssue, Michael Sola of National Wildlife Federation and Thomas Taylor of the Greater Philadelphia Cultural Alliance.

Subject Matter

Instead of doing the usual Powerpoint presentations and talking to the crowd, we pulled the chairs into circles for these sessions and put the session agenda up for grabs, asking each group what issues, related to the session topic, were foremost in their minds. The conversation was rich, and served as a healthy catalogue of the challenges facing nonprofit technology practitioners. Some highlights:

• Supporting remote laptop use in a western state with very little wireless bandwidth available


• Securing our networks while making network data accessible on mobile devices


• Supporting use of and crafting fair policies to address the boom in mobile devices


• Understanding the risks and benefits of virtualizing servers and desktops


• Knowing how and when to virtualize, and how Storage Area Networks fit in the big picture


• Weighing the risk of cloud computing, which also entails weighing the risks of our non-cloud networks


• Knowing what to ask a cloud provider to insure that data is safe, even in the case of the provider going out of business


• Assessing the cost of owned vs service-provided applications


• Assessing the readiness of Cloud Computing, and moving large, complex server rooms to the cloud


• Chickens and eggs: what to do when IT is asked to budget, but is not part of the planning process prior?


• What strategies can be applied to provide good technology with limited budgets?


• What tools and resources are available to help with the budgeting process?


• How can we engage our users when we roll out new technology?


• How do we get them to attend training?

Next week, I’ll follow this up with some of the answers we came up with for these questions.

I recently took on the project of migrating the Idealware articles and blog from their old homes on Idealware’s prior web site and Google’s Blogger service to our shiny, new, Drupalbased home. This was an interesting datamigration challenge. The Idealware articles were static HTML web pages that needed to be put in Drupal’s content database. And there is no utility that imports Blogger blogs to Drupal. Both projects required research and creativity.

The first step in any data migration project is to determine if automating the task will be more work than just doing it by hand. Idealware has about 220 articles published; cutting and pasting the text into Drupal, and then cleaning up the formatting, would be a grueling project for someone. On the other hand, automating the process was not a slam dunk. Database data is easier to write conversion processes for than free form text. HTML is somewhere in the middle, with HTML codes that identify sections, but lots of free form data as well.

Converting HTML Articles with Regular Expressions

My toolkit (of choice) for this project was Sed, the Unix Stream Editor, and a generic installation of Drupal. Sed does regular expression searching and replacing. So I wrote a script that:

1. Deleted lines with HTML tags that we didn’t need;


2. stored data between title and body tags;


3. and converted those items to SQL code that would insert the title and article text into my Drupal database.

This was the best I could do: other standardized information, such as author and publishing date, was not standardized in the text, so I left calling those out for a clean-up phase that the Idealware staff took on. The project was a success, in it that it took less than two days to complete the conversion. It was never going to be an easy one.

Without going too far, the sed command to delete, say, a “META” tag is:

/

That says to search for a literal “less than” bracket (the forward slash implies literal) and the text meta and delete any line that contains it. A tricky part of the cleanup was to make sure that my search phrases weren’t ones that might also match article text.

Once I’d stripped the file down to just the data between the “title” and “body” tags, I issued this command:

s/.*(.*)/insert into articles (title, body) values (‘1’, ‘2’);/

This searches for the text between HTML “title” tags, storing it in variable 1, then the text between “body” tags, storing it in variable 2, then substitutes the variable data into a simple SQL insert statement in the replacement string. Iterating a script with all of the clean-up commands, culminating in that last command, gave me a text file that could be imported into the Drupal database. The remaining cleanup was done in Drupal’s WYSIWYG interface.

Blog Conversion

As I said, there is no such thing as a program or module that converts a Blogger Blog into Drupal format. And our circumstance was further complicated by the fact that the Idealware Blog was in Blogger’s legacy “FTP” format, so the conversion options available were further limited.

There is an excellent module for converting WordPress blogs to Drupal, and there were options for converting a legacy Blogger blog to WordPress. So, then the question was, how well will the blog survive a double conversion? The answer was: very well! I challenge any of you to identify the one post that didn’t come through with every word and picture intact.

I had a good start for this, Matthew Saunders at the Nonprofits and Web 2.0 Blog posted this excellent guide. If you have a current Blogger blog to migrate, every step here will work. My problem was that the Idealware blog was in the old “FTP” format. Google has announced that blogs in their original publishing format must be converted by May 1st. While this fact had little or no relationship to the web site move to Drupal, it’s convenient that we made the move well in advance of that.

To prep, I installed current, vanilla copies of WordPress and Drupal at techcafeteria.com. I tracked down Google’s free blog converters. While there is no WP to Drupal converter, most other formats are covered, and I just used their web-based Blogger to WordPress tool to convert the exported Idealware blog to WP format. The conversion process prompted me to create accounts for each author.

To get from WordPress to Drupal, I installed above-mentioned WordPress-import module. As with the first import, this one also prompted me to create the authors’ Drupal accounts. It also had an option to store all images locally (which required rights to create a public-writeable folder on the Drupal server). Again, this worked very well.

With my test completed, I set about doing it all over again on the new Idealware blog. Here I had a little less flexibility. I had administrative rights in Drupal, but I didn’t have access to the server. Two challenges: The server’s file upload limit (set in both Drupal and PHP’s initialization file) was set to a smaller size than my WordPress import file. I got around this by importing it in by individual blogger, making sure to include all current and former Idealware bloggers. The second issue was in creating a folder for the images, which I asked our host and designer at Digital Loom.com to do for me.

Cleanup!

The final challenge was even stickier—the posts came across, but the URLs were in a different format than the old Blogger URLs This was a problem for the articles as well. How many sites do you think link to Idealware content out there? For this, I begged for enough server access to write and run a PHP script that renamed the current URLs to their former names—a half-successful effort, as Drupal had dramatically renamed a bunch of them. The remainder we manually altered.

All told, about two hours research time, three or four hours conversion (over a number of days) and more for the clean-up, as I wasted a lot of time trying to come up with a pure SQL command to do the URL renaming, only to eventually determine that it couldn’t be done without some scripting. A fun project, though, but I’d call it a success.

I hope this helps you out if you ever find yourself faced with a similar challenge.