Accelerate – Alanna J Brown from Alanna J Brown on Vimeo.

I’m playing with Alanna next week, on the U of T campus.

Next to email, replacing Google Reader as my feed reader was relatively easy, though I’ve chosen to use the move as an opportunity to clean out my feed subscriptions, rather than doing a straight export/import. I’ve replaced Google Reader with two free software feed readers: Liferea (desktop) and Tiny Tiny RSS (web).

A reading list can be very personal, and it can also be very misleading out of context. For example, my reading list suggests all sorts of things about my religious and political views, about the communities to which I may be connected, etc. Though, it would take some analysis to try and figure out why I subscribe to any particular feed. Is the author’s view one I espouse and whole-heartedly hold as my own? One I find interesting, challenging, or thought-provoking? Or one I utterly disagree with yet want to learn more about?

There is something private about a complete reading list, much like the books you might check out from the library or the videos you might rent from a store. As we get more of this content through the internet, it’s easy for these lists (and even more behavioural data about how we interact with them) to be compiled in large, centralized, proprietary databases, alongside all sorts of other personal information that would not be available to a traditional Blockbuster or public library. Besides the software fredom issues, this is another revealing personal dataset that I can claim more control over by exercising software freedom, rather than dumping it into a big centralized, proprietary database. Both software freedom and privacy issues are at play here.

Desktop Client: Liferea

Liferea is a desktop feed reader for GNU/Linux. Google Reader was my first feed reader, so a desktop feed reader was a bit of an adjustment, but there are a few things I really like about it:

• Native application: It integrates well with my desktop, with something like Ubuntu’s Messaging Menu, and it’s a client that feels somewhat familiar in GNOME.
• Control over update frequency: One of the things that bugged me about Google Reader is it constantly checks for new content, whether or not you want it to. Sometimes, I don’t want to see anything new until tomorrow. It’s nice to be able to click update, read, and then let it be until I choose to update again. (Though, the downside is missing material if you don’t update often enough.)
• Integration with Google Reader / Tiny Tiny RSS: This is a killer feature. You can use Liferea to read feeds through the Google Reader API, and recent versions have added support for a tt-rss backend as well. This helped with my transition because I could use Liferea as a front-end for Google Reader before I was prepared to migrate my feeds, to test it out, to ease the transition, etc. And, I will be able to use Liferea and tt-rss together to have both desktop and web-based clients.
• Embedded Web Browser: This is also a killer feature. Websites that don’t have full-text feeds and only offer a content snippet are annoying in Google Reader, because you have to leave Reader to see the full content. But, in Liferea, you can tell it to automatically load content for a feed using the embedded web browser instead of just viewing the snippet, or hit enter on any feed entry to load the URL using the embedded browser. It even has basic tabbed browsing support, so you don’t have to flip back and forth between your web browser and your feed reader. This makes reading content from non-full-text feeds easy without leaving Liferea.
• Integrated Comments: Liferea can detect comment feeds on many blogs, and it shows a handful of comments underneath entries. Combine this with a quick enter key to visit the web page with the embedded browser, and you no longer have to leave the feed reader to participate in the comments. This is a nice step up from the usual isolation of a feed reader from comment threads.
• Authentication support for protected feeds: This is a useful feature for subscribing to protected content, such as an updates feed on an internal wiki.

I tested Liferea as a Google Reader front end, then migrated subscriptions group by group (giving me a chance to re-organize, though I could have just used an OPML export/import), and once I upgrade to Liferea 1.8, I’ll connect it to tt-rss.

Other Desktop Clients: RSSOwl is a free software, cross-platform (Windows, Mac OS X, GNU/Linux) feed reader, which also has Google Reader integration. I have only tried this briefly, so that I could recommend it to Windows users.

Web Client: Tiny Tiny RSS

