The logic seems to be switched https://en.wikipedia.org/wiki/Boolean_data_type where a 0 = true and 1 = false.
Should this not be the other way around where 0 = false = off, and 1 = true = on.
Setting default to 1 as the site is now switched to Hobby public radio, and the robot picks up the default config.
A cross platform method to install the needed modules is the Perl CPAN application.
Make sure that the [gcc](https://www.gnu.org/software/gcc/),
@@ -55,7 +57,7 @@ cpan Tie::DBI
cpan Text:CSV_XS
```
## Testing for Perl module dependencies
### Testing for Perl module dependencies
A bash script is included in the utils directory that will list the Perl modules used by the site-generator and report whether the modules are installed on the current OS.
@@ -65,6 +67,39 @@ It can be run from any directory. To run from the utils directory:
./check-dependencies.sh
```
# Building with Docker
The docker file will copy the local version of the site-generator program, the templates directory, the LICENSE file,
and the site.cfg file into the Docker image. For the docker image to run correctly it needs access to your local
hpr.db file and the output directory (defaults to "public_html"). The default site.cfg assumes the hpr.db is located
in the directory from which the site-generator is run. There are two ways to make the db available to the container:
* Put the hpr.db file in the public_html folder and modify the driver option under the [DBI] section of the site.cfg to:<br>
```driver: dbi:SQLite:public_html/hpr.db```
* mount the hpr.db file into the container when starting up the container with the -v option: <br>
```-v <path to db directory>/hpr.db:/usr/src/app/hpr.db```
Build the image by running the following command from the hpr_generator directory:
```docker build -t hpr/site-generator .```
The first build will take a while. It must pull down the base container, perl-latest, and then pull down and build the
various Perl modules from CPAN. After the initial build, if you have modified your site.cfg file, templates dir, or the
site-generator program itself, builds will be very quick.
If the build fails, it is often from a CPAN module failing to download and install. Try running the Docker build command again.
## Running the container
When runing the Docker image, your local output directory (typically public_html) must be mounted into the container using
the -v option. If you are using the default path for the hpr.db, then the local hpr.db file must also be mounted into the image.
The following is an example of running the site-generator with default locations from the hpr_generator directory:
<pclass="index-link"><ahref="/contribute.html#TOP">↑ Go to top</a></p>
<h1id="so_you_want_to_record_a_podcast">So you want to record a podcast<ahref="<!--% absolute_url(baseurl,'contribute.html#so_you_want_to_record_a_podcast') %-->">.</a></h1>
</header>
<p>Well you've come to the right place.
Our goal here at HPR is to make it as easy as possible for you to get your show released.
We take care of the hard bits so you don't need to.
</p>
<p>
Recording your first show can be a daunting prospect but <ahref="<!--% absolute_url(baseurl) %-->correspondents/index.html">hundreds of people</a>
like yourself have done it, and so can you.
Don't worry that we won't like the topic, just have a look at our <ahref="<!--% absolute_url(baseurl) %-->eps/index.html">Archive</a>
to see how diverse the contributions have been.</p>
<p>
Don't worry if your audio isn't perfect,
that your voice sounds funny,
that English isn't your native language,
that you suffer from a <ahref="<!--% absolute_url(baseurl,'/eps/hpr1102/index.html') %-->">speech impediment</a>,
that your show has loads of ummms and awws in it, etc.
We have plenty of hosts that fall into all these categories, but continue to produce great shows.
</p>
<p>
At the end of the day the show is about the content and less about perfection.
That's not to say we won't help you with ways to improve the audio if you wish,
or narrate your script for you if you can't or won't record it yourself.
</p>
</article>
<article>
<header>
<pclass="index-link"><ahref="/contribute.html#TOP">↑ Go to top</a></p>
<h1id="stuff_you_need_to_know">Stuff you need to know<ahref="<!--% absolute_url(baseurl,'contribute.html#stuff_you_need_to_know') %-->">.</a></h1>
</header>
<p>
This is some important information that you will need to know before uploading to HPR.
</p>
<details>
<summaryid="wikipedia">You will no longer be allowed to <ahref="<!--% absolute_url(baseurl,'about.html#hpr_wikipedia_page') %-->">edit HPR pages</a> on Wikipedia<ahref="<!--% absolute_url(baseurl,'contribute.html#wikipedia') %-->">.</a></summary>
<p>
Once you upload a show, you will be associated with the HPR project.
As such, <ahref="https://en.wikipedia.org/wiki/Wikipedia:FAQ/Organizations">Wikipedia</a> policies will prevent you from creating,
or editing pages relating to
<ahref="https://en.wikipedia.org/wiki/Hacker_Public_Radio">Hacker Public Radio</a>. For more information see <ahref="<!--% absolute_url(baseurl,'about.html#hpr_wikipedia_page') %-->">(Re)Creating a HPR page on wikipedia</a>.
</p>
</details>
<details>
<summaryid="syndication">We <strong>do not syndicate</strong> shows not produced for HPR<ahref="<!--% absolute_url(baseurl,'contribute.html#syndication') %-->">.</a></summary>
<p>
HPR is founded on the principle of Hackers sharing knowledge, so we are not a media aggregation site.
For this reason we are only releasing material created exclusively for HPR.
Once released, the creative commons license will allows sharing it to other locations.
</p>
<p>
We will continue to promote new podcasts, and other creative commons material,
thought our sister site <ahref="https://freeculturepodcasts.org/">Free Culture Podcasts</a>.
</p>
<p>
We do allow <strong>promotion of one example</strong> episode of creative commons content.
You post it as a regular show in the series <ahref="<!--% absolute_url(baseurl) %-->series/0075.html">Podcast recommendations</a>,
with your introduction as to what the piece is, why it's important,
what version of Creative Commons it is released under, and provide links to the website, and to the RSS feed.
</p>
</details>
<details>
<summaryid="license">You are agreeing to <strong>license</strong> your show <strong>CC BY-SA 4.0</strong><ahref="<!--% absolute_url(baseurl,'contribute.html#license') %-->">.</a></summary>
<p>
All our shows are now released under a
<ahref="https://creativecommons.org/licenses/by-sa/4.0/">Creative Commons Attribution-ShareAlike 4.0 International (CC BY-SA 4.0)</a>
license, which means that while you continue to retain the copyright to your show,
you are allowing us (and everyone else) to use it provided we give you attribution and that we release it under the same license.
Click the <ahref="https://creativecommons.org/licenses/by-sa/4.0/">link</a> for more information.
</p>
</details>
<details>
<summaryid="permission">You have <strong>permission</strong> to redistribute your show in its entirety<ahref="<!--% absolute_url(baseurl,'contribute.html#permission') %-->">.</a></summary>
<p>
Never include content, for example music, in your show that you do not have permission to redistribute.
Try to avoid using any content in your show that can not be redistributed under a
<ahref="https://creativecommons.org/licenses/by-sa/4.0/">Creative Commons Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) </a>
license.
If you are redistributing under another Creative Commons license, GNU Free Documentation License, public domain,
or FLOSS software license, then please signal that when you upload your show.
We do not post <ahref="https://repo.anhonesthost.net/HPR/hpr_documentation/src/branch/main/policies.md#policy-change-should-we-reject-a-show-with-copyrighted-fair-use-clips-in-it-httpslistshackerpublicradiocompipermailhpr2019-may003673html">other copyrighted content</a>, even if it is made available under fair use, or by arranged permission.
</p>
</details>
<details>
<summaryid="not_moderated">The audio of your show will <strong>not be moderated</strong><ahref="<!--% absolute_url(baseurl,'contribute.html#not_moderated') %-->">.</a></summary>
<p>
We do not vet, edit, moderate or in any way censor any of the audio you submit, <strong>we expect you to do that</strong>.
Aside from checking snippets for audio quality/spam checking,
we have a policy that we don't listen to the shows before they are aired.
This is a long standing tradition arising from the fact that HPR is a community of peers
who believe that any host has as much right to submit shows as any other.
</p>
<p>
Please note that this only relates to the audio you upload.
We <strong>do</strong> transform the audio into different formats.
The rest of the meta-data (branding/summaries/tags/show notes/etc.), are managed by the HPR Community,
and <strong>probably will</strong> be edited.
</p>
<p>
There is no guarantee that we will accept your show.
Even after it is processes, <strong>any material that is reported as harming HPR may be unlisted until such a time as the situation can be resolved</strong>.
You can expect your show to be rejected for (incomplete list):
<ul>
<li>Inaudible audio</li>
<li>Containing Copyright Content, even <em>Fair Use</em></li>
Please refer to <ahref="https://repo.anhonesthost.net/HPR/hpr_documentation/src/branch/main/policies.md#free-speech-and-general-conduct">Free speech and general conduct</a>
which describes the agreed approach to this topic.
</p>
</details>
<details>
<summaryid="explicit_content">Your show will be signaled as containing <strong>explicit</strong> content<ahref="<!--% absolute_url(baseurl,'contribute.html#explicit') %-->">.</a></summary>
<p>
Given that we are an open forum for free speech,
we signal all our shows as "explicit" with the assumption that the listeners will apply the required discretion when playing the shows in public.
That said the majority of our content is technical in nature and therefore is often considered appropriate for any audience.
If you feel that your show will be considered <strong>inoffensive in every region of the world</strong>
then you can signal your show as <em>Clean</em> when you upload the show.
</p>
<p>
When dealing with content that is "explicit" or contains material that would best be suited for a mature audience,
it has become traditional to include a <strong>short warning</strong> at the very beginning of the show before the intro,
to allow listeners <strong>sufficient time</strong> to switch off the episode should they so desire.
</p>
<p>
Please refer to <ahref="https://repo.anhonesthost.net/HPR/hpr_documentation/src/branch/main/policies.md#free-speech-and-general-conduct">Free speech and general conduct</a>
which describes the agreed approach to this topic.
</p>
</details>
<details>
<summaryid="schedule">You determine when your show will be <strong>scheduled</strong><ahref="<!--% absolute_url(baseurl,'contribute.html#schedule') %-->">.</a></summary>
<p>You decide when you upload your show <ahref="<!--% absolute_url(baseurl,'contribute.html#upload_your_show') %-->">when it should be released</a>.
You can pick a day, or put it in the reserve pool and let the Janitors use it there are free slots.</p>
</details>
<details>
<summaryid="utf8">We use <strong>UTF-8</strong> end to end<ahref="<!--% absolute_url(baseurl,'contribute.html#utf8') %-->">.</a></summary>
<blockquote>See the video "<ahref="https://www.youtube.com/watch?v=MijmeoH9LT4">Characters, Symbols and the Unicode Miracle -
Computerphile</a>" for an interesting background to ASCII and <ahref="https://en.wikipedia.org/wiki/UTF-8">UTF-8</a>.
</blockquote>
</details>
<details>
<summaryid="accessibility">Keep <strong>accessibility</strong> in mind<ahref="<!--% absolute_url(baseurl,'contribute.html#accessibility') %-->">.</a></summary>
<p>
When you includes output from the command line in the show notes,
posting screen-shots of console or terminal output
makes it impossible for screen readers to access the text.
Always try to include the raw output ( eg: embedded in <pre> tags)
</p>
<p>Include descriptive language in any link texts.
Avoid structures like: <em>"For accessibility information
<p>When adding Images, add the descriptive text under the image (not in the alt tag).
That way everyone can benefit from the description.
</details>
<details>
<summaryid="international">Your show will be heard by an <strong>International Audience</strong><ahref="<!--% absolute_url(baseurl,'contribute.html#international') %-->">.</a></summary>
<p>
We have people listening from all over the world, who may not have the same cultural background as yourself,
therefore you should be as clear as possible when giving details.
For example always give temperatures in both Celsius and Fahrenheit, measurements in Metric and Imperial,
dates in <strong>YYYY-MM-DD</strong><ahref="https://en.wikipedia.org/wiki/ISO_8601">iso8601</a> format,
and abbreviations using the <ahref="https://en.wikipedia.org/wiki/NATO_phonetic_alphabet">NATO phonetic alphabet</a>.
</p>
<p>
Never assume that your audience knows what age a sixth grader is, or how big a 20 Cent Euro coin is.
Keep in mind that keyboard layouts are also different so make sure to specify the key shape or the position
inrelation to a common known standard.
For example:
</p>
<blockquote>The at sign normally situated above the 2 key on a US keyboard, and has a unicode number of U+0040.
For more information see <ahref="https://en.wikipedia.org/wiki/At_sign">Wikipedia</a></blockquote>
title="ISO 8601 was published on 06/05/88 and most recently amended on 12/01/04."alt="An xkcd cartoon showing ISO 8601"/></a>
</p>
</details>
<p>
If you have any questions please join one of our <ahref="<!--% absolute_url(baseurl,'about.html#contact') %-->">contact channels</a> to chat with people who will help.
</p>
</article>
<divclass="lane stack">
<article>
<header>
<pclass="index-link"><ahref="/contribute.html#TOP">↑ Go to top</a></p>
<h1id="pick_a_topic">Pick a Topic<ahref="<!--% absolute_url(baseurl,'contribute.html#pick_a_topic') %-->">.</a></h1>
</header>
<p>
The first thing you will need to do is decide on a topic for your show.
OMG I just learned, broke, hacked, discovered this cool thing and noone in my house get’s it.
Check out our 91 in depth series, or 6,938 unique tags for ideas.
You might already have an idea,
but if not you can have a look at our <ahref="<!--% absolute_url(baseurl) %-->eps/index.html">Archive</a> page for examples of shows people have recorded in the past.
<pid="requested topics">
We maintain a page of <ahref="https://repo.anhonesthost.net/HPR/hpr_documentation/src/branch/main/requested_topics">requested topics</a>
that have been sent in by the community.
Feel free to add it to the list via <ahref="<!--% absolute_url(baseurl,'about.html#contact') %-->">the contact channels</a>.
</p>
<ahref="<!--% absolute_url(baseurl,'contribute.html#requested_topics') %-->">Requested Topics</a>, or our
<ahref="<!--% absolute_url(baseurl) %-->series/index.html">Series</a> page to see if you can add your knowledge to the pool.
</p>
<p>
If you are worried that your show may not be of interest to Hackers then you can <ahref="<!--% absolute_url(baseurl) %-->will-my-show-be-of-interest-to-hackers.html">click here</a> to check if it is.
</p>
<p>
If you can't think of anything to talk about then please just record a show telling us
<ahref="<!--% absolute_url(baseurl) %-->series/0029.html">how you got into tech</a>
as a way to introducing yourself to the community.
</p>
</article>
<h2id="record_your_show">3. Record your show<ahref="<!--% absolute_url(baseurl,'contribute.html#record_your_show') %-->">.</a></h2>
<h1id="scheduling">Deciding when to post your show</h1>
<p>Y</p>
<p>We have a <ahref="https://repo.anhonesthost.net/HPR/hpr_documentation/raw/branch/main/workflow/SchedulingGuidlinesFlowChart.odg">flow diagram</a> if that helps.</p>
<p>Please see <ahref="https://repo.anhonesthost.net/HPR/hpr_documentation/src/branch/main/queue.md">for more information on the queue</a>.</p>
<h2id="regular_queue">Regular Queue</h2>
<ol>
<li>You must have your audio recording ready to upload <strong>before</strong> you pick a slot.</li>
<li>All hosts must leave at least 9 slots (approximately two weeks) between their shows.</li>
<li>New hosts, Interviews, and other time critical shows should use the first free slot.
Otherwise, when the queue is filling up then leave some slots free for new contributors by selecting a slot in the first empty week.</li>
</ol>
<h2id="reserve_pool">Reserve Pool</h2>
<li>If you have a non urgent show that is timeless, then add it to the <ahref="<!--% absolute_url(baseurl,'contribute.html#reserve_pool') %-->">reserve pool</a>.</li>
</article>
future feed
<p>
Over the years
The HPR Schedule is entirely community driven and we recommend that <strong>you</strong> pick the date or show number
as then you know when your show will be released.
However the slots will only be allocated once the shows have been successfully processed.
Any missing information can result in a show missing the requested slot.
</p>
<p>
The reserve pool is intended only to be used in the cases where there is still a gap in the schedule one week prior to release.
This was known as the emergency queue, but now can also be used when the hosts don't care when the shows are scheduled.
They will be used on a first come first go basis, when there is no conflict with the scheduling Rules.
These shows contain a message alerting listeners to the fact that we had free slots that were not filled.
</p>
<p>
<ahref="https://repo.anhonesthost.net/HPR/hpr_documentation/src/branch/main/policies.md#permission-to-move-out-a-show">not possible to move them</a>.
</p>
<h2id="reserving">All reservations need to be approved<ahref="<!--% absolute_url(baseurl,'contribute.html#reserving') %-->">.</a></h2>
You may include backing music but it's best if you don't. Most long time podcast listeners speed up their shows,
as this allows them to cram more shows into a day. Having bedding music makes it more difficult to understand,
and prevents tools like <em>truncate silence</em> from working correctly.<br/>
Others will convert shows to mono to listen in one ear leaving the other free to carry out their other chores.
Still more slow the shows down so that they can improve their English.
Others are hard of hearing and backing music makes it difficult to understand the text.
</p>
<h2id="encoding">We mix down to Mono<ahref="<!--% absolute_url(baseurl,'contribute.html#encoding') %-->">.</a></h2>
<p>
We will by default mix down your show to one channel mono and we will
<ahref="https://gitorious.org/hpr-scheduling-system/hpr-scheduling-system/source/2d526e000d31e79afa3d863ea8659503e2074267:transcoding/hprtranscode">transcode</a> to MP3, ogg and spx formats. If you want to control this in more detail then please email admin at Hacker Public Radio for more information.
</p>
<h2id="no_metadata">No need to add Metadata to the file<ahref="<!--% absolute_url(baseurl,'contribute.html#no_metadata') %-->">.</a></h2>
<p>
There is no need to add any information to the file as that will be inserted based on the information you fill in when you upload the show.
</p>
</article>
<hrclass="no-css">
<article>
<header>
<pclass="index-link"><ahref="/contribute.html#TOP">↑ Go to top</a></p>
Enter some text about yourself with links to your blog or other online presence.</li>
</ul>
<p>
Your profile information is used on the website, in the RSS feeds, and on social media sites. You can change your profile information at any time, by submitting another show.
This will be a short descriptive title and will be used everywhere to identify your show. Any valid UTF-8 character is acceptable, but keep the length short and clear.</li>
If I notice an error in my show's details how can it be fixed?</h2>
<ul>
<li><p>The HPR administrators can make changes to show titles, summaries, notes and so forth. Ideally send an
email to <code>admin</code> at <code><!--% make_sfw(is_sfw, "hobby", "hacker") %-->publicradio.org</code> explaining what the problem is and we'll fix it for you.
We'll also ensure that the changes are propagated to the relevant page on archive.org.</p></li>
<li><p>Don't be tempted to send in your corrections as a comment. Comments are not propagated to archive.org, so people
referring to that copy will not see the changes.</p></li>
<p>For more information on how to become a Correspondent see our <ahref="<!--% absolute_url(baseurl) %-->../about.html#so_you_want_to_record_a_podcast">contribute</a></center> page. To add a logo here, either email one to admin at hpr or setup your email on <ahref="https://en.gravatar.com/">Gravatar</a>. To protect your browsing privacy we gather the images every hour and serve them directly from HPR.<p/>
<h2class="title"><ahref="/eps/hpr3246/index.html">The Fourteenth Annual 26 Hour New Year's Eve Show</a></h2>
</header>
<h3>Welcome every <ahref="https://www.timeanddate.com/counters/multicountdown.html">TimeZone</a>!</h3>
<p>
<em>If you keep talking, we'll keep recording.</em>
</p>
<p>For those who don't know, on New Year's Eve 2025-12-31 10:00 UTC (5:00 AM EST), we will have a recording going on the HPR Mumble server for anyone to come on and say "Happy New Year" and talk about whatever they want.
We will leave the recording going until at least 2026-01-01 12:00 UTC (7:00 AM EST), and keep recording until the conversation stops.</p>
<p>
So please stop in. Say "Hi" and maybe join in the conversation with other HPR listeners and contributors. It's always a good time!!<br>
<p>Hacker Public Radio is a technology focused podcast that releases shows every weekday Monday to Friday. Our shows are produced by listeners like you and can be on any topic that is of interest to hackers, makers, hobbyists, etc. We are a welcoming community that offers positive feedback and encourages respectful debate.</p>
<!--% INCLUDE 'content-index-announcement.tpl.html' %-->
<p><!--% make_sfw(is_sfw, "Hobby", "Hacker") %--> Public Radio is a technology focused podcast that releases shows every weekday Monday to Friday. Our shows are produced by listeners like you and can be on any topic that is of interest to <!--% make_sfw(is_sfw, "hobbyists", "hackers, hobbyists") %-->, makers, etc. We are a welcoming community that offers positive feedback and encourages respectful debate.</p>
<!--% PROCESS 'content-index-announcement.tpl.html' %-->
<h1><u>The <!--% get_new_year_show_ordinal_year %--> Annual 26 Hour New Year's Eve Show</u></h1>
<h2>Welcome every <ahref="https://www.timeanddate.com/counters/multicountdown.html">TimeZone</a>!</h2>
<p>
<em>If you keep talking, we'll keep recording.</em>
</p>
<p>For those who don't know, on New Year's Eve <!--% get_new_year_show_start() %-->, we will have a recording going on the HPR Mumble server for anyone to come on and say "Happy New Year" and talk about whatever they want.
We will leave the recording going until at least <!--% get_new_year_show_end() %-->, and keep recording until the conversation stops.</p>
<p>
So please stop in. Say "Hi" and maybe join in the conversation with other HPR listeners and contributors. It's always a good time!!<br/>
<p>With so many people on the chat, you must use push to talk.
You also need to use a Headset so the audio of the room is not fed back.
If there is a problem with your setup, then please drop and listen to the stream.
Trying to correct poor audio in post is a lot of work, that someone else will have to do.</p>
<h3>Be Polite</h3>
<p>When you enter the room please do not interrupt ongoing conversations.
Wait for a pause in the conversation and say Hi.
It's quite common for people you might not know to join as they wish to speak with other people in the room.
They may have been waiting all year for the chance to meet, so please give people the space to have these conversations.</p>
<h3>Do not announce the Time Zones</h3>
<p>As there are so <amoz-do-not-send="true"href="https://en.wikipedia.org/wiki/Time_zone">many Time Zones</a> there is no need to interrupt the conversation to announce every one.
If you are joining from a time zone that is currently switching to the New Year, then please wait for a pause and wish people Happy New Year.</p>
<h3>Don't Fill Dead Air</h3>
<p>This is a relaxed meet-up, and not a traditional "Radio Broadcast".
If there are no conversations going on at a given time, don't feel the need to "fill dead air".
Before the recording is posted as a podcast the <ahref="https://manual.audacityteam.org/man/truncate_silence.html">silences will be truncated</a>.</p>
<h3>Do not monopolise the conversation</h3>
<p>Please be mindful that you (or your beverage of choice) may be speaking too much ;-).</p>
<h3>You are a Guest</h3>
<p>Be respectful, and remember that attendance on the New Year Show does not <ahref="https://hub.hackerpublicradio.org/calendar.php">constitute a show</a>.</p>
<h3>CC-BY-SA</h3>
<p>The recording will be released as a podcast on HPR under a <arel="license"href="https://creativecommons.org/licenses/by-sa/4.0/"> Creative Commons Attribution-ShareAlike 4.0 International (CC BY-SA 4.0)</a> license.
The recordings will be released mid year, when there is a lull in submissions.</p>
<h2>Mumble Setup</h2>
<p>Already have Mumble installed, then <ahref="mumble://chatter.skyehaven.net:64738/Hacker%20Public%20Radio?version=1.2.0">this link will bring you to the HPR Room</a>.</p>
<p>Get the PC Client <ahref="https://wiki.mumble.info/wiki/Main_Page">https://wiki.mumble.info/wiki/Main_Page</a><br/>
<p>Get the Android Client Mumla <ahref="https://f-droid.org/packages/se.lublin.mumla">https://f-droid.org/packages/se.lublin.mumla</a></p>
<p>Then join the Server: <strong>chatter.skyehaven.net</strong><br/>
Port: <strong>64738</strong><br/>
Channel: <strong>HPR</strong></p>
<p><strong>Use Push to Talk</strong>. With so many people hands free is not an option.</p>
<p>For those who have never used Mumble before, see this <ahref="https://hackerpublicradio.org/mumble-howto">how-to explaining the setup of the desktop Mumble client</a>,
or listen to <ahref="https://hackerpublicradio.org/eps.php?id=3503">hpr3503 :: Configuring Mumble</a>.</p>
<h3>Video Only (no audio) server</h3>
<p>
For those who wish to see the video of some of the participants we have a jitsi server.<br/>
We are using Etherpad for people to share links and info to things they are discussing.
The Etherpad will be used for the HPR audio shownotes so please feel free to add to it.
The entire event will be broken into 2 to 3 hour segments and made available as HPR episodes.<br/>
<em>This really, really helps us out to post the show faster !</em>
</p>
<h2>History</h2>
<p>Suggested by <ahref="https://hackerpublicradio.org/correspondents/0128.html">pokey</a> in 2011.
As podcasting tends to be a one way conversation, he thought it would be nice to get all the FLOSS, Linux, Free Culture, podcasters and Listeners in one place to get together and chat in person.
Initially it was planned to be just a few hours, but we kept missing members from other parts of the world.
The show was extended to welcome ever time zone to the New Year, which actually turns out to be <ahref="https://en.wikipedia.org/wiki/List_of_UTC_offsets">38 Timezones</a>, over 26 Hours.</p>
<p>So we will record for at least 26 Hours, but will keep the recording going for an "After Show".
Some years the after show has been even longer than the show itself.
While this is on the HPR Site, it is entirely a community initiative which is supported heavily by the fine folks over at the <ahref="https://linuxlugcast.com/">LinuxLugCast</a>, with the Mumble Server been provided by <ahref="https://hackerpublicradio.org/correspondents/0228.html">Delwin</a>.</p>
<h2class="title"><ahref="<!--% absolute_path(baseurl) %-->new_year.html">The <!--% get_new_year_show_ordinal_year %--> Annual 26 Hour New Year's Eve Show</a></h2>
</header>
<h3>Welcome every <ahref="https://www.timeanddate.com/counters/multicountdown.html">TimeZone</a>!</h3>
<p>
<em>If you keep talking, we'll keep recording.</em>
</p>
<p>For those who don't know, on New Year's Eve <!--% get_new_year_show_start() %-->, we will have a recording going on the HPR Mumble server for anyone to come on and say "Happy New Year" and talk about whatever they want.
We will leave the recording going until at least <!--% get_new_year_show_end() %-->, and keep recording until the conversation stops.</p>
<p>
So please stop in. Say "Hi" and maybe join in the conversation with other HPR listeners and contributors. It's always a good time!!<br>
<!--% page_title = "HPR ~ Subscribe to our feeds" %-->
<h1>RSS Syndication</h1>
<h2>Subscribe to our Feeds</h2>
<p>
@@ -51,9 +52,9 @@
Use this feed to get the archived episodes. The feed themselves run over 15Mb in size and so use them to download the archived episodes and when you are up to date switch back to the Two Week Feeds listed above.
</p>
<ul>
<li><ahref="<!--% absolute_path(baseurl) %-->hpr_total_opus_rss.php">opus feed</a> Warning over 62G</li>
<li><ahref="<!--% absolute_path(baseurl) %-->hpr_total_ogg_rss.php">ogg feed</a> Warning over 71G</li>
<li><ahref="<!--% absolute_path(baseurl) %-->hpr_total_rss.php">mp3 feed</a> Warning over 70G</li>
<li><ahref="<!--% absolute_path(baseurl) %-->hpr_total_opus_rss.php">opus feed</a> Warning over 64G</li>
<li><ahref="<!--% absolute_path(baseurl) %-->hpr_total_ogg_rss.php">ogg feed</a> Warning over 68G</li>
<li><ahref="<!--% absolute_path(baseurl) %-->hpr_total_rss.php">mp3 feed</a> Warning over 72G</li>
<metaname="description"content="Hacker Public Radio is a podcast that releases shows every weekday Monday through Friday. Our shows are produced by the community (you) and can be on any topic that is of interest to hackers and hobbyists."/>
<linkrel="shortcut icon"href="/hpr.ico">
<linkrel="alternate"type="application/rss+xml"title="Hacker Public Radio Opus RSS"href="<!--% absolute_path(baseurl) %-->hpr_opus_rss.php"/>
<linkrel="alternate"type="application/rss+xml"title="Hacker Public Radio Ogg Vorbis RSS"href="<!--% absolute_path(baseurl) %-->hpr_ogg_rss.php"/>
<linkrel="alternate"type="application/rss+xml"title="Hacker Public Radio MP3 RSS"href="<!--% absolute_path(baseurl) %-->hpr_mp3_rss.php"/>
<linkrel="alternate"type="application/rss+xml"title="Hacker Public Radio Comments RSS"href="<!--% absolute_path(baseurl) %-->comments.rss"/>
<metaname="description"content="<!--% make_sfw(is_sfw, "Hobby","Hacker")%--> Public Radio is a podcast that releases shows every weekday Monday through Friday. Our shows are produced by the community (you) and can be on any topic that is of interest to <!--% make_sfw(is_sfw, "makers", "hackers") %--> and hobbyists." />
<linkrel="alternate"type="application/rss+xml"title="<!--% make_sfw(is_sfw, "Hobby","Hacker")%--> Public Radio Opus RSS" href="<!--% absolute_path(baseurl) %-->hpr_opus_rss.php" />
<linkrel="alternate"type="application/rss+xml"title="<!--% make_sfw(is_sfw, "Hobby","Hacker")%--> Public Radio Ogg Vorbis RSS" href="<!--% absolute_path(baseurl) %-->hpr_ogg_rss.php" />
<linkrel="alternate"type="application/rss+xml"title="<!--% make_sfw(is_sfw, "Hobby","Hacker")%--> Public Radio MP3 RSS" href="<!--% absolute_path(baseurl) %-->hpr_mp3_rss.php" />
<linkrel="alternate"type="application/rss+xml"title="<!--% make_sfw(is_sfw, "Hobby","Hacker")%--> Public Radio Comments RSS" href="<!--% absolute_path(baseurl) %-->comments.rss" />
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.