New episodes every weekday Monday through Friday. This page was generated by The HPR Robot at
Welcome to HPR the Community Podcast
We started producing shows as Today with a Techie on 2005-09-19, 17 years, 10 months, 30 days ago. our shows are produced by listeners like you and can be on any topic that "are of interest to hackers". if you listen to HPR then please consider contributing one show a year. if you record your show now it could be released in 4 days.
Call for shows
We are running very low on shows at the moment. Have a look at the hosts page and if you don't see "2023-??-??" next to your name, or if your name is not listed, you might consider sending us in something.
operat0r will never get to some of these as full eps so here you go!
Hosted by operat0r on 2023-08-17 is flagged as Explicit and released under a CC-BY-SA license. hacking,computers,Android,quick tips.general.(Be the first).
Meal preparation involves preparing meals ahead of time for a short
or period of time. This practice may occur among people who desire to
lose weight, gain muscle mass, or maintain a healthy lifestyle. Advance
preparation can serve to standardize food portions. Meals preparation
are fully cooked. Meals may be prepared in small containers such as
Tupperware, and are sometimes labeled and dated to remain
organized.
Freshly cut onions often cause a stinging sensation in the eyes of
people nearby, and often uncontrollable tears. This is caused by the
release of a volatile liquid, syn-propanethial-S-oxide and its aerosol,
which stimulates nerves in the eye. This gas is produced by a chain of
reactions which serve as a defence mechanism: chopping an onion causes
damage to cells which releases enzymes called alliinases. These break
down amino acid sulfoxides and generate sulfenic acids. A specific
sulfenic acid, 1-propenesulfenic acid, is rapidly acted on by a second
enzyme, the lacrimatory factor synthase (LFS), producing the
syn-propanethial-S-oxide. This gas diffuses through the air and soon
reaches the eyes, where it activates sensory neurons. Lacrimal glands
produce tears to dilute and flush out the irritant.
Cooking onions and sweet onions are better stored at room
temperature, optimally in a single layer, in large mesh bags in a dry,
cool, dark, well-ventilated location. In this environment, cooking
onions have a shelf life of three to four weeks and sweet onions one to
two weeks. Cooking onions will absorb odours from apples and pears.
Also, they draw moisture from vegetables with which they are stored
which may cause them to decay.
Sweet onions have a greater water and sugar content than cooking
onions. This makes them sweeter and milder tasting, but reduces their
shelf life. Sweet onions can be stored refrigerated; they have a shelf
life of around 1 month. Irrespective of type, any cut pieces of onion
are best tightly wrapped, stored away from other produce, and used
within two to three days.
A brief history of the term "Silent Key" as applied to amateur radio
Hosted by Trey on 2023-08-15 is flagged as Clean and released under a CC-BY-SA license. morse code, cw, amateur radio, telegraph, memorial.HAM radio.2.
Hello this is Trey, and I am recording this in the shadow of the loss
of a good friend and mentor who helped guide me in my career and in
hobbies like electronics, aviation, and amateur radio. The amateur radio
area is what I will be discussing today.
Many terms within amateur radio find their origins from the days of
telegraph, when operators would use Morse code to send messages across
great distances using wires strung from pole to pole. The telegraph
“key” (or code key) was basically a momentary contact switch which would
close an electrical connection when pressed. Pressing the key down for a
short period of time would send a short pulse down the line, which is
referred to as a “dit” (Sometimes the term “dot” is used). This may be
written using the period “.” symbol. Holding the key down for a bit
longer would send a longer pulse down the line, called a “dash”
(Sometimes the term “dah” is used) and it may be written using the
hyphen “-” symbol.
Telegraph operators became a close knit community, even though they
were geographically separated. Often one operator could identify another
operator by subtleties in the style or personality of how they sent
their messages. This was known as the operator’s “fist” and today we
would describe it as a “behavioral biometric”. As the community of
telegraph operators moved around or were replaced, new “fists” would be
identified, as new personalities of code sending were tapped out on the
telegraph keys.
When an operator passed away, it was a loss to the community, and a
loss of someone who might have been befriended remotely by other
operators. The term of respect created for this situation was “Silent
Key” sent as the abbreviation “SK” ( … -.- ). It meant that the
particular operator would never send code again. His telegraph key would
be silent.
This tradition has been carried on among amateur radio operators or
“Hams”. This is also a close knit community of people. While some still
use Morse code to communicate (Referred to as “CW” for continuous wave),
there are many other forms in use, including voice and digital modes.
But regardless of how we communicated with them, when we lose one of our
own, we still say they are SK. Silent key. No longer able to
transmit.
Organizations like the American Radio Relay League (ARRL) and QRZ.com
try to update their records when a Ham passes away. There are also
databases like silentkeyhq.com which keep records and memories of
deceased operators.
So, it is with great sadness that I have been updating the records
for my close friend and mentor KV4YD. Thank you for your friendship and
support, and for sharing your wisdom over the years. You will be
missed.
In this episode the HPR Audiobook Club discusses the first three books of John Carter of Mars
Hosted by HPR_AudioBookClub on 2023-08-14 is flagged as Explicit and released under a CC-BY-SA license. mars, audiobook club, fiction, scifi, audiobook.general.1.
Pokey:Yellow Tail
Chardonay Its definitely a chardonay in flavor. You can taste the
cost effectiveness up front, but it mellows out on the finish, and is
pretty okay for the price on average.
Right now we are working through a backlog of older episode that have
already been recorded. Once that ends we fully anticipate recording new
episodes with listener participation.
Feedback
Thank you very much for listening to this episode of the HPR
AudioBookClub. We had a great time recording this show, and we hope you
enjoyed it as well. We also hope you'll consider joining us next time we
record a new episode. Please leave a few words in the episode's comment
section.
As always; remember to visit the HPR contribution page HPR could
really use your help right now.
Sincerely, The HPR Audiobook Club
P.S. Some people really like finding mistakes. For their enjoyment,
we always include a few.
Our Audio
This episode was processed using Audacity. We've been making
small adjustments to our audio mix each month in order to get the best
possible sound. Its been especially challenging getting all of our
voices relatively level, because everyone has their own unique setup.
Mumble is great for bringing us all together, and for recording, but
it's not good at making everyone's voice the same volume. We're pretty
happy with the way this month's show turned out, so we'd like to share
our editing process and settings with you and our future selves (who, of
course, will have forgotten all this by then).
We use the "Truncate Silence" effect with it's default settings to
minimize the silence between people speaking. When used with it's
default (or at least reasonable) settings, Truncate Silence is extremely
effective and satisfying. It makes everyone sound smarter, it makes the
file shorter without destroying actual content, and it makes a
conversations sound as easy and fluid during playback as it was while it
was recorded. It can be even more effective if you can train yourself to
remain silent instead of saying "uuuuummmm." Just remember to ONLY pass
the file through Truncate Silence ONCE. If you pass it through a second
time, or if you set it too aggressively your audio may sound sped up and
choppy.
Next we use the "Compressor" effect with the following settings:
"Make-up Gain for 0db after compressing" and "compress based on
peaks" were both left un-checked.
After compressing the audio we cut any pre-show and post-show chatter
from the file and save them in a separate file for possible use as
outtakes after the closing music.
We adjust the Gain so that the VU meter in Audacity hovers around
-12db while people are speaking, and we try to keep the peaks under
-6db, and we adjust the Gain on each of the new tracks so that all
volumes are similar, and more importantly comfortable. Once this is done
we can "Mix and Render" all of our tracks into a single track for export
to the .FLAC file which is uploaded to the HPR server.
At this point we listen back to the whole file and we work on the
shownotes. This is when we can cut out anything that needs to be cut,
and we can also make sure that we put any links in the shownotes that
were talked about during the recording of the show. We finish the
shownotes before exporting the .aup file to .FLAC so that we can paste a
copy of the shownotes into the audio file's metadata.
At this point we add new, empty audio tracks into which we paste the
intro, outro and possibly outtakes, and we rename each track
accordingly.
Remember to save often when using Audacity. We like to save after
each of these steps. Audacity has a reputation for being "crashy" but if
you remember save after every major transform, you will wonder how it
ever got that reputation.
In this episode we look at the planning process for our second RV
trip. Last year we toured the Southwest US, but we don't like to repeat
ourselves. So this time we decided to tour the Southeast US. This not
only let us visit a much different part of the country, but it also
allowed us to go back to our plan to visit some NASA facilities.
These are comments which have been made during the past month, either to shows released during the month or to past shows.
There are 20 comments in total.
Past shows
There are 4 comments on
3 previous shows:
hpr3876
(2023-06-12) "Recording An Episode For Hacker Public Radio"
by Ryuno-Ki.
Comment 1:
Reto on 2023-07-01:
"Good information about recording"
hpr3883
(2023-06-21) "Emergency Show: How to demonstrate the power of condensing steam"
by Mike Ray.
Policy decisions surrounding HPR are taken by the community as a whole. This
discussion takes place on the Mail List which is open to all HPR listeners and
contributors. The discussions are open and available on the HPR server under
Mailman.
The threaded discussions this month can be found here:
This is the LWN.net community event calendar, where we track
events of interest to people using and developing Linux and free software.
Clicking on individual events will take you to the appropriate web
page.
Any other business
The HPR Static Site
As mentioned in the last Community News episode, the HPR database and
website was moved to a new server, and the static site generator written
by Rho`n was used to generated the non-interactive part of
the website.
Since then, there has been a process of adapting the software to the
new configuration. Unfortunately Rho`n has not been
available during this process, but we are gradually learning our way
around his excellent software and making changes to suit our needs.
A policy change is required in the use of the reserve queue. When
there are unfilled slots between 5 and 7 days in the future, episodes in
this queue will be used to fill them.
This extra time is required because of the time it can take to
process a show and load it to the Internet Archive.
Bram Moolenaar, author of Vim
dies
There was an announcement from Bram's family today (2023-08-05) that
he died on August 3rd 2023 from a medical problem that
worsened recently.