Tiny Tiny RSS is a web-based feed reader, similar to Google Reader, but free software that you can run on your own web server. There are some feeds I read all the time, and others I’ll skim or catch up on when I have a chance. For the must-read feeds, it makes a huge difference to be able to read them from my mobile computer. With Google Reader, I used grr, and there is a mobile web interface. I migrated my must-read feeds to tt-rss instead of Liferea so that I’d have easy access to them while away from my laptop, while still having the ability to use Liferea when on my laptop with it’s tt-rss integration. I’m moving more and more feeds into tt-rss, though I plan to leave some less frequently updated, less important feeds or feeds that are difficult to read from my mobile in Liferea only.

Some cool features:

• Publish articles to shared feed: Google Reader had a shared articles RSS feed, and I’d piped that into blaise.ca. tt-rss has a similar RSS feed, which I’ve also been able to include on my website
• Mobile web interface: tt-rss has a mobile web interface for webkit browsers powered by iUI. With Macuco on my N900 or the Android web browser, it works quite well — though, only for full-text feeds.
• Filters: With tt-rss, you can create filters on feeds. So, for example, I am automatically publishing articles from the Techdirt feed that I’ve written, or I can auto-delete posts for a particular series or author that I’m not interested in to custom tailor a feed to my interests. It’s very useful for automating certain actions or reducing noise on a high-traffic feed.
• Custom CSS: I suppose you could customize Google Reader’s styles with a GreaseMonkey script or something, but tt-rss offers custom CSS overrides and multiple themes out of the box, which is great for setting some more readable default colours.
• API: tt-rss has an API, which allows for Liferea integration, an Android client, etc.
• Authentication support for protected feeds: Like Liferea, tt-rss provides support for feeds requiring authentication.

As with Liferea, tt-rss gives me control over how frequently updates run, since I schedule the update job. But that control also comes without the downside of missing content if I’m away from my feed reader for a while; unlike a desktop client that needs to be open to retrieve new content, tt-rss does so in the background from the server, so it can still track new entries while I’m away. It has the benefits of Google Reader’s persistent background updates, while still giving me control over frequency and scheduling. I have the update job set to run a few specific times through the day, and tt-rss gives you the option to set an even longer update interval for any given feed.

While I was initially migrating from Google Reader to Liferea, Tiny Tiny RSS is quickly becoming my primary feed reader, while Liferea will become my primary desktop client for tt-rss and home for less frequent/important/non-full-text feeds.

Other Web Clients: NewsBlur is another web-based, free software feed reader, which is based on a more modern web stack and seems to have some neat features. I have yet to try it, and I’m not sure of the state of its mobile or API/desktop integration, which are two things I really like in tt-rss. It’s worth taking a look at though for sure. NewsBlur.com has a hosted service, if you aren’t able to run your own web server or don’t have a friend who’s running one.

Conclusion

My migration away from Google Reader is essentially complete. I have less than a dozen feeds remaining there, but mostly old or broken feeds. I no longer log into Google Reader to read anything, though I’ve got one more round of cleaning to do to empty my account. I’m currently split between Liferea and tt-rss, but with Liferea 1.8, I’ll be able to integrate the two. I also have other libre options to explore with NewsBlur and RSSOwl.

There is nothing that I miss about Google Reader, and if anything, with an embedded browser, native desktop options, integrated comments, control over update scheduling, feed filters, and authentication support for protected feeds, I have a lot of useful features now that I didn’t have with Google’s proprietary service — nevermind more software freedom and less surveillance.

Mark Zuckerberg’s letter to shareholders included in Facebook’s IPO filing contains a pretty bold vision for Facebook to not just connect people and enable them to share, but to fundamentally restructure the way that the world works:

By helping people form these connections, we hope to rewire the way people spread and consume information. We think the world’s information infrastructure should resemble the social graph — a network built from the bottom up or peer-to-peer, rather than the monolithic, top-down structure that has existed to date. We also believe that giving people control over what they share is a fundamental principle of this rewiring.

