The Problem

It’s not really a problem. Today most everything on the web has moved from http to https. This is generally a good thing. However, in the case of icecast, all of the services that I could find for pay-as-you-go internet radio services don’t offer icecast+https services to customers.

Ok, wait Mike. Why do I need https on icecast?

Normally, this isn’t an issue. You can (still) happily click through all of the ‘safety’ warnings that web browsers show you when you connect to an http web server. You accept the risks and move on. It’s only an issue if you’re trying to connect to an endpoint service that will refer to your icecast stream point to play your tream THROUGH it’s https web site.

Last Revised: January 2, 2022 22:45

Why

Discussion between Adam and Dave in Podcasting 2.0 Board Meeting #68 on how cool it might be to see dedicated applications on Roku app, for example, in front of a services dedicated to music, or movies, or documentaries, etc. with unique and familiar experiences/interfaces to those types of media, taking full advantage of the Podcasting 2.0 namespace and index.

Then I got to thinking, what excatly is involved in developing a Roku app, and what is that ecosystem like?