Update branding.md

Suggestions from murph's talk at olf

README.md

@@ -18,10 +18,18 @@ Where we can link to other free culture sites that provide usefull services.
 - Requested Topics
 Where we can track topics that have been requested, and link to shows that addressed them.
 
+## HPR Policies
+
+[See Policies](https://repo.anhonesthost.net/HPR/hpr_documentation/src/branch/main/policies.md)
+
 ## Podcatcher and Podcasting Platform Compatibility
 
 [See Podcatchers](https://repo.anhonesthost.net/HPR/hpr_documentation/src/branch/main/podcatchers)
 
+## Branding Into and Outro
+
+[See Branding](https://repo.anhonesthost.net/HPR/hpr_documentation/src/branch/main/branding.md)
+
 ## Workflow
 
 - [Uploading a Show](https://repo.anhonesthost.net/HPR/hpr_documentation/src/branch/main/workflow/uploading_a_show.md) - the processes involved in getting your show to the HPR servers.

branding.md

@@ -0,0 +1,142 @@
+# HPR Branding
+
+## The Intro
+
+### Duration
+
+It will always be 30 seconds long and in some edge cases may be slightly longer.
+The following table will help put that into context.
+It gives the percentage of the show the intro takes related to the length of the shows.
+
+      1.7% of an average show (29 minutes 30 seconds)
+      0.1% of our longest show (7 hours 27 minutes)
+    187.5% of our shortest show (16 seconds)
+
+### Breakdown
+
+### Generation
+
+The intro is generated by the [process\_episode.bash](https://repo.anhonesthost.net/HPR/hpr-tools/src/branch/main/workflow/process_episode.bash#L1388-L1391) script and uses the [say.php](https://repo.anhonesthost.net/HPR/hpr_hub/src/branch/main/cms/say.php) file to generate the data.
+
+The text is [created](https://repo.anhonesthost.net/HPR/hpr-tools/src/branch/main/workflow/process_episode.bash#L1427) using [piper test to speech](https://github.com/rhasspy/piper).
+It was previously created using [espeak](https://espeak.sourceforge.net/), and we are open to [suggestions](https://repo.anhonesthost.net/HPR/hpr_hub/issues/new) on how to improve it.
+
+The text is played over the HPR Theme Music
+
+### Theme Music Credits
+
+The background is an arrangement by [Maestraccio](https://repo.anhonesthost.net/HPR/hpr_website/src/branch/main/www/theme/intro-ak-Maestraccio-cc-by-4.0.mp3) which is released under the [Creative Commons Attribution-ShareAlike 4.0 International (CC BY-SA 4.0)](https://creativecommons.org/licenses/by-sa/4.0/) license, of the [HPR Theme](), composed by [slick0](https://hackerpublicradio.org/correspondents/0042.html) which has [No Copyright](https://creativecommons.org/publicdomain/zero/1.0/) applied.
+
+### Message
+
+To effectively communicate an event it's important to convey the answers to **Who?**, **What?**, **When?**, **Where?**, and **Why?**
+
+> The Five Ws is a checklist used in journalism to ensure that the lead contains all the essential points of a story. As far back as 1913, reporters were taught that the lead should answer these questions about the situation being reported.
+
+[https://en.wikipedia.org/wiki/Five_Ws](https://en.wikipedia.org/wiki/Five_Ws)
+
+
+#### What?, When?, Where?
+
+The first sentence is always **This is Hacker Public Radio episode (show id) for "(day of week)" the "(day number)" of "(month and year). **
+
+Saying the name of the show at the beginning of an episode is called establishing [brand recognition](https://en.wikipedia.org/wiki/Brand_awareness#Brand_recognition).
+It is standard for podcasts, TV and Radio shows as well as on broadcast networks, not to mention the pre-rolls in a movie.
+
+We started to do it because some of our Visually Impaired users appreciated knowing what show is playing.
+Now the same reason can be applied to everyone as the use of visual controlled [User interfaces](https://en.wikipedia.org/wiki/User_interface) have diminished.
+Most people control the playlist with headset or voice controls.
+
+Saying the show id, and date is common where there are a lot of episodes eg: news or weather shows. 
+It is often skipped where the content is sufficient to identify the episode, eg "the last episode of the foo bar baz podcast, or the last Saturday Night Live"
+
+We include the show id and date to allow the listener to refer to the episode easily.
+As we have literally thousands of shows, we need to help people identify which show they are now listening to, so that it can be easily shared, or commented on.
+
+#### What? Why?
+
+We always include **Today's show is entitled. (title)**.
+If the episode is part of a series then we also include **It is part of the series (series name)**.
+We always include the show **(synopsis)**.
+
+This tells the listener what the show is about.
+It allows them to skip the episode if they wish.
+They may wish to do this for many reasons, for example:
+
+- because they are not interested in the topic, 
+- they wish to listen to it while in front of a computer to reference the accompanying show notes, 
+- they are listening in public and the topic might not be appropriate.
+
+#### Who?
+
+The next part will either be **It is the first show by new host (host name)**, **It is the (multiple of 10)th show of (host name)**, or **It is hosted by (host name)**
+
+We are required by the [Creative Commons Attribution-ShareAlike 4.0 International (CC BY-SA 4.0)](https://creativecommons.org/licenses/by-sa/4.0/) license to credit our hosts, so we do.
+
+We think it's important to highlight new hosts especially, so our community we encourage them to continue to contribute.
+
+It's also nice to call out hosts who have been contributing a lot by highlighting each 10th show they send in.
+
+#### Where?
+
+We always include **and is about (minutes)minutes long** to give people an idea of how long the show is.
+
+Normal broadcasts have to fit neatly into a standard TV/Radio Broadcast schedule. 
+Many podcasters now follow the same tradition of having episodes of a predictable length. Eg: 30 minutes or an hour.
+
+On HPR, [there is no restriction on how long the show can be](https://hackerpublicradio.org/about.html) so it's desirable to give the listener a way to know how long the episode is so they can plan accordingly.
+
+
+#### Warning
+
+We always include either **It carries a clean flag** or **It carries an explicit flag**.
+
+This is also common for broadcasts where they are dealing with a topic that may be disturbing to some people.
+
+#### What
+
+We always include **The summary is. (summary)**.
+
+As this also tells the listener what the show is about.
+
+#### License
+
+In the event that the show is not released [CC-BY-SA](https://creativecommons.org/licenses/by-sa/4.0/) we include **Todays show is licensed under a (license_long_name) license.**
+
+## Outro
+
+### Theme Music Credits
+
+The background is an arrangement by [Maestraccio](https://repo.anhonesthost.net/HPR/hpr_website/src/branch/main/www/theme/intro-ak-Maestraccio-cc-by-4.0.mp3) which is released under the [Creative Commons Attribution-ShareAlike 4.0 International (CC BY-SA 4.0)](https://creativecommons.org/licenses/by-sa/4.0/) license, of the [HPR Theme](), composed by [slick0](https://hackerpublicradio.org/correspondents/0042.html) which has [No Copyright](https://creativecommons.org/publicdomain/zero/1.0/) applied.
+
+Over the music is the following text recorded by [Manon](https://hackerpublicradio.org/correspondents/0449.html) which has [No Copyright](https://creativecommons.org/publicdomain/zero/1.0/) applied.
+
+> You have been listening to the Hacker Public Radio podcast, at [hackerpublicradio.org](https://hackerpublicradio.org/).<br>
+> Today's show was contributed by a HPR listener like yourself.<br>
+> If you ever thought of recording a podcast, then visit the [HPR site](https://hackerpublicradio.org/) to find out how easy it really is.<br>
+> Hosting for HPR has been kindly provided by [anhonesthost.com](https://anhonesthost.com/), the [Internet Archive](https://archive.org/),  [rsync.net](https://www.rsync.net/), and the [HPR Community Content Delivery Network](https://repo.anhonesthost.net/HPR/hpr_documentation/src/branch/main/ccdn).<br>
+> Unless otherwise stated, today's show is released under a [Creative Commons Attribution-ShareAlike 4.0 International (CC BY-SA 4.0)](https://creativecommons.org/licenses/by-sa/4.0/) license.
+
+# Discussions about the HPR Theme
+
+- [2023-04 intro](https://hackerpublicradio.org/eps/hpr3837/index.html#comments)
+- [2022-03 Great Intro](https://hackerpublicradio.org/eps/hpr3553/index.html#comment_3378)
+- [2022-03 TTS](https://hackerpublicradio.org/eps/hpr3461/index.html#comment_3306)
+- [2022-03 The TTS voice](https://hackerpublicradio.org/eps/hpr3461/index.html#comment_3377)
+- [2021-11 Theme - was "Possible cause and solution to subscriber attrition(trying again without encryption)"](https://lists.hackerpublicradio.com/pipermail/hpr/2021-November/004327.html)
+- [2020-08 the voice](https://hackerpublicradio.org/eps/hpr3139/index.html#comment_3007)
+- [2019-11 Ken's Voice Is Better Than espeak](https://hackerpublicradio.org/eps/hpr2936/index.html#comment_2799)
+- [2018-09 HPR Branding](https://lists.hackerpublicradio.com/pipermail/hpr/2018-September/003541.html)
+- [2018-09 Accordion outro](https://hackerpublicradio.org/eps/hpr2625/index.html#comment_2493)
+- [2018-10 Intro volume](https://hackerpublicradio.org/eps/hpr2651/index.html#comment_2515)
+- [2018-10 TTS over intro music](https://hackerpublicradio.org/eps/hpr2651/index.html#comment_2517)
+- [2016-02 speech synthesis during intro](https://lists.hackerpublicradio.com/pipermail/hpr/2016-February/002881.html)
+- [2015-12 How to check if the intro and outro are added](https://lists.hackerpublicradio.com/pipermail/hpr/2015-December/002795.html)
+- [2015-02 Intro and Outro](https://lists.hackerpublicradio.com/pipermail/hpr/2015-February/002515.html)
+- [2014-12 Outro Theme](https://lists.hackerpublicradio.com/pipermail/hpr/2014-December/002410.html)
+- [2014-12 Bug Fix HPR Intros](https://lists.hackerpublicradio.com/pipermail/hpr/2014-December/002399.html)
+- [2014-11 MaryTTS, clipping](https://hackerpublicradio.org/eps/hpr1642/index.html#comment_991)
+- [2014-11 An HPR Theme Question, And First Time Member](https://lists.hackerpublicradio.com/pipermail/hpr/2014-November/002312.html)
+- [2014-02 What's the word on intro and outro clips?]()https://lists.hackerpublicradio.com/pipermail/hpr/2014-September/002266.html
+- [2011-09 HPR Theme](https://lists.hackerpublicradio.com/pipermail/hpr/2011-September/000455.html)
+- [2009-06 my eps for HPR and intro](https://lists.hackerpublicradio.com/pipermail/hpr/2009-June/000084.html)

ccdn/README.md

@@ -1,13 +1,12 @@
 # Community Content Delivery Network (CCDN)
 
-A location to track the deployment of the HPR Community Content Delivery Network, that provides a mirror network for our content.
+_A location to track the deployment of the HPR Community Content Delivery Network, that provides a mirror network for our content._
 
+## Availability of HPR Content
 
- Availability of HPR Content
+The HPR site has traditionally been run on a single instance which makes the project vulnerable. 
 
-The HPR site has been traditionally been run on a single instance, which makes the project vulnerable. 
-
-We have experienced several times where we have suffered from issues resulting from system outages, denial of service attacks, forced decommissioning, or increased costs.
+We have experienced several occasions where we have suffered downtime, resulting from system outages, denial of service attacks, forced decommissioning, or increased costs.
 
 There is a clear need to host the content in multiple geographically distributed networks to increase reliability and redundancy.
 
@@ -15,27 +14,26 @@ Applying a [Content Delivery Network](https://en.wikipedia.org/wiki/Content_deli
 
 These large vendor solutions provide free tiers, but the long term business model shows that these are not sustainable. 
 
-Additionally the algorithms used would flag behavior considered normal for HPR contributors, as suspicious and would deny them access.
+Additionally the algorithms used would flag behavior, considered normal for HPR contributors, as suspicious and would deny them access.
 
-
-# Looking to the past
+## Looking to the past
 
 At the dawn of the Internet, it was common for websites and services like DNS to be [mirrored](https://en.wikipedia.org/wiki/Mirror_site) by friends.  
 
 This was for a long time not a viable option for HPR as the quantity of Audio Content was expensive to host and transfer, and was therefore beyond what a home user could reliably serve.
 
-Over time, in some locations members of our community have access to facilities that a few years ago would have been reserved for Internet Service Providers.
+Over time, and in some locations members of our community have access to facilities that a few years ago would have been reserved for Internet Service Providers.
 
-If you are interested in helping hosting the HPR site and media, then please get in touch with _admin @ hackerpublicradio.org_
+If you are one of the fortunate people, and would like to contribute hosting of a mirror of the HPR site and media, then please get in touch with _admin @ hackerpublicradio.org_
 
 
-## Requirements for Hosting
+### Requirements for Hosting
 
 - 24/7 Home Service
 - fixed IP address
 - unlimited bandwidth
 - fast > 500mb/sec upload
-- large > 1T of storage
+- large > 3T of storage
 - permission from your ISP to run a web server
 - Contact information know to the Janitors
 - Optional: [UPS](https://en.wikipedia.org/wiki/Uninterruptible_power_supply)

developer_information.md

@@ -36,7 +36,7 @@ That said, we move with the times when there is a clear advantage to do so.
 
 We run up to date patched stable software.
 
-We have a long tradition of supporting and sharing hacker culture. Any identified vulnerability are fixed with credit if requested.
+We have a long tradition of supporting and sharing hacker culture. Any identified vulnerabilities are fixed with credit if requested.
 
 We use [RSS](https://www.rssboard.org/rss-specification) as a delivery mechanism, which is by default fault tolerant.
 
@@ -46,7 +46,7 @@ All our code is on [GitTea](https://repo.anhonesthost.net/HPR), please clone loc
 
 [Our database](https://hackerpublicradio.org/hpr.sql) is updated frequently, please copy locally.
 
-Our media is served from our [Community Content Delivery Network (CCDN)](https://repo.anhonesthost.net/HPR/hpr_documentation/ccdn/)
+Our media is served from our [Community Content Delivery Network (CCDN)](https://repo.anhonesthost.net/HPR/hpr_documentation/ccdn/).
 
 Bug reports, and patches are welcome from anyone without commitment.
 
@@ -61,5 +61,5 @@ In order to contribute you need to [create an account](https://repo.anhonesthost
 Once you have set up your account, you will need to set up your local
 development environment. [Instructions here](set-up-development-environment.md)
 
-Changes can be submittted as described in [hpr3797 :: How to submit changes to HPR](https://hackerpublicradio.org/eps/hpr3797/index.html).
+Changes can be submitted as described in [hpr3797 :: How to submit changes to HPR](https://hackerpublicradio.org/eps/hpr3797/index.html).
 

podcatchers/README.md

@@ -22,9 +22,9 @@ The following are some of the clients, and we request that people help out repor
 - [Podchaser](https://repo.anhonesthost.net/HPR/hpr_documentation/src/branch/main/podcatchers/Podchaser)
 - [Podtail](https://repo.anhonesthost.net/HPR/hpr_documentation/src/branch/main/podcatchers/Podtail)
 - [Radio.net](https://repo.anhonesthost.net/HPR/hpr_documentation/src/branch/main/podcatchers/RadioNet)
+- [Sonos](https://repo.anhonesthost.net/HPR/hpr_documentation/src/branch/main/podcatchers/Sonos)
 - [Spotify](https://repo.anhonesthost.net/HPR/hpr_documentation/src/branch/main/podcatchers/Spotify)
 - [stagefright](https://repo.anhonesthost.net/HPR/hpr_documentation/src/branch/main/podcatchers/stagefright)
 - [Top Podcast](https://repo.anhonesthost.net/HPR/hpr_documentation/src/branch/main/podcatchers/TopPodcast)
 
-
 See Wikipedia for a [list of podcast clients](https://en.wikipedia.org/wiki/List_of_podcast_clients).

podcatchers/Sonos/README.md

@@ -0,0 +1,25 @@
+# Sonos
+
+<a href="https://upload.wikimedia.org/wikipedia/commons/a/a8/Sonos_Logo.jpg" >
+  <img width="200" src="https://upload.wikimedia.org/wikipedia/commons/a/a8/Sonos_Logo.jpg" alt="Sonos logo" />
+</a>
+
+<!--
+- Confirmed working with HPR Feeds and [CCDN](https://repo.anhonesthost.net/HPR/hpr_documentation/wiki/Community-Content-Delivery-Network)
+- [Source Code on GitHub](https://gpodder.github.io/)
+-->
+## Description
+
+![Sonos UI](podcatcher_Sonos.png "A screenshot of the Sonos UI")
+
+```
+
+```
+## How to install
+
+
+## Subcribing to HPR
+
+
+## Playback
+

policies.md

@@ -0,0 +1,102 @@
+# Policies
+
+## Did you notice Harm ?
+
+Therefore 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.
+
+## We don't tolerate Harassment, Trolling
+
+Hacker Public Radio is dedicated to sharing knowledge in a welcoming community that offers positive feedback and encourages respectful debate.
+
+[Harassment on HPR](https://lists.hackerpublicradio.com/pipermail/hpr/2019-December/003804.html)
+
+## Schedule Guidelines
+
+You must have your show recorded before you reserve a slot.
+
+You must only post a show every two weeks.
+
+[Changes to scheduling guidelines](https://lists.hackerpublicradio.com/pipermail/hpr/2025-September/004922.html)
+
+## Community News
+
+The Community News presenters may exercise discretion in what they read out and refer the audience to the skipped content.
+
+[HPR Community News Comment Summaries](https://lists.hackerpublicradio.com/pipermail/hpr/2025-July/004873.html)
+
+## Auditors
+
+The Auditors role is to observe and report if necessary that the Janitors are been faithful in their communication.
+
+[Auditors on HPR](https://lists.hackerpublicradio.com/pipermail/hpr/2025-September/004908.html)
+
+[Permission to move out a show](https://lists.hackerpublicradio.com/pipermail/hpr/2022-March/004419.html)
+
+## Permission to move out a show
+
+[Permission to move out a show](https://lists.hackerpublicradio.com/pipermail/hpr/2022-March/004410.html)
+
+Janitors can move shows on host permission as normal, but will always ask the mail list where the host cannot or will not move their show.
+
+## HPR is not a podcast platform
+
+[Is HPR a podcast or podcast hosting platform ?](https://lists.hackerpublicradio.com/pipermail/hpr/2022-August/004615.html)
+
+There seems to be a clear desire to keep HPR as a podcast and not transition to a podcast hosting platform. What I came to realize was that the HPR setup could be adapted to become a podcast hosting platform with minor changes. For example, were we to not release the main feed, remove the HPR branding, and provide each show their own schedule, then each hosted podcast (now HPR series) would be their own entity. However it's not something that the community, janitors, or the HPR patrons are enthusiastic about implementing.
+
+## Not everything that "could be of interest to hackers" is allowed.
+
+[Rejecting a show on the grounds that it is "using HPR as a means to push a particular product or view"](https://lists.hackerpublicradio.com/pipermail/hpr/2025-July/004883.html)
+
+
+## We promote other Creative Commons Works
+
+On dropping the Non Commercial License: [HPR: RFC Changing show to CC-BY-SA](https://lists.hackerpublicradio.com/pipermail/hpr/2011-June/000384.html)
+
+Supporting [Various Creative Commons Works](https://lists.hackerpublicradio.com/pipermail/hpr/2013-April/001216.html), that allows people to to submit (a single) interesting/important creative commons works on a given topic to the queue. It should be prefixed with a short introduction as to why we should be interested, then submit it under your own name to the queue. 
+
+### [Policy Change: removal of non free CC-BY-NC license](https://lists.hackerpublicradio.com/pipermail/hpr/2025-March/004853.html)
+
+### [Policy Change: Clarification that contributions are CC BY-SA 4.0 unless otherwise stated](https://lists.hackerpublicradio.com/pipermail/hpr/2024-October/004791.html)
+
+### [Policy Change: Should we reject a show with copyrighted fair use clips in it ?](https://lists.hackerpublicradio.com/pipermail/hpr/2019-May/003673.html)
+
+- From [Kevin O'Brien](https://lists.hackerpublicradio.com/pipermail/hpr/2019-May/003683.html): "Fair Use is not, in the U.S., a right recognized by any statute. It is best understood as "the right to hire a lawyer"."
+- From [stankdawg](https://lists.hackerpublicradio.com/pipermail/hpr/2019-May/003692.html): "Sorry. Not worth the risk. I appreciate the contribution and do not want to discourage the submissions.  But it is too dangerous.  And for the record... no one else can voluntarily accept responsibility. It falls back to me as site owner no matter what."
+- From [Ken Fallon](https://lists.hackerpublicradio.com/pipermail/hpr/2019-May/003695.html): Remember that our policy is also a commitment to anyone using our feed. I know there are downstream projects like college radio, workplaces, shops etc that are using our feed. They would not need to buy a public music license, for feeds [that] contains *only* Creative Commons content.
+
+## Search Page
+
+[Boo, Hiss, a google search on top of the HPR webpage!](https://lists.hackerpublicradio.com/pipermail/hpr/2013-March/001145.html)
+
+Why we do search like we do.
+
+## Site Security stays with the Site admin
+
+[Implemented a deny list on HPR](https://lists.hackerpublicradio.com/pipermail/hpr/2013-March/001112.html)
+
+Attacks to our site get blocked, no discussion required.
+
+## Avoiding background music
+
+[Bed Music](https://lists.hackerpublicradio.com/pipermail/hpr/2012-November/000877.html)
+
+It can be distracting so avoid if possible.
+
+## Swearing is allowed but remember JWP's Granny is listening.
+
+[Swearing?](https://lists.hackerpublicradio.com/pipermail/hpr/2012-April/000640.html)
+
+Swearing is allowed when necessry but use the explicit tag. And don't go out of your way to be belligerent.
+
+## What is a Syndicated show ?
+
+[Syndicated shows](https://lists.hackerpublicradio.com/pipermail/hpr/2011-January/000214.html)
+
+If a show is posted elsewhere prior to been posted to HPR then it would be considered to be a syndicated show.
+
+## When to wind down HPR
+
+[HPR RIP ?](https://lists.hackerpublicradio.com/pipermail/hpr/2010-September/000109.html)
+
+After a period of intermittent posting, the community decided to continue posting HPR shows.

requested_topics/README.md

@@ -0,0 +1,92 @@
+# Requested topics
+
+This is a list of topics that have been requested by the community. 
+
+## General
+
+- How did you get into podcasting/linux/geekdom?
+- What podcasts you listen to and can recommend
+- What's in your bag? Tell us what tools/gear/stuff you keep close at hand.
+- What got you into Linux?
+- Your favorite Android applications.
+- Your favorite desktop applications.
+- Your favorite browser extensions.
+- A introduction to Wireshark.
+- How to set up your own blog.
+- Choosing a artistic design for website, business cards etc.
+- Music Theory
+- Installing a VPN to your home network
+- Init and System.d
+- Episodes for the LPI, or the Networking series.
+- Beginning Audio Series for HPR and OSMP Release
+- Hackintosh computers - what are they, why would you want one.
+- Grub 2.0 introduction and customization.
+- FM Transmitter hack to listen into internet streams
+- How I Got Into Accessible Computing
+- How to do knitting
+- How to build a house
+- How to solder <a href="<!--% absolute_path(baseurl) %-->eps/hpr1037/index.html">hpr1037</a>, 
+  <a href="<!--% absolute_path(baseurl) %-->eps/hpr1047/index.html">hpr1047</a>
+- How to weld
+- How to fix a car
+- Reviews of stream playing software, (for linuxheads who don't want to keep a browser tab open all the time)
+- Reviews of stream ripping software on linux
+- Beginners guide to gnuplot
+- Nagios series, intro, setup, advanced ...
+- How to set up GPG/openPGP
+- What I do with my Raspberry Pi
+- It broke, I fixed it
+- How does coreboot work
+- Introduction to HAM Radio
+- I've moved and they do it like this here
+- How to record a tag team tutorial on a topic
+- Open Street Map new editor
+- etymology
+- functional versus procedural programming
+- sed, awk and grep
+- Setting up imap/smtp (gmail) in a cli mail program
+- Irssi - a sane setup
+- Your view of the future
+- Alternative uses for Bayesian email classifiers (<a href="https://www.youtube.com/watch?v=JKB5CojW4AA">more info</a>)
+- How to use a multimeter, and other basic electronic components like a 555 timer
+- How does Hubble remain fixed on a spot in space while in orbit of the earth
+- Gnu automake system.
+- Any experiences integrating Dell/Wyse thin- and zero- clients into linux networks.
+- What Are the Answers I Need, To the Questions I Don't Know Enough to Ask?
+
+## Networking
+
+### IPv6
+
+- What is an IP address, and what is IPv6 - basic settings. Why can't we just NAT at the ISP level, are there privacy issues in having your MAC address as part of your IP?
+- How to setup IPv6 on Linux, BSD, Windows, Mac, Spark, Android etc
+- IPv6 Addressing terminology , format, shortcuts, address structure, (link local, unique and global), reservations, subnetting, allocation
+- IPv6 Firewall, what to block what to allow
+- Packet structure
+- Troubleshooting IPv6 network issue, using common tools with IPv6, ping icmp, telnet, curl, tcpdump, wireshark,etc
+- How discovery is handled, what is used for dhcp
+- DNS server setup
+- Routing server setup
+- Setting up common services like ssh, apache, nginx
+- Setting up VPN like wireguard
+- Explanation of the new Anycast and why you would use it.
+- Transition plans tips and tricks.
+
+
+## Security 
+
+What do we need for a firewall and what are the detection/prevention technologies that we could be implementing?
+Beyond Firewall and an IDS/IPS, what do I need?
+If you were to treat your home network like a corporate server farm, what tools and hardware would it entail to treat your home network like a security professional?
+Should one use a secondary IDS, behind the firewall, to record what the primary defenses missed.
+Where and how do I set that up?
+Beyond firewall and IDS, what other tools should we be running ?
+Where should they be in my network, and how many physical boxes are we talking about ?
+Emphasis should be on low power devices and free as in beer tools.
+
+How to Read Logs and Formulate a Response to an Intrusion.
+What I've learned from SW, is that you can't prevent an intrusion, it's how to respond when you are compromised.
+Again, according to SW, the security manager's job is to detect intrusions, inside 48 hours rather than 48 months.  
+How can you protect your proprietary data and customer database?
+Better uses for IPFS and IPNS to get a better understanding of practical use of this.
+

suggested_changes.md

@@ -0,0 +1,46 @@
+# HPR Suggested Change
+
+
+## Track reservation key in eps table
+
+Moved from https://repo.anhonesthost.net/HPR/hpr_generator/issues/238
+
+A uploaded show is know by it's key, this should be kept in the eps table so it can be located easily.
+
+## Remove deprecated fields in eps table
+
+Check if version and downloads can be deprecated.
+
+## Comment links should be clickable
+
+Should they ? More moderation needed ?
+
+https://repo.anhonesthost.net/HPR/hpr_generator/issues/157
+
+## Audit of media and supplementary files
+
+https://repo.anhonesthost.net/HPR/hpr_generator/issues/154
+
+Given a show like 2173, which was built to link to supplementary notes on the HPR server, these notes (and other assets) are currently not available because the links are incorrect.
+
+This show references several assets for example:
+
+sqlite> select filename from assets where episode_id = 2173;
+┌─────────────────────────────┐
+│          filename           │
+├─────────────────────────────┤
+│ hpr2173/blinkt_client.py    │
+│ hpr2173/blinkt_legends.svg  │
+│ hpr2173/cronjob_comments    │
+│ hpr2173/full_shownotes.html │
+│ hpr2173/img_01.png          │
+│ hpr2173/img_02.png          │
+│ hpr2173/img_03.png          │
+│ hpr2173/img_04.png          │
+│ hpr2173/img_05.png          │
+│ hpr2173/img_06.png          │
+└─────────────────────────────┘
+
+These are on the IA with the same filenames.
+
+Could this issue be resolved by redirection?