We have already helped more than 800 million people map out more than 100 billion connections so far, and our goal is to help this rewiring accelerate. [emphasis added]

That sounds pretty lofty, but if you recognize that Facebook provides a social networking service that hundreds of millions of people use — but forget for a moment that it’s Facebook — it’s quite a bold “social mission.” And there are many examples of how the service has been used as a key tool in affecting change on everything from opposition to the Canadian DMCA to the Arab Spring. There’s no doubt that the service makes it easier for people to organize in a more bottom-up way.

But, once you remember that it’s Facebook we’re talking about, the vision sounds more problematic. Could Facebook ever truly bring about a peer-to-peer, bottom-up network? The notion seems to be an inherent contradiction to Facebook’s architecture — as a centralized, proprietary, walled garden social networking service. Facebook may enable a more bottom-up structure, but it’s a bit disingenuous for Zuckerberg to decry a monolithic, top-down structure when Facebook inserts itself as the new intermediary and gatekeeper. As a centralized, proprietary, walled garden service, Facebook is a single point for attacks, control, and surveillance, never mind controversial policies or privacy concerns. Facebook may enable a more bottom-up and peer-to-peer network compared to many things that came before, but there is something fundamentally at odds with a truly distributed solution at the core of its architecture and its DNA.

To realize the full potential of bottom-up, peer-to-peer social networking infrastructure, we need autonomous, distributed, and free network services — the sort of vision that StatusNet/Identi.ca or Diaspora have tried to bring about. Rewiring the world to create a more bottom-up, peer-to-peer network is a bold vision for Zuckerberg to put forth — and one that Facebook has advanced in many ways — yet it’s fundamentally at odds with the reality of Facebook as a centralized and proprietary walled garden.

Read the comments on Techdirt.

in 2007, the Songwriters Association of Canada gained some international headlines with a proposal to legalize non-commercial peer-to-peer file sharing through an ISP levy. This sort of proposal wasn’t new, but had not been so prominently put forth by an artist organization before. There were serious problems with the proposal, but it stimulated a healthy debate and it started from many correct premises — that file sharing should be embraced, that digital locks and lawsuits were not a way forward, etc. But it was a non-voluntary, “you’re a criminal” tax that could open the floodgates for other industries to demand similar levies.

I was a member of the Songwriters Association of Canada from 2007-2011, and I had the opportunity to express my concerns about the proposal to many people involved. Last year, I attended a session with an update on the proposal, and was surprised how much it had changed. The proposal had dropped the legislative angle in favor of a business to business approach, with an actual opt-out option for both creators and customers of participating ISPs. Unlike groups behind other licensing proposals, the SAC has actually been responsive to many concerns, and unlike other artist groups, the SAC takes a decidedly positive view on sharing music and the opportunities technology provides to creators. This attitude comes through in the proposal:

Rather than a legislative approach to the monetization of music file-sharing as we originally envisioned, the S.A.C. is now focused on a “business to business” model that requires no new legislation be enacted in Canada.

Our basic belief however remains the same: Music file-sharing is a vibrant, open, global distribution system for music of all kinds, and presents a tremendous opportunity to both creators and rights-holders. [...]

People have always shared music and always will. The music we share defines who we are, and who our friends and peers are. The importance of music in the fabric of our own culture, as well as those around the world, is inextricably bound to the experience of sharing. [emphasis changed]

As the copyright debate heats up again in Canada in light of SOPA and new pressures on pending legislation, this positive attitude towards peer-to-peer file sharing was expressed again in a recent TorrentFreak interview with the SAC VP, Jean-Robert Bisaillon:

We think the practice [of file-sharing] is great and unstoppable. This is why we want to establish a regime that allows everyone to keep on doing it without stigmatizing the public and, instead, find a way for artists and rights holders to be fairly compensated for the music files that are being shared. [...]

Other positive aspects include being able to find music that is not available in the commercial realm offer, finding a higher quality of digital files, being able to afford music even if you are poor and being able to discover new artists or recommend them to friends. [...]

