Is government open source code we can patch?
That's the question raised by Britt Blaser in “Oh, if only government went in for an open source make-over…”. It's also one suggested indirectly by Phil Hughes in Our Internet.
Democracy is by nature "our government". The open source twist on that we put it together and can hack improvements to it. Think of elected officials as committers and maintainers and you start go get the idea.
The analogy isn't perfect, because by nature open source code is purely practical: it has to work. While government often does not. All government is buggy. In the worst cases it crashes outright and is replaced or supplemented by corrupt alternatives.
But government and governance are not the same things. A lot of governance takes place outside of government, in society. What Britt's suggesting is an open source model of governance, facilitated by code, that directly engages citizens in governance. What Phil's suggesting is building or rebuilding the Internet on the model Bob Frankston suggests in my Interview with him in the current issue of Linux Journal. That model is one not dependent on mainframe-like proprietary networks by phone and cable carriers that add the Internet as "a service", but instead depends on individuals and small groups connecting to each other, and then out to the world by any means available, which might or might not include those carriers.
I have long believed that there is far more business, especially for carriers, to be found in bets on abundance than in bets on scarcity. In other words, there are non-monopolistic advantages to incumbency that far exceed the monopolistic ones.
I bring this up for two reasons.
First, individual and community-built networks will eventually encounter big carriers that own backbones as well as "last mile" CFR (copper, fiber and radios). When that happens, we need to be able to show business as well as social advantages of wide-openness and ubiquitous connectivity.
Second, those carriers are part of what Bob calls the Regulatorium -- a combination of regulated enterprise and governance in which the latter tends to control the former. We can work around it up to a point. Or we can hack it.
We did it with code. Now let's do it with connections.
Doc Searls is Senior Editor of Linux Journal
Fast/Flexible Linux OS Recovery
On Demand Now
In this live one-hour webinar, learn how to enhance your existing backup strategies for complete disaster recovery preparedness using Storix System Backup Administrator (SBAdmin), a highly flexible full-system recovery solution for UNIX and Linux systems.
Join Linux Journal's Shawn Powers and David Huffman, President/CEO, Storix, Inc.
Free to Linux Journal readers.Register Now!
- Devuan Beta Release
- May 2016 Issue of Linux Journal
- EnterpriseDB's EDB Postgres Advanced Server and EDB Postgres Enterprise Manager
- The US Government and Open-Source Software
- The Humble Hacker?
- The Death of RoboVM
- BitTorrent Inc.'s Sync
- Open-Source Project Secretly Funded by CIA
- New Container Image Standard Promises More Portable Apps
- AdaCore's SPARK Pro
In modern computer systems, privacy and security are mandatory. However, connections from the outside over public networks automatically imply risks. One easily available solution to avoid eavesdroppers’ attempts is SSH. But, its wide adoption during the past 21 years has made it a target for attackers, so hardening your system properly is a must.
Additionally, in highly regulated markets, you must comply with specific operational requirements, proving that you conform to standards and even that you have included new mandatory authentication methods, such as two-factor authentication. In this ebook, I discuss SSH and how to configure and manage it to guarantee that your network is safe, your data is secure and that you comply with relevant regulations.Get the Guide