On 8/12/22 03:27, Ken Fallon wrote:
On 2022-08-11 22:16, Ken Fallon wrote:
https://hackerpublicradio.org/eps.php?id=3658

So, let me clarify the question to "*Should* we be a podcast or podcast hosting 
platform ".


I feel we should be a podcast, and should maintain the same policy towards accepting and airing 
shows from other podcasts that we currently have. As long as they meet the requirements of posting 
on HPR--i.e. shows of 'any topic that "are of interest to Hackers"', they post on the 
accepted schedule (currently not more than once every two weeks, if I am not mistaken), their show 
can be posted under the same CC license that HPR uses, and they are generally not a disruptive 
member of the community. The gray area is when a podcast is wholly hosted through HPR versus 
playing an episode from one which is hosted elsewhere. I think we ask the host to give a brief 
summary of any external podcast being aired on HPR at the start of the show, before including the 
external material. For podcasts which air regularly or are wholly hosted on HPR, the summary isn't 
requested. So far, I don't feel like anyone "hosting their podcast" on HPR has abused the 
spirit of posting to HPR.

For me the connotation of a podcast hosting platform means either some kind of 
monetization going on in the background, or some kind of sharing of resources 
between the podcasts, and I am not sure how that would look and work as HPR is 
currently structured. I doubt Josh and AnHonestHost.net would mind some extra 
capital coming in to offset the HPR resources they graciously give to HPR, but 
it would be a completely new dynamic that would need to be worked out. If we 
went that route, I see a Hacker Public Network (HPN) or Hacker Public 
Broadcasting Network (HPBN) to which HPR would then become part of that 
network, but HPR would remain basically the same.

Cheers,

Roan

_______________________________________________
Hpr mailing list
[email protected]
http://hackerpublicradio.org/mailman/listinfo/hpr_hackerpublicradio.org

Reply via email to