Music is much better off with the Web. The internet network allows for musical discovery despite distance and time of the day. It has sparked collaborations between musicians unimaginable before. It has helped artists to book international tours without expensive long-distances charges and postal delays we knew before. [emphasis added]

However, significant problems remain with the proposal. For example, the original criticism still stands as to how this would scale for other industries — what about book publishers, newspapers, movie studies, video game manufacturers and other industries that are also crying foul about “piracy”? The SAC dismisses other cultural industries pretty quickly, as if only the music industry is concerned about unauthorized copying. And, just like private copying levies have suffered from scope creep, as people no longer buy blank audio cassettes or CDs, or short-sightedness, as technology changes rapidly, it’s not clear how the SAC model would adapt to growing wireless and mobile computing or more distributed file sharing. Many more questions remain: Would small, independent artists, who are not charting through traditional means, get fair treatment? Is it wise to largely rely on a single, proprietary vendor, Big Champagne, for tracking all distribution? Would consumers be paying multiple times for music? What does it mean to “self-declare not to music file-share” in order to opt-out?

But the central problem with the proposal is the SAC’s copyright crutch. Jean-Robert Bisaillon says things like,

The Internet has dramatically increased the private non-commercial sharing of music, which we support. All that is missing a means to compensate music creators for this massive use of their work. [emphasis added]

And the proposal says things like,

Once a fair and reasonable monetization system is in place, all stakeholders including consumers and Internet service providers will benefit substantially. [emphasis added]

The SAC seems obsessed with a “monetization system,” when the truth is there is no one model, no magic bullet. Rather, the the sky is rising and the path to success involves all sorts of different models and creative approaches, most of which don’t depend on copyright or worrying about getting paid for every use. Even a voluntary license plan is still a bad idea. The means to compensate music creators isn’t missing, it’s just increasingly found outside of copyright.

Still, it’s important for the SAC’s voice to be heard as the copyright debate heats up again in Canada. As a creator group offering a positive take on peer-to-peer file sharing, and denouncing an “adversarial relationship” between creators and fans, they offer an important counterpoint to the SOPA-style provisions being pushed by Canadian record industry groups. I would take the SAC’s constructive and responsive approach over record industry astroturfing and fear mongering any day.

Read the comments on Techdirt.

To be clear, I still generally trust and respect Google, and I do believe they’re generally less evil than most, but…

1. Despite great support for open source software, they remain a proprietary software company at their core. Google is a friend to open source infrastructure, but not to free (libre) network services. Specifically, it’s the proprietary network services I’m degoogling from.
2. The sheer amount of data — email, contacts, documents, calendar, RSS feeds, social graph, phone calls, photos, GPS location, nevermind web searches… — aggregated into a one single account with a proprietary service provider is an obviously bad idea. Even if Google never intends to do anything bad with it, they can make mistakes. Even if Google never does anything bad itself, it’s a single vector for attack from an outsider. And it’s not your account.

Email is one of the easiest services from which to degooglify. It’s also a good example of a multi-step transition.

Changing the front-end

The first thing I did was to stop using the Gmail web interface. I configured my Gmail account in Thunderbird, which I was already using for other email accounts. Google’s commitment to data portability often makes it easy to switch your front-end software before switching the back-end, which can make a transition much smoother. Rather than cutting over cold turkey, you can ease into a new interface. My Gmail account is still active, but it rarely sees any important email anymore. I’ve transitioned 99% of my email to other accounts on domains I control (like this one).

Changing the Backend

Gradually, I started using my blaise.ca email addresses instead of my Gmail account, until eventually I wasn’t getting much email through Gmail anymore. With my Gmail account configured in Thunderbird, it was easy to archive the contents on my computer. You can access Gmail labels as IMAP folders and just copy email from one account to another, and Thunderbird will even offer to synchronize a local copy of your Gmail account. I never used Gmail contacts, but an export and import to Thunderbird would get your data out (more on contacts another time). Lastly, I’m still monitoring my Gmail account via Thunderbird, but I could set an auto-reply and/or forwarder if I really wanted to force that last 1% over. I will probably do that eventually.

