It's good because with this, no one will be able to question whether
listeners are your own or HPR's, making any claims of success
irrefutable. Perhaps you're right that HPR has tended to shy away from
success in these 17 years.

Jokes aside, I do enjoy your shows and appreciate your work to feature
guests we want to hear from, so I look forward to subscribing to your
feed and continuing to listen.

Now for the things pertaining to HPR that we all have talked about here:
I think considering how easy it is to have your own CC-licensed podcast
by hosting it on the IA, and how well such a prospective podcaster can
be expected to host an rss feed to point to the audio files, it seems
like the only real good reason to slot one's podcast into the HPR feed
is to access HPR listeners. Then the question for the community should
be: do you want to sample new podcasts within the HPR feed? For me the
answer would tend to be no, because again, I think we should always keep
the focus on attracting new contributors, it's what sets HPR apart, and
it's the principle that should guide every decision, without exception.
It's the diversity of voices and experiences and the people who wouldn't
otherwise be a podcaster. If someone can argue that this would help
convince listeners to become contributors, then we should talk about it.

For me, a new podcast host or hosts wanting to gain subscribers can send
a regular HPR show and let us know that if we like their vibe, they've
started their own podcast we can subscribe to, as Klaatu has done. Those
who like it will follow.

-dnt

On 8/19/22 00:24, Christoph Zimmermann wrote:
> Dear community,
>
> First of all, the Inlaws would like to thank the HPR community for their 
> feedback over the
> years and especially the last few days.
>
> Ken is of course right in pointing out the bootstrapping argument in 
> Wednesday's reply to
> Yannick's mail (although we never really defined how long this 
> "bootstrapping" period
> would last).
>
> In addition to the above, the assessment of the situation in our mail from 
> Wednesday
> (republished in Ken's mail): the situation from an Inlaws' perspective hasn't 
> changed
> since we published our first episode in early 2020. The content is published 
> exclusively
> on HPR and our RSS feed points to HPR *only*. Having said that I cannot get 
> rid of that
> sinking feeling that HPR and its community shy away from success. If Ken's 
> analysis
> published recently [1] is anything to go by, we are one of HPR's most popular 
> podcasts
> which regularly publishes content. In addition to the fact that we are 
> syndicated left,
> right and center without any involvement of our own (as we found out a while 
> ago, there's,
> for example, a Youtube channel republishing the audio content  and giving HPR 
> credit [2]).
>
> But let's take a look at the bigger picture. If our experience never mind the 
> feedback we
> are getting through official and other channels are anything to go by,
> the vast majority of our listeners couldn't care less where they get their 
> episodes from.
> They heard or read about the podcast, search for the RSS feed, subscribe to 
> it and if they
> like what they hear downloaded from a server, they stick with us.
>
> End of story.
>
> In this light, any discussion about wording, podcasts vs hosting platforms, 
> etc. is
> academic and thus irrelevant for these listeners (playing devil's advocate 
> for the above
> of course never mind ignoring bylaws, etc. :-).
>
> Of course, bylaws are bylaws and feeling that we may have overstayed our 
> welcome, we are
> happy to move the content elsewhere (probably archive.org as suggested by 
> Ken) which also
> has the side effect of reducing the technical debt of the corresponding 
> automation
> workflow significantly. But do so with a bitter-sweet feeling as we do 
> believe in the true
> spirit of FLOSS communities and their welcoming / inclusive attitude, thus 
> having made
> every effort to promote HPR and its cause as part of the episodes and 
> elsewhere. Which is
> in stark contrast to the wording of some of the comments posted to the HPR ML 
> over the
> last couple days.
>
> On an interesting side node: HPR seems to be actively soliciting podcasts 
> from other
> platforms if, for example, the case of the Grumpy Old Coders is anything to 
> go by. In its
> most recent episode [3], David speaks about HPR having reached out to them 
> trying to move
> them over to HPR. Given the fact that this format is hosted on a proprietary 
> platform
> (Soundcloud) with their format exhibiting far more restrictive aspects (for 
> example, they
> publish their content under an "All Rights Reserved" license in contrast to 
> CC-BY-SA as
> preferred by HPR) and knowing David (the producer of this format) quite well 
> as he has
> been one of my colleagues for the last years, it would surprise me if such an 
> endeavour
> would prove to be successful.
>
> Never mind the above, the Inlaws would like to thank HPR for having us for 
> the last 2.5
> years and wish this platform (our words :-) every possible success for the 
> future. But it
> may help in order to avoid similar incidents in the future to be clearer 
> about syndication
> never mind what the difference is between a show, a series and a podcast as 
> far as HPR is
> concerned (as the wording in [4] is somewhat terse)
>
>        Cheers, The Inlaws
>
> [1] http://hackerpublicradio.org/eps.php?id=3648
> [2] https://www.youtube.com/channel/UC1j_uaAbB3magzPs4Z0Y-mg
> [3] https://soundcloud.com/user-498377588/grumpy-old-coders-ep18-rollercaster
> [4] https://hackerpublicradio.org/stuff_you_need_to_know.php#syndication
> --
> This email account is monitored seven days a week.
> _______________________________________________
> Hpr mailing list
> [email protected]
> http://hackerpublicradio.org/mailman/listinfo/hpr_hackerpublicradio.org


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

Reply via email to