Thoughts on “Preserve This Podcast”

I recently finished listening to the “Preserve This Podcast” podcast series, a five episode podcast on best practices for preserving the files associated with podcasts as well as the final podcast files themselves. I thought the series was excellent, which includes a zine/document supplementing the podcast and good advice on how to put the principles into practice. I also liked how they had some audio clips from conversations with Dave Winer, who created the technology base for podcasting through RSS.

I didn’t have any philosophical disagreements with the podcast until the last episode, when the subject of web hosting was discussed. The host, Molly Schwartz, talked about how many people have the expectation that their podcast show should live forever, and didn’t realize that if they don’t pay for a hosting service (like Libsyn, etc.), or host it themselves on a website, that their files would disappear. How can people in 2019 still have this expectation? (see Site deaths) The idea that someone can create a web asset (podcast, website, video, whatever) for zero cost and still have complete control is ridiculous! I also think that the image of a person producing a podcast as someone who does not have much technical ability is misleading. If you are not just using your phone as a voice recorder, and are recording and editing audio and handling sound equipment, you have to have some technical ability. To emphasize the need to spend effort to make sure that data is not lost, but then put the idea out there that it is too much work to do self-hosting or create a RSS feed is inconsistent at best, trending to stupid at worst. You can only get something for nothing for so long, and you can’t expect to have the functionality of paid services on a free basis.

I also thought that the idea in episode 5 of “having to figure out what to do about PreserveThisPodcast.org” was ludicrous! With all the planning of this series and archiving experts working on the project, how could they have not planned to keep this information beyond the end of the grant funding? Why didn’t the organization who got the grant (Metro New York Library Council) take responsibility for keeping this available? At a minimum, it seems like a terrible plot device to motivate/manipulate podcasters into preserving their work.

Don’t get me wrong on my intent – I love that this podcast was created. As a result, I am starting to think about how to preserve my own web content. The thing that sticks out as inconsistent is perpetuating the idea of expecting something for nothing (free hosting, etc). If that is a person’s expectation when they create something on the web, that person should not shed any tears if it disappears.

Node.js resources and other things

Freshman.tech – How to build your first website with Express and Pug

Codeburst.io – How to build a Node Weather App with 16 Lines of Code (Part 1)

Codeburst.io – Build a Weather Website in 30 minutes with Node, Express, and Open Weather

Codeburst.io – Three courses for learning Node.io

Codeburst.io – Learn Javascript by building a game

Codeburst.io – AI in the browser

Infinite Red Academy – AI Demystified – free 5 day course

 

Podcast Drama Links

I was thinking of creating a dramatic podcast, but have stalled out, so I am collecting these links somewhere so I can get back to them…

John Fleming  – How to Structure and Maintain A TV Soap Opera like Coronation Street

Our Pastimes  – How to Create A Soap Opera

Our Pastimes –  How to Write a Soap Opera Script

Buzzsprout   – Audacity Tutorial for Podcasts

Radio Drama Revival  – Creating A Radio Drama

Ruyasonic  – Tony Palermo’s Radio Drama Resources

National Audio Theater Festivals:   Well Tempered Audio Dramatist

MakeUseOf  – Five Amazing Sounds You Can Make with Audacity Sound Editor

The economics of open source development

Recently, I watched a video from JSConf.EU by CJ Silverio on the economics of open source development. She recounted the story of the start of Node.js and the Node Package Manager (NPM), and how the creator of Node.js gave the source code to the Node Foundation, but the creator of Node Package Manager retained all rights and created a company to continue development of NPM and took VC money. The video is a good watch, with lots of excellent examples on how business get value from open source software, but don’t (in general) pay anything for the software (either development or support costs). My additions to this video: (1) people who want to make money from the software they create should think hard about how they are going to do that before they start releasing that software, and (2) people who use open source for profit should invest some of their profits in keeping the wheels of progress turning (pay the developers something), otherwise the supply may dry up.

Got problems with Windows 10 sound/app focus? It might be a stuck key…

Recently, I had two problems with my Windows 10 computer at work. The first one was an inability to control the volume of the computer during Google Hangouts. The volume would always go to 100%, and I could not reduce it. Eventually, I figured out that there was a function key on my keyboard for increasing the volume, and it was pressed down and stuck. After fiddling with it for a few seconds, I managed to loosen it, and was able to control my PC volume again.

The second problem was that a Radeon Graphics setting pop-up started popping up. At first, I thought it was a computer problem again, but then I started searching and found that this particular pop-up is tied to Alt-R. Sure enough, when I looked at my keyboard, the left Alt key was stuck, and after more fiddling, I was able to type the letter “r” without bringing up this pop-up.

Moral: Look at your keyboard when weird things start happening on your PC. If they persist, maybe get a new keyboard…..

Jeremy Keith: Building the World Wide Web in Five Days – recreating the original CERN  web browser using modern  web technology.

More news on Boeing MCAS issues

The New Republic features an article by Maureen Tkacik on the MCAS issues for the Boeing 737-MAX. This one references many of the previous articles from other publications on topics like the outsourcing of software development and the use of DERs on the program. To me, this article breaks new ground in examining the management culture of Boeing, how things changed after Boeing purchased McDonnell Douglas, and how this affected the 737-MAX development process. A recurring theme from previous articles is how the pursuit of profit and “making your numbers” can result in safety impacts and, in this case, loss of life.