Other Considerations

There are a few other perks of a Gmail account that are pretty easy to get from libre alternatives:

• Hosted: Not everyone is going to run their own mail server, or have a friend or family member who does. But there are hosted, libre services, like riseup.net
• Storage space: in 2004, 1 GB of email was a huge game changer. Today, it’s not very hard to get that kind of storage space on a server for cheap.
• Chat: Google uses the open standard XMPP for its chat service. I run my own XMPP server, and there are public Jabber services like jabber.org. I’ve simply added my Gmail contacts to my blaise@blaise.ca XMPP account. More on chat another time.
• Conversations: The Conversations add-on provides Gmail-style conversations inside Thunderbird.
• Spam filtering: Gmail has a good track record on spam filtering, but SpamAssassin, ClamAV and a greylisting policy can produce great results on your own server nowadays. I don’t get any more spam to my blaise.ca inbox than I do to my Gmail inbox.
• Webmail: I love Thunderbird, but not everyone wants to use a desktop client, and you’re not always on your own computer. Roundcube is already a great free software webmail client, and it hasn’t even hit 1.0 yet. Many hosting providers already offer Roundcube to their customers.
• Mobile: With IMAP, my email is easily accessible from and synchronized between Thunderbird, Roundcube, and my mobile computer’s IMAP client.

Email is probably the easiest thing to degooglify. It can be a smooth, gradual transition, and there are lots of good alternatives, as well as benefits from leaving Gmail. Over the next while, I’ll share my ongoing efforts to degooglify other aspects of my online life.

Just as stand-up comedians are trained to be funny by observing which of their lines and expressions are greeted with laughter, so too are our thoughts online molded to conform to popular opinion by these buttons. A status update that is met with no likes (or a clever tweet that isn’t retweeted) becomes the equivalent of a joke met with silence. It must be rethought and rewritten. And so we don’t show our true selves online, but a mask designed to conform to the opinions of those around us.

Now, we rarely “show our true selves” offline either, but it’s not self-presentation that impairs authentic social interaction. It’s when automated, superficial interaction becomes the dominant mode of communication. A “Like” or +1 may be better for Facebook or Google than a comment — a simple binary value is easier for their algorithms to tally — but that’s not the kind of human interaction that drew me to social media.

There is so much more value in online social networking than the popularity contest, than merely pressing digital levers, like lab rats looking for pellets of social affirmation. Social technology can enable intimate and in-depth conversations where time, space and fate might otherwise not allow. Ambient awareness can maintain ties that distance and a loss of common circumstances might otherwise break. The ease of organizing can enable groups and communities to thrive where, offline, they might be dispersed. Yet, I’ve seen less of this in the evolution of Facebook and other social media, and more encouragement of the lab rat lever-pushing type interaction. Deep, rich, intimate and profound interactions — expressions of love, nostalgia, unity, shared memories, the meeting of minds, bonds of friendship or common experience — these are much harder for an algorithm to make use of than a binary +1 or “Like.”

Don’t let thumbs and plus ones be substituted for authentic social interaction online.

Google+ is Google itself. We’re extending it across all that we do — search, ads, Chrome, Android, Maps, YouTube — so that each of those services contributes to our understanding of who you are [emphasis added]

Maybe I’m naive or wrong, but it never seemed like the primary motivation behind Gmail was to sell more ads. It felt like an innovative email service that Google was able to monetize with relevant, contextual ads, not merely a means to improve Google’s ad business. But Google+ feels different. Google’s primary interest is to get access to more social information, not to create a better social networking service. Buzz or Google+ are just the means for Google to gather social data.

As Fred Wilson said with respect to Google+ as an identity service:

