What's Next for Open Source and Public Media?
Open Source has won. We've moved into Gandhicon 4. Now what? That's the question that occurred to me yesterday, while sitting in the audience of a tech session at Public Media 2008 in Los Angeles — the big annual conference for what most of us still call public broadcasting.
I sat there hearing panelists tell story after story about what stations can do with piles of open code, tools and standards. In cases where the nature or provenance of recommended code was in doubt, questions from the audience went, "Is the source code for that available?" or "Is that open code, or just an open service?"
This wasn't the only place I've seen this. In one business category after another, it's becoming clearer that we've passed the tipping point. Open Source is no longer just an option, no longer needs to justify itself. It's the baseline.
At one conceptual level up, I'll be on a panel today called Technology and Trends: What's Around the Bend? To prep for that, I thought I'd share are a few of my preliminary ideas.
- It's not a fight, but listeners and viewers will win anyway. They have far more choice about what they hear and watch. They can produce media as well as consume it. And they have the means to take the lead not only in the choice and supply of media and content, but in participation with stations, networks, program producers and everybody else who plays a role in the system. The market for public media will finally become, truly, conversational and participatory.
- There will be a new business model for public media, based on the ability of listeners and viewers to pay as much as they want, for whatever they want, whenever they want, wherever they want. We'll call this new model VRM, for Vendor Relationship Management. It will supplement rather than supplant the old fund-raising systems. It will enrich and deepen the relationships between the consumers and producers of media, by working on terms provided by both sides, and not just by the supply side alone. This will not only increase the percentage of listeners and viewers paying for public media, but a new and vital source of funding for non-broadcast media — such as podcasts.
- VRM will reform CRM. Once we have tools that that will allow any of us voluntarily to pay for music and everything else we call "media" — and beyond that to relate with suppliers on terms that work for us as well as for them — CRM (Customer Relationship Management) systems will cease to be one-way marketing vehicles and start to become two-way means by which real relationships between individuals and institutions are supported.
- Membership will mean more than schwag and promotion payoffs. We will cease to conflate transaction with relationship, and start relating to listeners and viewers in ways that conform to the shape of their wants, need an habits as well as ours. That means, if listeners care more about This American Life than about our stations, we help with that, rather than insist that listeners relate only to stations and silo'd CRM systems.
- The Intention Economy will happen first with public media. This is the economy that will grow around customers' and users' actual intentions — rather than guesswork about those intentions, or efforts to capture or drive people's attention. As a result, the advertising boom will come to an end, simply because the supply side will know more about what the demand side wants, and will have better ways of relating to it. Advertising won't go away, and never will. But wasting money time and money with guesswork about what people might want will fade as a value system, simply because a system that starts the actual intentions of users and customers will be in place.
- Cell phones will be the new radios and televisions. This will start to happen in a big way the minute Apple opens its iPhones to independent developers of native applications (rather than just ones that run in a browser). Then it will get a huge boost when carriers start selling open phones developed on Android, OpenMoko, Maemo, Trolltech and other platforms — all Linux-based, by the way. (Nokia buying TrollTech is a huge harbinger here.) The carriers will resist this development at first, and complain about how much bandwidth gets used, but they'll deal with it because demand will drive supply, and openness will outperform the closed alternatives.
- Websites will become as inadequate as transmitters. That is, both will remain necessary but insufficient means for reaching listeners and viewers, and for relating to them. "Live Web" methods such as streaming, file sharing, social networking and "rivers of news" will all play roles as well.
- Archives will be the ultimate killer kontent. Stations and networks will come to value not only their own archives, but will work to make those archives as easy as possible to find, consume and otherwise use — and to open CRM systems for VRM tools to make it as easy as possible for listeners and viewers to voluntarily pay for the privilege. Bigger inventory, bigger income.
- The end of analog terrestrial television will be a big mess and a wake-up call in more ways than we can name. The loss of analog TV's familiar channels, and in countless cases their signals as well, will go beyond annoying millions of people who never asked for DTV, and will barely understand it. In the long run it will help break everybody free from the ancient model of broadcasting as a system defined by limits in time and distance. No longer will everything need to be "live" — and constantly to hog bit paths to listeners and viewers who are tuned in to something else. No longer will local be a strictly geographical concept.
- Brands and reputations will matter more than ever. Familiar call letters, program names, personalities and institutions will have countless new ways to leverage their incumbent advantages, and to relate to their listeners and viewers, without both real and conceptual constraints imposed by transmitters and entailments such as "range". What will matter most about those names and reputations, however, will not be limited to their familiarity. Instead they will be enriched or impoverished by the degrees to which they participate in a marketplace sustained by real relationships, and not just by marketing that goes by that name.
So those are my first ten. Add your own below, and feel free to correct any or all of the above.
Doc Searls is Senior Editor of Linux Journal
Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.
Sponsored by AMD
Built-in forensics, incident response, and security with Red Hat Enterprise Linux 6
Every security policy provides guidance and requirements for ensuring adequate protection of information and data, as well as high-level technical and administrative security requirements for a system in a given environment. Traditionally, providing security for a system focuses on the confidentiality of the information on it. However, protecting the data integrity and system and data availability is just as important. For example, when processing United States intelligence information, there are three attributes that require protection: confidentiality, integrity, and availability.
Learn more about catching the bad guy in this free white paper.
Sponsored by DLT Solutions
| Designing Electronics with Linux | May 22, 2013 |
| Dynamic DNS—an Object Lesson in Problem Solving | May 21, 2013 |
| Using Salt Stack and Vagrant for Drupal Development | May 20, 2013 |
| Making Linux and Android Get Along (It's Not as Hard as It Sounds) | May 16, 2013 |
| Drupal Is a Framework: Why Everyone Needs to Understand This | May 15, 2013 |
| Home, My Backup Data Center | May 13, 2013 |
- Designing Electronics with Linux
- New Products
- Linux Systems Administrator
- Senior Perl Developer
- Technical Support Rep
- UX Designer
- Making Linux and Android Get Along (It's Not as Hard as It Sounds)
- Dynamic DNS—an Object Lesson in Problem Solving
- Web & UI Developer (JavaScript & j Query)
- Using Salt Stack and Vagrant for Drupal Development
- Reply to comment | Linux Journal
6 hours 26 min ago - Dynamic DNS
7 hours 14 sec ago - Reply to comment | Linux Journal
7 hours 58 min ago - Reply to comment | Linux Journal
8 hours 49 min ago - Not free anymore
12 hours 50 min ago - Great
16 hours 38 min ago - Reply to comment | Linux Journal
16 hours 46 min ago - Understanding the Linux Kernel
19 hours 46 sec ago - General
21 hours 30 min ago - Kernel Problem
1 day 7 hours ago
Enter to Win an Adafruit Pi Cobbler Breakout Kit for Raspberry Pi

It's Raspberry Pi month at Linux Journal. Each week in May, Adafruit will be giving away a Pi-related prize to a lucky, randomly drawn LJ reader. Winners will be announced weekly.
Fill out the fields below to enter to win this week's prize-- a Pi Cobbler Breakout Kit for Raspberry Pi.
Congratulations to our winners so far:
- 5-8-13, Pi Starter Pack: Jack Davis
- 5-15-13, Pi Model B 512MB RAM: Patrick Dunn
- 5-21-13, Prototyping Pi Plate Kit: Philip Kirby
- Next winner announced on 5-27-13!
Featured Jobs
| Linux Systems Administrator | Houston and Austin, Texas | Host Gator |
| Senior Perl Developer | Austin, Texas | Host Gator |
| Technical Support Rep | Houston and Austin, Texas | Host Gator |
| UX Designer | Austin, Texas | Host Gator |
| Web & UI Developer (JavaScript & j Query) | Austin, Texas | Host Gator |
Free Webinar: Hadoop
How to Build an Optimal Hadoop Cluster to Store and Maintain Unlimited Amounts of Data Using Microservers
Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.
Some of key questions to be discussed are:
- What is the “typical” Hadoop cluster and what should be installed on the different machine types?
- Why should you consider the typical workload patterns when making your hardware decisions?
- Are all microservers created equal for Hadoop deployments?
- How do I plan for expansion if I require more compute, memory, storage or networking?



Comments
toplum
Hi there, I found your blog via Google while searching and your post looks very interesting for me
Archives will be the
Archives will be the ultimate killer kontent. Stations and networks will come to value not only their own archives, but will work to make those archives as easy as possible to find, consume and otherwise use — and to open CRM systems for VRM tools to make it as easy as possible !
Totally true !
What is DTV? (something
What is DTV? (something tells me it's a dumb question:D)
CDA - Customer Driven Advertising
As well as VRM, here's another TLA to conjure with. CDA or Customer Driven Advertising. This takes Publisher Driven Advertising one stage further.
I would love to have an RSS/Atom feed of adverts specifically targeted at me. I leave enough traces round the web at places like Amazon, eBay, Last.FM, the gadget sites, doubleclick and so on that an advertising agency should be able to come up with a very tightly targeted feed. And I want to help refine it with Love,Skip,Ban buttons on every ad.
CDA
Well, CDA means many different things, including Communications Decency Act, a lame an lamented (and struck down) law that failed to restrict speech on the Net a decade ago.
Still, I get your point. What I'm wondering is why Google isn't doing this now. Or, isn't this what they think they're doing? Or trying to do?
Doc Searls is Senior Editor of Linux Journal
the role of widgets in the death of the url
Re: "Websites will become as inadequate as transmitters."
Have to agree. I think widgets which do the following illustrate how easy it is to think of the death of the url:
1. Speak in an authentic voice (close the gap between creation and marketing)
2. Lose the TV envy (think relevance over quality)
3. Give people tools to make it their own (that which we create, we embrace)
4. Don't bother with urls, links or 'brand messages'. (We don't do spin) If people intend to find they will search.