Hi Christoph,
While you are entitled to your opinions, I do need to correct you on a
few factual inaccuracies in your email.
Regarding "/If Ken's analysis published recently [1] is anything to go
by, we are one of HPR's most popular podcasts/"
What I didn't include in that analysis was the 170 additional
subscribers that you get to your feed. As no one else promote their own
RSS feed, we need to subtract that from the download figures to be fair
to the other shows. The corrected numbers are below.
First day of release numbers
*hpr3609 2022-06-02 583 (was 753)*
hpr3608 2022-06-01 726
hpr3607 2022-05-31 722
hpr3606 2022-05-30 732
hpr3605 2022-05-27 774
hpr3604 2022-05-26 748
hpr3603 2022-05-25 756
hpr3602 2022-05-24 766
hpr3601 2022-05-23 753
Regarding "/Youtube channel republishing the audio content and giving
HPR credit [2]/"
I can't see that they are assigning credit, or even flagging the content
as Creative Commons. Unless you mean in the audio stream, which is
created by HPR ?
$ yt-dlp.sh --dump-json
https://www.youtube.com/channel/UC1j_uaAbB3magzPs4Z0Y-mg | jq '.' | sed
-e 's#hackerpublicradio.org/eps.php##g' -e 's/All about Hacker Public
Radio//g' -e 's/Hacker Public Radio in general and Ken Fallon//g' | grep
-Ei "Hacker|Creative" | wc -l
*0*
Regarding "/David speaks about HPR having reached out to them trying to
move them over to HPR./"
This statement is not correct and I would appreciate it if you could
contact David and correct his understanding. Fortunately the entire
conversation is available publicly on twitter
https://twitter.com/ken_fallon/status/1539598341096480770
"@ken_fallon to @tkglaser and @nosqlgeek Jun 22: Have you ever
considered releasing your content as Creative Commons ? We promote shows
both on @HPR and also on https://freeculturepodcasts.org. For both we
would need to have your RSS feed or you don't qualify as a "Podcast".
--
Regards,
Ken Fallon (PA7KEN,G5KEN)
https://kenfallon.com
https://hackerpublicradio.org/hosts/ken_fallon
2022-08-19 07: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
_______________________________________________
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