It begs the question of whom Google built this service for? You or them. And the answer to why you need to use your real name in the service is because they need you to.

Google is often pretty good at aligning its interests with that of its users. For example, the more useful their ads are to users, the better Google does. Or, the better your web browser is, the more you use the Internet, the more Google thrives. But with Google+, it feels like the desire for an identity data mining tool well precedes their desire to provide a useful social networking platform.

Google+ is not first and foremost “a place for friends” or a way for student life to find expression online. From Google’s hyper-engineer perspective, we are just things to be organized in the process of organization the world’s information. They’ve organized web sites, photos, maps, calendars, videos, books — now, they’re just organizing people.

Maybe Google+ is really no different from other Google services. Maybe I’m just different. I don’t want my relationships with other people, my identity, to be treated as ultimately just data to harvest, information to organize, inputs to a proprietary Google algorithm, a way to teach Google about me as some sort of data structure. Google+ seems to exist more for Google than it does for me.

I don’t want to be treated as just a thing to be organized.

Companies like Google have a unified vision. Look at Chrome or Android from Google’s perspective: the purpose of a mobile computer is simply to increase access to proprietary network services. These open source operating systems are designed to run proprietary applications and connect to proprietary network services. From Google’s perspective, mobile computing and network services go hand in hand — open source software is a way to increase the adoption of mobile computers complementing their proprietary network services. While Google’s goal is not software freedom, we should take note of how their strategy involves both mobile computing and network services together. We can’t effectively free one without freeing the other.

The free software movement needs a unified vision for network services and mobile computing. But what might that look like? StatusNet has an Android client, as does Libre.fm, but these are just more convenient ways to access network services from a mobile computer — not network services designed for mobile computing.

Look at the kinds of proprietary network services companies are developing for mobile computing. Google Latitude enables social location sharing, combining mobile positioning systems with online social networking. Last.fm’s mobile applications include some features for finding events based on your location. Google Goggles let’s you point the camera on your mobile computer at something and find information on that thing through Google’s search engine. Apple’s Facetime and Google+ Hangouts (not mobile quite yet…) are attempts to bring video chat to mobile and tablet computers. Social networking services like Facebook, Google+, and LinkedIn are focusing in on the mobile space as well.

What does free software have to offer? For location-based services, we have OpenStreetMap. StatusNet offers some location-sharing, but StatusNet for Android doesn’t seem to support this yet. Other than direct map programs, are there libre mobile applications making use of OpeenStreetMap? Could Libre.fm use mobile location data to highlight local free culture events? Regarding something like Google Goggles, are there many libre mobile applications can do something similar with, say, Wikipedia? (Mixare seems like a good example of this.) SIP and XMPP are great for video chat, but I’m not sure many users are aware of public XMPP or SIP services. How can we offer libre alternatives to Skype and Facetime on tablets? What kinds of opportunities are there for libre social networking services, like GNU Social or Diaspora, in mobile computing? What barriers are there to libre augmented reality or location-based services?

More importantly, beyond just emulating proprietary services, where might libre solutions offer new innovations? Where might free software have a distinct advantage, or something unique to offer? On desktop operating systems, the ability to easily distribute and repackage free software lent itself towards the development of package managers — applications that manage all your software installations and upgrades from one place, making it easy to find new software or keep your entire system up-to-date from one application. Meanwhile, on proprietary operating systems, you often have different update managers for each proprietary vendor. and upgrades often involve a purchase and don’t come as easily. Similarly, free software desktop operating systems provide much more desktop integration, as free software applications each contribute to a corpus of tools for the operating system, and distributions can customize software packages to make them work well together. On proprietary systems, each proprietary vendor tries to carve out their own space, and the distributor has limited options to customize software packages from other sources (or you end up with one company’s vision being ruthlessly enforced on any players in the ecosystem, as with Apple).

