Let's help these folks start podcasting
Radio stations should archive programs as podcasts for the same reason newspapers and magazines should save stories as Web pages. Especially since it's so darn easy. And help is so handy. (Hint, hint.)
This occured to me this morning when I was listening to KZSB/1290, the live news outlet of our local daily newspaper, the Santa Barbara News-Press. KZSB has no website, but it does stream live, using Windows Media Player. This brings up the Kaffeine Media Player in my Linux laptop, but ... nothing after that. Pretty annoying.
The same idea occurred to me again a few minutes ago, when I wished I could hear the Tabitha Soren interview of Ana Marie Cox, better known as Wonkette, which I had heard on a Commonwealth Club radio broadcast in the Bay Area earlier this week while I was driving down to Mashup Camp. (Here's one blog report on the 'cast.) So I looked up Commonwealth Club podcasts on Google. The top result wasn't useful; but the second result was Commonwealth Club Radio Program, an "unrecognized" file format that turns out to be http://audio.commonwealthclub.org/audio/podcast/weekly.xml. An RSS 2.0 file, for podcasts.
That was cool, but... there's nothing about podcasts or RSS on the Commonwealth Club site, though there are pointers to webcasts on KQED and KALW, San Francisco's two main public stations. Those pointers also include "Listen Now" links (like this one here, for Wonkette), which have other links that bring you RealAudio webcasts, rather than podcasts.
What's strange in both these cases is that podcasting is much easier than webcasting. You store files and point to them in an RSS feed. In KZSB's case, most of its broadcasts are programs. It would be easy for the station to archive those programs as .mp3 files, for downloading as podcasts. Storage is cheap these days. So, why not? As for the Commonwealth Club, same question.
So now I'm thinking it might just be a matter of tools. How about mashing up something combining podcasting with the open source Rivendell broadcast content management suite, which is written for Linux by Salem Radio Laboratories, and which I featured here a few weeks ago.
Stations with lots of programs, and not just music formats, would benefit enormously, methinks.
As for the Commonwealth Club, a simple RSS feed with pointers to extant archives would suffice.
As for RSS, there's some additional background in the form of the RSS roadmap and two pieces about it by Dave Winer, who has guided RSS development since he first made it stand for Really Simple Syndication.
The second of those pieces is about how much companies have invested in RSS over the years. Another angle on it is, how much have they saved?
I think we can save them a lot of money.
What do the rest of ya'll think?
Doc Searls is Senior Editor of Linux Journal
Practical Task Scheduling Deployment
July 20, 2016 12:00 pm CDT
One of the best things about the UNIX environment (aside from being stable and efficient) is the vast array of software tools available to help you do your job. Traditionally, a UNIX tool does only one thing, but does that one thing very well. For example, grep is very easy to use and can search vast amounts of data quickly. The find tool can find a particular file or files based on all kinds of criteria. It's pretty easy to string these tools together to build even more powerful tools, such as a tool that finds all of the .log files in the /home directory and searches each one for a particular entry. This erector-set mentality allows UNIX system administrators to seem to always have the right tool for the job.
Cron traditionally has been considered another such a tool for job scheduling, but is it enough? This webinar considers that very question. The first part builds on a previous Geek Guide, Beyond Cron, and briefly describes how to know when it might be time to consider upgrading your job scheduling infrastructure. The second part presents an actual planning and implementation framework.
Join Linux Journal's Mike Diehl and Pat Cameron of Help Systems.
Free to Linux Journal readers.Register Now!
- SUSE LLC's SUSE Manager
- My +1 Sword of Productivity
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Managing Linux Using Puppet
- Non-Linux FOSS: Caffeine!
- Doing for User Space What We Did for Kernel Space
- SuperTuxKart 0.9.2 Released
- Parsing an RSS News Feed with a Bash Script
- Google's SwiftShader Released
- Rogue Wave Software's Zend Server
With all the industry talk about the benefits of Linux on Power and all the performance advantages offered by its open architecture, you may be considering a move in that direction. If you are thinking about analytics, big data and cloud computing, you would be right to evaluate Power. The idea of using commodity x86 hardware and replacing it every three years is an outdated cost model. It doesn’t consider the total cost of ownership, and it doesn’t consider the advantage of real processing power, high-availability and multithreading like a demon.
This ebook takes a look at some of the practical applications of the Linux on Power platform and ways you might bring all the performance power of this open architecture to bear for your organization. There are no smoke and mirrors here—just hard, cold, empirical evidence provided by independent sources. I also consider some innovative ways Linux on Power will be used in the future.Get the Guide