Sounds good thanks for the explanation and all you do at hpr. brian-in -ohio
On Thursday, September 18, 2025, Ken Fallon <[email protected]> wrote: > Hi Carl/list, > > Actually that is a very good point. We've been in pretty stressful > situations in the past waiting for a decision to come through. It's also > normal to delay posting shows for various technical/policy reasons, so it's > good to have this formalized. > How about a more general statement like this: > > "The janitors may place content on hold while communication with the host > or mail list is ongoing." > > Ken. > > > On 2025-09-15 18:40, Carl D Hamann via Hpr wrote: > > This looks good to me. I also wouldn't be opposed to an addendum to the > effect of "in the case of a time sensitive issue, the janitor may take > whatever temporary action is necessary to protect HPR and their own > liability while communication with the host or mail list is pending" > > > On 2025-09-15 18:20, Ken Fallon via Hpr wrote: > > TL;DR: Policy change. > > "*If there are any shows that are on the site which you feel harm HPR > <https://lists.hackerpublicradio.com/pipermail/hpr/2022-June/004492.html>, > first see if a response episode > <https://lists.hackerpublicradio.com/pipermail/hpr/2021-September/004250.html> > is sufficient to address the grievance. If not then please bring it to the > attention of the janitors at hpr, and we will see if the concerns are > grounded based on the same criteria as if the show was been posted today.* > " > > Hi Brian, > > To answer how this effects HPR > > 1. 181 listeners can no longer hear this episode. > 2. We can no longer expect to go un-noticed in our little back water > on the Internet, as the fact we are on Spotify means that all our shows are > been scanned. > 3. We are now knowingly in violation of the DMCA, and can also no > longer use the "safe harbor > <https://lists.hackerpublicradio.com/pipermail/hpr/2019-May/003673.html>" > defense. > > So this is *not* a discussion about should we or should we not remove the > infringing copyright music - only the domain holders stankdawg and myself > get a say in that: "And for the record... no one else can voluntarily > accept responsibility. It falls back to me as site owner no matter what. > <https://lists.hackerpublicradio.com/pipermail/hpr/2019-May/003692.html> > ". After consulting with my legal team, surprise, surprise, the response > was to remove the offending content. > > The show itself violates our current policies > <http://hackerpublicradio.org/stuff_you_need_to_know.php#permission> > ""Never include content, for example music, in your show that you do not > have permission to redistribute." however that policy came in 10 years > after that show was posted. If it were posted now, we would reject it. > > This discussion is about **how to deal with legacy issues in older shows* > *. > > Issues may be identified by the Janitors noticing it during posting, the > QA team hearing it on the Future Feed > <https://hackerpublicradio.org/syndication.html#Future_feed>, or the > general public when it is posted to the main feed. > > This topic came up in a recent mail-list discussion, and in reply to > Steve, I wrote "*if there are any shows that are on the site which you > feel harm HPR > <https://lists.hackerpublicradio.com/pipermail/hpr/2022-June/004492.html>, > first see if a response episode > <https://lists.hackerpublicradio.com/pipermail/hpr/2021-September/004250.html> > is sufficient to address the grievance. If not then please bring it to the > attention of the janitors at hpr, and we will see if the concerns are > grounded based on the same criteria as if the show was been posted today.* > " > > For the record "*The normal procedure > <https://lists.hackerpublicradio.com/pipermail/hpr/2025-September/004910.html> > is that when the Janitors notice an issue, they will contact the host, > explaining what the issue is and listing a link to the policy. It is then > up to the host and only the host to decide what to do. If the host > disagrees, then they or the Janitors will bring it to the attention of the > Mail List*". > > So expect more discussion on what to do with hpr0492 later, but for now is > the approach outlined above acceptable when dealing with complaints ? > Links. > > - https://lists.hackerpublicradio.com/pipermail/hpr/2019-May/003673. > html > - https://lists.hackerpublicradio.com/pipermail/hpr/2019-May/003683. > html > - https://lists.hackerpublicradio.com/pipermail/hpr/2019-May/003684. > html > - https://lists.hackerpublicradio.com/pipermail/hpr/2019-May/003692. > html > - http://hackerpublicradio.org/stuff_you_need_to_know.php#permission > - https://lists.hackerpublicradio.com/pipermail/hpr/2022-June/ > 004492.html > - https://lists.hackerpublicradio.com/pipermail/hpr/2021-September/ > 004250.html > - https://lists.hackerpublicradio.com/pipermail/hpr/2025-September/ > 004910.html > - https://hackerpublicradio.org/syndication.html#Future_feed > > > -- > Regards, > > Ken Fallon > (PA7KEN,G5KEN)https://kenfallon.comhttps://hackerpublicradio.org/hosts/ken_fallon > > On 2025-09-15 14:17, Brian K Navarette wrote: > > I'm wondering, does a show being removed from Spotify actually effect HPR? > Should we care or does responding to them give them (spotify and others) > some sense of control over us? > brian-in-ohio > > >
_______________________________________________ Hpr mailing list [email protected] https://lists.hackerpublicradio.com/mailman/listinfo/hpr