What kinds of advantages does free software have in developing a comprehensive approach to network services and mobile computing? Is it that libre solutions are often more distributed and less subject to surveillance or external control? That the user isn’t just a product for advertisers? I’m not sure yet myself, but this is something I think software freedom advocates need to consider more directly. Proprietary mobile computing offers convenient vertical integration with proprietary network services. What unique advantages does free software have at the intersection of mobile computing and network services?

Software freedom advocates need to think about network services and mobile computing together. If you take a look at the FreedomBox Foundation, for example, there are a lot of great ideas floating around about free network services… but there seems to be little mention of mobile computing. Yet, people are increasingly interacting with network services through their mobile and tablet computers, rather than just on their laptops. Bradley Kuhn offers another example. He never ceases to share excellent insights on software freedom for mobile computers and network services, but usually as two separate topics. For example, in a March 2010 post entitled Musings on Software Freedom for Mobile Devices, Kuhn writes:

We can take a page from Free Software history. From the early 1990s onward, fully free GNU/Linux systems succeeded as viable desktop and server systems because disparate groups of developers focused simultaneously on both operating systems and application software. We need that simultaneous diversity of improvement to actually compete with the fully proprietary alternatives, and to ensure that the “mostly FLOSS” systems of today are not the “barely FLOSS” systems of tomorrow. [emphasis added]

He’s absolutely right here, but network services form a third necessary category of software for success in the mobile space. In the same way that a libre desktop OS needs libre applications, a libre mobile OS needs libre network services. In a sense, to talk about software freedom on mobile computing without mentioning network services is like talking about building a free desktop operating system without mentioning the applications. And the interdependent relationship between mobile applications and network services is much more complex than application level software for a desktop OS.

It’s not just a question of which libre network services are missing, or which libre mobile applications are missing, but how libre mobile applications and network services can complement each other and work together. Success in one area depends on success in the other. We need to approach network services and mobile computing not just as two separate challenges, but as two parts of a whole, with a comprehensive vision and shared strategy. What might that look like?

Two of Canada’s big three telcos have recently appointed former cabinet ministers of the ruling party’s government to their respective boards. A few weeks ago, Bell appointed Jim Prentice, who was responsible for telecom policy and regulating companies like Bell while serving as Minister of Industry in 2007-2008. Then, while former cabinet minister Stockwell Day’s new “government relations” not-a-lobbying-firm has raised concerns about loopholes in lobbying laws, this past weekend Telus named Day to its board. (How long until Rogers aligns with industry standards and finds an ex-minister of their own?) OpenMedia.ca decried both appointments as examples of big telecom “cozying up to the government,” but journalist Peter Nowak argues it’s the system’s fault: “Lobbying is so pervasive and deeply integrated” into the system that the only way to deal with it seems to be to “fight fire with fire,” as even new wireless carriers have quickly learned — i.e. don’t hate the players, hate the game.

Neither Prentice nor Day will be lobbyists, but it seems obvious that their knowledge of government is being sought for the purposes of lobbying. In the broadband space, Bell has been butting heads with the government and regulators over issues like wholesale usage-based billing. In the wireless space, the next spectrum auction is approaching and incumbents want to avoid a repeat of the last auction, where 40% of the spectrum was reserved for new entrants and the government forced incumbents to offer roaming agreements — rules ironically set by Bell’s new board member, Jim Prentice.

Are these appointments examples of regulatory capture? It might appear that way. It’s certainly a case of telcos gearing up for a heavy round of lobbying that’s unlikely to favor consumers, but it’s hardly a case of blatant revolving doors. Day was not actually responsible for telecom policy, and Prentice was behind rules that angered incumbents. If the government favors incumbents in the next spectrum auction or backs down on wholesale usage-based billing, that would be a different story, but Canadian incumbents are scrambling because they’ve lost some big battles. This isn’t so much a cause for deep concern as it is a challenge to those who favor more competition in Canada to keep pressing the government to follow through on what it’s started.

Comments are on Techdirt.