Podcasts about Increment

Pastor Alan R. Knapp discusses the topic of "INFERENCES (Part 2 of 2): “Inferences in Hebrews”" in his series entitled "Hebrews 2020: We See Jesus (2X)" This is Increment 167 and it focuses on the following verses: Hebrews in Toto, Hebrews 6:16-20 ESPECIALLY

Pastor Alan R. Knapp discusses the topic of "The Present Truth: Part Two" in his series entitled "Hebrews 2020: We See Jesus" This is Increment 443 and it focuses on the following verses: Hebrews in toto especially Hebrews 11; 2 Peter 1:12

Pastor Alan R. Knapp discusses the topic of "The Present Truth: Part One" in his series entitled "Hebrews 2020: We See Jesus" This is Increment 442 and it focuses on the following verses: ebrews 3:7-11, 4:2, 3a, 11:4-40; 2 Peter 1:12

Pastor Alan R. Knapp discusses the topic of "Inferences Part One (of Two): The Inference of Universal Salvation!" in his series entitled "Hebrews 2020: We See Jesus (2X)" This is Increment 166 and it focuses on the following verses: Hebrews In Toto, Hebrews 6:16-20 and 10:19-22, ESPECIALLY

Some believers who remain unhappy about the increase in the Achimota Forest gate fee from GH¢1 to GH¢10 have gathered to pray for God's intervention

Pastor Alan R. Knapp discusses the topic of "Doers NOT Drifters" in his series entitled "Hebrews 2020: We See Jesus (2X)" This is Increment 18 and it focuses on the following verses: Hebrews 4:2, 12:1-2

Pastor Alan R. Knapp discusses the topic of "Who Told You to Stop Marching?" in his series entitled "Hebrews 2020: We See Jesus" This is Increment 441 and it focuses on the following verses: Hebrews 11:30

El INEGI informó que, de acuerdo a la estimación oportuna del producto interno bruto, en el segundo trimestre de 2026 la economía mexicana incrementó 1.5 por ciento, respecto al trimestre previo, mientras que, en su comparación con el mismo periodo, pero del año anterior el producto interno bruto creció 2.1 por ciento. al respecto, la presidenta Claudia Sheinbaum detalló los sectores donde se reportaron los avances más significativosSee omnystudio.com/listener for privacy information.

Conocé los datos oficiales más destacados del turismo internacional para el segundo trimestre del año.    

Pastor Alan R. Knapp discusses the topic of "Always “In a Son” " in his series entitled "Hebrews 2020: We See Jesus" This is Increment 440 and it focuses on the following verses: Hebrews 1:1-2 and Hebrews 11:1-40

This show has been flagged as Clean by the host. 01 Introduction In this episode I will describe techniques for downloading podcasts using basic shell commands such as wget. I will illustrate this using a bash script that can be used to download HPR podcasts. Even if you do not have any interest in downloading your podcasts using this method, you may find some of the methods useful or interesting. It is the principles that are discussed here that are important, rather than the implementation. 02 I realize that there are already a number of different podcast download programs available, including at least one written in bash. However, you may feel that none of these suit how you wish to do things and want to create your own system tailored to your specific needs. If so, then I hope the following is of some use to you. If not, then you may still find some of the things discussed here to still be of interest. Some of the subjects I cover include wget to a user defined file name. parsing xml with xmllint. using inotifywait to trigger an action when a file is created or modified. using notify-send to send a message to the notification area. and a way of allowing a cron job to send a message to the user interface. 03 Background There has been an ongoing discussion in comments to some HPR episodes about problems downloading HPR podcast episodes. Apparently some people have been experiencing problems with the way the episode URLs are structured. 04 I am afraid that I don't fully understand the nature of these problems, so I won't be addressing that problem directly. Instead, I will present a bash script that I have written which can be used to download HPR podcasts. This bash script can be run using cron to automatically fetch new HPR podcasts and save them to a designated directory. This is a simplified version of a script that I have used for years to download HPR and other podcasts. 05 I won't try to read the full bash script out in this podcast, as that would be a bit dull to listen to. I will instead describe what each section does and why I chose to do things that way. Perhaps other people can offer suggestions of better ways to do things. I will post the full bash script in the show notes. 06 Fetching Podcasts The standard way of distributing podcasts is to publish an RSS feed containing URL links to the audio files. RSS is a very long established and widely supported mechanism for this and other purposes. An RSS feed is basically an XML document which can be accessed over HTTP. These URLs contained in the RSS XML document can then be used to download the actual audio files, such as MP3 or OGG files. 07 Basically what we need to do is the following • Download the RSS XML document. • Extract the URL links to the audio files. • Compare the list of these links to a previously saved list to see which ones are new and which ones are ones that we previously downloaded. 08 • Make a list of the new URLs. • Go through this list of new URLs and download each of the new audio files. • Check to see that we actually received the new audio file. • Add the URLs of the files we successfully downloaded to our saved list of podcast URLs 09 In addition to this, we would like to have the above happen automatically in the background without our having to take any action on our own. We may wish to receive a notification of when a new podcast has arrived however. We would probably also wish to receive notification of any errors or failures. 10 Fetching Podcasts - The Preliminaries Our desire to be able to run the script automatically imposes some requirements on our solution. To schedule the script we will use cron. Cron is a Linux facility to run scripts on a schedule. 11 One of the side effects of using cron however is that we need to specify the full path to the locations where we intend to keep any data files, plus also the full path to where we intend to put the downloaded podcasts. 12 So the first thing we need to do in our script is to specify a number of different values for things like file location, the URL for the HPR RSS feed, and several other things as well. I will skip over the details of these, although I may make reference to them later. 13 Get the RSS Data The first thing of real substance to do is to fetch the current RSS feed data. I have put this in a bash function called getrssurldata The contents of this function are a one liner, but with a number of elements chained together through pipes. 14 Downloading the RSS XML Document • First we use wget, which is a standard command on most Linux distros. • We specify four things. • First we set a timeout. I have chosen 20 seconds. • Next we set the retry limit. I have chosen 3. 15 • Then we specify that the output of wget is sent to stdout rather than saved as a file. • This is done by using the -O option followed by a space and then a dash. • The O option is usually used to specify a file to save the output to, but when used with a dash causes output to go to stdout. • Then we specify the URL of the HPR RSS feed. 16 Contents of the XML Document This gives us the HPR RSS XML document. There are about 5,000 lines in this RSS document. Most of those lines are the show notes which are also included in the feed. 17 Extracting the Podcast Episode URLs There are only 10 lines of the document that contain information that we are interested in however. These lines are enclosed in "enclosure" XML tags. We just need to find those lines and separate out the URLs 18 Standard Command Line Tools There are two ways that we can do this. One is to use a combination of grep, sed, and cut. Grep can find the lines containing the enclosure tags. Sed and cut can extract the URL from the surrounding extraneous data. 19 However, this method does not discriminate between real enclosure tags in the data portion of the RSS feed and enclosure tags in the show notes which are included in the feed from episodes such as this one. This may be an acceptable problem in practical terms, but we can do better. 20 Using an XML Parser The other method is to actually parse the XML document. there are at least two command line XML parsers that I am aware of. These are "xmllint", and "xlmstarlet". I have used xmllint in this example. I have not used xmlstarlet, so I can't offer any comment on how easy or difficult to use it is. 21 I won't give a detailed explanation of all the things that xmllint can do. It has many features, most of which, as the name suggests, have to do with finding formatting problems with the XML itself. Describing everything it can do would be at least one episode in itself. I will instead just give the particular command used and explain each element of it. 22 In this example assume that we are piping the output of wget directly into xmllint. The complete command is xmllint --xpath "//channel/item/enclosure/@url" - | cut -d'"' -f2 23 In this example, xmllint is the name of the command. --xpath tells it to parse the document according to the string which follows. "//channel/item/enclosure/@url" tells it to find a series of tags in the hierarchy of channel, followed by item, followed by enclosure, and then extract the url attribute from the enclosure tag. The "-" which follows tells it to look for input from stdin rather than from a file. 24 The result is a string which has the url attribute name, an equal sign, and the URL that we want enclosed in quotes. To get just the URL itself, we pipe the output from xmllint into cut, using the doublequote characters as delimiters. We then save the result in a temporary file. 25 Finding the New Episodes Next we wish to find the new podcast episodes. Each HPR episode is identified by a unique URL. This means that if we save the URLs of episodes that we have already downloaded, we just have to look for the URLs that do not appear in this saved list. https://hub.hackerpublicradio.org/ccdn.php?filename=/eps/hpr4659/hpr4659.mp3 26 The easiest way to do this is to take our two lists of URLs, sort each into temporary files, and then compare the sorted URLs using the "comm" command. 27 This is simple, but has a drawback. Some podcasts occasionally change distributors. When they do this, the old podcasts are re-published with new URLs and you end up downloading a lot of old episodes over again. 28 With HPR we could get around this by extracting just the file name and looking for that instead of the full URL. I will however leave that problem as an exercise for the student and just accept that if the URL format changes we may end up downloading old episodes over again. Since the feed has a maximum of only 10 episodes in it however, that isn't really that big of a problem. It would be more of a problem with podcasts which have very large numbers of episodes in their feed, but the solutions to those will be feed specific. 29 Downloading the New Podcasts We should now have a list of URLs for the new podcasts we do not already have. Typically this should be only one file, but there could be several, or even as many as 10, if we have not turned on our computer in a while. Therefore, we need to iterate through the file of new podcast URLs and download each one. 30 Before we do that however, we should check to see if there is in fact anything new to download. To do this, simply use "wc -l" to count the number of lines in the list of new URLs and save the resulting number. 31 If this number is zero, there is nothing to download, we can skip the download step. As an additional check, we should see if the number of downloads exceeds some threshold value that we wish to set. This is not a major problem with HPR, but some podcasts have hundreds of files in their RSS feed rather than just the most recent ones. If we do exceed our download limit, then we need to log an error and skip downloading. 32 Assuming there are no problems so far however, the first thing we need to do is to extract the name of the audio file from the URL. We can do that using the "basename" command. We will use this to specify the name that we use when we save the audio file. 33 HPR has a very well formed file name. Some podcasts do not however, and for those you would need to construct some sort of suitable name either using information found in the URL or simply creating a name using a time stamp. 34 Next we download the audio file using wget. This is similar to how we downloaded the RSS feed, but with a few changes. One is that I have increased the timeout to 90 seconds. This may not have been necessary, but seemed like a good idea. 35 The next is that when specifying the output file name using -O, we use the file name we extracted from the URL. The third is that we specify a destination directory using the -P option. 36 After wget has finished, including any retries that it had to do, we next check that the expected new file is both present and not empty. We did this using an "if" statement with the "-s" option. If the file was found and not zero, then we add that URL to a temporary list of downloaded URLs. 37 If the file was not present, or was zero length, we output an error message to an error log. I will come back to this point later. 38 Next, if there is more that one podcast to download we sleep for 3 seconds. While not strictly necessary, it is considered to be "polite" to not hammer a server repeatedly, but rather to put a small delay between file downloads.. 39 After we have downloaded all the audio files in our list, we can add the list of URLs for the files downloaded to the permanent list. While we are at it, we should use "tail" to trim the permanent log to keep it from growing indefinitely. This limit should be several times bigger than the number of files in the RSS feed. In this case I selected 50. 40 Finally we write any errors to the permanent error log, and also write these same errors to another file used to signal errors for display to the user. We have now successfully downloaded at least one HPR podcast. 41 Notify the User of Events It would be convenient to be informed of new podcast downloads when they occur, and also be notified of any errors. One of the limitations of cron jobs is that they cannot access the user interface. This means that we cannot readily send a message directly to the notification system to inform the user of the presence of new podcasts or of errors. 42 inotifywait The solution to this is to use "inotifywait" to monitor particular files and directories for changes. The man page for inotifywait states the following - 43 inotifywait efficiently waits for changes to files using Linux's inotify(7) interface. It is suitable for waiting for changes to files from shell scripts. It can either exit once an event occurs, or continually execute and output events as they occur. End of quote. 44 In many Linux distros, inotifywait is provided by the "inotify-tools" package. I won't go over all the features of inotifywait. Instead, I will just describe how to use it for our purposes here. 45 inotifywait Modes I should point out first though that inotifywait operates in two different modes. In the normal default mode, it exits after being triggered by an event and must be re-established again in order to resume monitoring. In monitor mode, which is enabled by using the "-m" option, it runs indefinitely, responding to events. I will use the default mode here. 46 The man page for inotifywait provides a simple example that we could copy and modify for our purposes. A great many examples that you will find are based on this example. However, it doesn't quite do what we want, so we need to change a few things. 47 podfetchnotify The first shell script is one which monitors for the arrival of new podcasts and sends a notification to the user. I will call this "podfetchnotify". The complete scripts are in the show notes, I will just provide a brief description here. 48 Setting Up Event Watches Using inotifywait The script is enclosed in a while loop which run indefinitely. In the first line inside the while loop, we call inotifywait. inotifywait will then block until the event it is told to look for occurs. In short, execution of the script will wait there until an event occurs. 49 The names of the events are listed in the man file. In this case we are looking for "modify", "create", and "moved_to". Each of these does pretty much as you would expect, reacting to modifying an existing file, creating a new file, or moving a file to that directory. 50 Problems When Testing Using Text Editors I should point out that if you are testing a script which uses inotifywait, then modifying a file with a text editor may not produce the results that you may think it would. Instead it treats this as a new file with the same name, with the original file being erased. Since inotifywait attaches itself to the inode rather than the filename, it sees the file that the text editor changed as being a new file. If you wish to test this realistically, then use "echo" to overwrite the file by using I/O redirection. 51 Capturing Output In my example I capture the output from standard out into a variable, but I don't do anything with it. If you wish to for example display the name of the newly downloaded podcast file, then use the --format option along with an appropriate formatting code. There are details about this in the man page. On the next line we capture the exit code using "$?" 52 Responding to Exit Codes If the exit code was zero, then a monitored event was triggered and there should a new podcast in the directory. In this case we display a message indicating that a new podcast has arrived. I will describe how to send notifications shortly. If the exit code was not zero, then an error occurred. An example of such an error would be if the directory were not present when monitoring was started. In this case we display a message indicating that a fatal error has occurred and then exit. 53 Delay for More Podcasts Finally, we use "sleep" to wait for some arbitrary period of time to prevent notifications from being triggered multiple times if several podcasts were being downloaded in succession. In this case I chose to wait for 60 seconds. 54 We have now completed the process and can return to the top of the loop and resume waiting using inotifywait. 55 Sending Notifications to the User I mentioned above about sending notification messages to the user. In the Gnome desktop, notification messages appear from the centre of the top bar in a list. Other desktops or operating systems may have something similar. 56 To send a notification message to the notification area, you use the "notify-send" command. Simply follow notify-send with a quoted string and it will be displayed in the notification area. 57 podfetcherrornotify The second shell script is one which notifies the user of errors. I will call this "podfetcherrornotify". With this shell script we set up a watch on a file which contains any error messages from podfetch. This script is very similar to podfetchnotify. 58 The exceptions are With inotifywait we only monitor for "modify". There is no sleep command at the end of the loop. Instead we sleep for a few seconds just after getting the exit code from inotifywait. This helps prevent problems caused by race conditions. 59 Next we check the inotifywait exit code. If it was zero, then we read the error report file and send a notification message to the user containing that error message. 60 If it was not zero, then we check to make sure that the directory that should contain the error log exists. If it does not exist, then we send a notification message to that effect to the user and terminate the script. 61 If the directory exists, then we check to see if the error message file used for signalling exists. If the file does not exist, then we create it. 62 One of the reasons for an inotifywait error is that if the file that it is told to monitor does not exist, it cannot set up a watch condition. By creating the file we correct the cause of the error and allow inotifywait to operate normally. 63 Finally we increment an error counter and check to see if the limit is exceeded. If there are excessive errors, then send a notification message to the user and exit. The reason for this is to give the user an indication that the error notifications are not working for some reason and there may be a problem that needs looking into. 64 The error counter is reset every time the inotifywait exit status is ok, so occasional unexpected glitches should be something that is ignored. Of course podcast fetching errors are something that will probably happen only rarely if at all, so this final step may be seen as an unnecessary embellishment. 65 Installing the Scripts Next I will describe how to install and prepare the scripts to run. We need to perform the following steps. 66 • First, we need to create a directory to hold the scripts and their associated data files. • Next we need to create a directory to hold the downloaded podcasts. • Then we must copy the scripts to these directories and make them executable. • Then, we must edit the scripts to have the file path in the script match the locations of the new directories that we created. 67 • Then we need to install xmllint, or alternatively modify the download script to comment out the use of xmllint and enable the alternative method using grep and sed instead. • Then we need to run each script manually from the command line to check for errors. • If podfetch ran correctly, it should download the most recent 10 podcasts during this test. 68 Adding podfetch to the Crontab The above describes how to run the scripts manually. In order to fetch podcasts automatically, we need to add the podfetch script to the cron schedule. To do this, open a terminal. 69 Type "crontab -e", and then press return. A text editor should open up containing the crontab file. On Ubuntu, this editor is GNU nano. Enter the appropriate cron parameters. I will provide an example here for running it 12 minutes past the hour every three hours. 70 12 */3 * * * /home/username/pathtofiles/podfetch.sh 71 I won't explain cron in detail here. The example that I have just given should be good enough for most people. The "*/3" parameter will cause it to run every three hours. The "12" parameter will cause it to run 12 minutes past the hour when it does run. 72 Checking every three hours should be good enough for most people, but you can adjust that as you see fit. I would recommend however that you don't check more frequently than once per hour. Checking more frequently than necessary puts extra load on the distribution servers. It is very unlikely that you really do need each new episode the moment it is available. 73 I would also recommend changing the "12" parameter to some other random minute value. I would suggest avoiding on the hour or on the half hour, as a lot of other people are probably checking at those times, and it would be better to spread the load out more evenly over time. 74 The file path parameter should of course match the actual path to wherever you have located the script, including the correct user name. 75 Making the Notification Scripts Start Automatically The two notification scripts can be made to start automatically. The exact method to do this may vary according to distribution or desktop. 76 On Ubuntu this is done using the Startup Applications Preferences GUI program, which should come already installed. 77 I won't go into details on this here, it should be fairly self evident how to use it once you see it. What this program does is to create ".desktop" files in the ".config/autostart" directory in your home directory. 78 These ".desktop" files are all run automatically on start up. Once you have added the notification scripts, you will need to log out and then log back in to make them active. 79 Conclusion I this episode I explained how to write a set of simple shell scripts to automatically download each new episode of HPR as it comes out and to notify you of its arrival. 80 The download script described here is tailored specifically for use with HPR only. However, it was derived from a larger script that downloaded other podcasts as well, based on information read in from a text file. If you are feeling ambitious, you can add those features back into this to handle all of the podcasts that you listen to. 81 In a comment to another episode of HPR I had said that I would cover ID3 tags in MP3 files, but this episode is long enough now, so I will leave that subject for later. I look forward to seeing you again later on another episode of Hack Public Radio. # ====================================================================== podfetchdownloader #!/bin/bash # Fetch pending HPR podcasts listed in the HPR RSS feed. # 8-Jun-2026 # Licensed under GPLv3 or later. # ====================================================================== # Today's date and time as YYYYMMDDHHMMSS. podttimestamp=$( date +"%Y%m%d%H%M%S" ) # The absolute path to the script. This is necessary when running it # using a cron job. podpath="/home/me/Apps/hprfetch" # This is the absolute path to where to store the podcast files. podfilepath="/home/me/Music/Podcasts/HPR" # Create the full path names here for all the text files used. podcastsfetched="$podpath/podcastsfetched.txt" poderrorslog="$podpath/poderrorslog.txt" poderrorsreport="$podpath/poderrorsreport.txt" tmpoldurlssorted="$podpath/tmpoldurlssorted.txt" tmppodsnew="$podpath/tmppodsnew.txt" tmppodstodownload="$podpath/tmppodstodownload.txt" tmppodserrors="$podpath/tmppodserrors.txt" tmppodcastsfetched="$podpath/tmppodcastsfetched.txt" tmplog="$podpath/tmplog.txt" # The URL for the HPR RSS feed. PodURL="http://hackerpublicradio.org/hpr_rss.php" # Limit on number of podcasts to download. DownloadLimit=11 # Name of the podcast. PodName="Hacker Public Radio" # ====================================================================== # Check if the required paths exist. # If this path does not exist, cannot log the error. if [[ ! -d "$podpath/" ]]; then echo "$podttimestamp Error - Could not find $podfilepath." exit 1 fi # Where to store the podcast file fetched. if [[ ! -d "$podfilepath/" ]]; then echo "$podttimestamp Error - Could not find $podfilepath." >> $tmppodserrors # Copy the errors log from the temporary errors file to the permanent files. LogErrors exit 1 fi # ====================================================================== # Check if the podcast log exists. We read it before we write to it, # so it must exist or we will hang on it not being present. if [[ ! -e $podcastsfetched ]]; then touch $podcastsfetched fi # ====================================================================== # Delete the specified files if they exist. # This accepts multiple file names in a variable number of parameters. CleanupFiles () { # $@ accepts multiple parameters. for f in "$@"; do # Check if the file exists. if [ -e "$f" ]; then rm "$f" fi done } # ====================================================================== # Copy the errors log from the temporary errors file to the permanent files. LogErrors () { if [ -e $tmppodserrors ]; then # The permanent log. cat $tmppodserrors >> $poderrorslog # This file is monitored for display by other scripts. cat $tmppodserrors > $poderrorsreport fi } # ====================================================================== # Get the URL data from an RSS feed GetRSSURLData () { wget --timeout=20 --tries=3 -O - "$PodURL" | xmllint --xpath "//channel/item/enclosure/@url" - | cut -d'"' -f2 | sort > $tmppodsnew # This is an alternate method that does not use xmllint. # However, it is not as robust. If someone were to include the # first grep search pattern in their show notes, then it would # look for that as a valid tag and output the following text # as a URL. #wget --timeout=20 --tries=3 -O - "$PodURL" | grep " $poderrorsreport fi # Increment the error counter. count=$(( count + 1 )) if (( count > 3 )); then notify-send "Podfetch error: Excessive unknown errors, exiting." exit 1 fi fi done # ====================================================================== Provide feedback on this episode.

La Protectora denuncia un increment dels gats abandonats

Pastor Alan R. Knapp discusses the topic of "The Red Sea Trope" in his series entitled "Hebrews 2020: We See Jesus" This is Increment 439 and it focuses on the following verses: Hebrews 11:29

Pastor Alan R. Knapp discusses the topic of "A Move Toward Distillation" in his series entitled "Hebrews 2020: We See Jesus" This is Increment 438 and it focuses on the following verses: Acts 13:15-43; Hebrews in toto

Pastor Alan R. Knapp discusses the topic of "The Faith by Which We Live: “Abide in Him”" in his series entitled "Hebrews 2020: We See Jesus" This is Increment 437 and it focuses on the following verses: Hebrews 1:1; 11:1f; 1 John 2:20, 27

Pastor Alan R. Knapp discusses the topic of "By Faith, Moses left Egypt…" in his series entitled "Hebrews 2020: We See Jesus" This is Increment 436 and it focuses on the following verses: Hebrews 11:27-28

Conocé los datos oficiales más destacados del turismo internacional para el quinto mes del año.

Conoce más datos sobre el PIB de la República Argentina. 

Pastor Alan R. Knapp discusses the topic of "“An Emerged Doctrine: The One People of God”" in his series entitled "Hebrews 2020: We See Jesus" This is Increment 435 and it focuses on the following verses: Hebrews 11:25-26

Pastor Alan R. Knapp discusses the topic of "By Faith, Moses Left Egypt" in his series entitled "Hebrews 2020: We See Jesus" This is Increment 434 and it focuses on the following verses: Hebrews 11:24-27

Pastor Alan R. Knapp discusses the topic of "Auxesis: Moses and Jesus" in his series entitled "Hebrews 2020: We See Jesus" This is Increment 433 and it focuses on the following verses: Hebrews 11:23-26, 12:2

Càritas avisa d'un increment de la precarietat en l'habitatge al Vallès

Pastor Alan R. Knapp discusses the topic of "Living by The Faith Shown by The Son of God" in his series entitled "Hebrews 2020: We See Jesus" This is Increment 432 and it focuses on the following verses: Hebrews 11:22-23

Pastor Alan R. Knapp discusses the topic of "THE BONES OF JOSEPH" in his series entitled "Hebrews 2020: We See Jesus" This is Increment 431 and it focuses on the following verses: Hebrews 11:3-22, (especially Hebrews 11:21-22)

Pastor Alan R. Knapp discusses the topic of "H2020 in Overdrive Aqedah - Part Ten: "Each of the Sons of Joseph"" in his series entitled "Hebrews 2020: We See Jesus" This is Increment 430 and it focuses on the following verses: Hebrews 11:21

Pastor Alan R. Knapp discusses the topic of "H2020 in Overdrive Aqedah - Part Nine: “Going Back is NO OPTION”" in his series entitled "Hebrews 2020: We See Jesus" This is Increment 429 and it focuses on the following verses: Hebrews 11:8-16 especially Hebrews 11:15

Pastor Alan R. Knapp discusses the topic of "Prepared Just So" in his series entitled "Hebrews 2020: We See Jesus (2X)" This is Increment 288 and it focuses on the following verses: Hebrews 9:6-7, 11-12, 28; 10:3 et al

Pastor Alan R. Knapp discusses the topic of "H2020 in Overdrive Aqedah - Part Eight: “Jacob AND Esau?”" in his series entitled "Hebrews 2020: We See Jesus" This is Increment 428 and it focuses on the following verses: Hebrews 11:20

Pastor Alan R. Knapp discusses the topic of "H2020 in Overdrive Aqedah - Part Seven: “Reasonable Faith”" in his series entitled "Hebrews 2020: We See Jesus" This is Increment 427 and it focuses on the following verses: Hebrews 11:17-19

Pastor Alan R. Knapp discusses the topic of "SEE: Living by Faith at the Edge of the Eschaton Part Sixteen: “Abel's Sacrifice”" in his series entitled "Hebrews 2020: We See Jesus (2X)" This is Increment 411 and it focuses on the following verses: Hebrews 11:4

Pastor Alan R. Knapp discusses the topic of "H2020 in Overdrive Aqedah - Part Six: “The Only Begotten”" in his series entitled "Hebrews 2020: We See Jesus" This is Increment 426 and it focuses on the following verses: Hebrews 11:17-19

Pastor Alan R. Knapp discusses the topic of "H2020 in Overdrive Aqedah - Part Five: "The Bible Doctrine of God our Savior"" in his series entitled "Hebrews 2020: We See Jesus" This is Increment 425 and it focuses on the following verses: Titus 2:10-11; Hebrews 11:17-19

Pastor Alan R. Knapp discusses the topic of "H2020 in Overdrive Aqedah - Part Four: “The Binding”" in his series entitled "Hebrews 2020: We See Jesus" This is Increment 424 and it focuses on the following verses: Hebrews 11:4, 17-19

Pastor Alan R. Knapp discusses the topic of "H2020 in Overdrive Adequah - Part Three: “For Love of All”" in his series entitled "Hebrews 2020: We See Jesus" This is Increment 423 and it focuses on the following verses: John 3:16a; Hebrews 11:17-19

Pastor Alan R. Knapp discusses the topic of "H2020 in Overdrive Adequah - Part Two" in his series entitled "Hebrews 2020: We See Jesus" This is Increment 422 and it focuses on the following verses: Jeremiah 45:1-5; Philippians 2:3-11; Hebrews 11:14; 12:1-2

Pastor Alan R. Knapp discusses the topic of "H2020 in Overdrive Adequah - Part One" in his series entitled "Hebrews 2020: We See Jesus" This is Increment 421 and it focuses on the following verses: Hebrews In Toto; especially Hebrews 5:7, 11:17-19

Pastor Alan R. Knapp discusses the topic of "SEE: Living by Faith at the Edge of the Eschaton Part Twenty-Five: Longing for a Homeland" in his series entitled "Hebrews 2020: We See Jesus" This is Increment 420 and it focuses on the following verses: Hebrews 11:11-16, 40

Pastor Alan R. Knapp discusses the topic of "SEE: Living by Faith at the Edge of the Eschaton Part Twenty-Four: God's Memorial Name" in his series entitled "Hebrews 2020: We See Jesus" This is Increment 419 and it focuses on the following verses: Exodus 3:6, 15; Hebrews 11:8-13, 16-17

Pastor Alan R. Knapp discusses the topic of "SEE: Living by Faith at the Edge of the Eschaton Part Twenty-Three: The Theology of Faith" in his series entitled "Hebrews 2020: We See Jesus" This is Increment 418 and it focuses on the following verses: Psalm 39:1-13, 119:9; Hebrews In Toto

Pastor Alan R. Knapp discusses the topic of "SEE: Living by Faith at the Edge of the Eschaton Part Twenty-Two: From One" in his series entitled "Hebrews 2020: We See Jesus" This is Increment 417 and it focuses on the following verses: Jeremiah 14:8; Romans 5:12-21; Galatians 3:16; Hebrews 11:8-13

The Trio meet to discuss two of the talks (ours!) from the recent in-person PhillyCocoa meetup called "Beyond the Simulator: Perspectives on Modern App Development" that took place on January 29 at the Vanguard offices in Philadelphia. This pod was recorded before the event due to scheduling, but we go into detail on what you missed now that it is the future (insert Spaceballs joke here)! Kotaro talks about Liquid Glass and what it means for modern UI/UX while Steve goes into some detail about how to effectively get started using tools like Codex CLI or Claud Code for app development. Be sure to check out PhillyCocoa.org for a link to join our Slack and follow us on Luma so you know when our next in-person and virtual events are scheduled: https://luma.com/phillycocoa.## Show Notes- Introductions- IRL Meetup Follow-up (recorded before the meetup!) - Kotaro's Liquid Glass talk - Steve's Spec. Plan. Ship. “AI” assisted dev talk- Wrap-Up- One More Thing... - Monthly Zoom Call Meeting in February - Follow us on Luma: https://luma.com/phillycocoa## Chapters00:00 Introductions02:33 Beyond the Simulator IRL Event03:49 Kotaro's Talk: Liquid Glass and Modern UI/UX Trends11:25 Liquid Glass Encourages Gesture-Based Interactions16:18 Branding Challenges in Liquid Glass UI19:31 Steve's Talk: Spec. Plan. Ship21:47 The Four I Workflow: Intent, Interact, Increment, Iterate28:59 Continuously Iterate on Your System33:17 Steve's Tips for Getting Started41:51 Best Practices for Using AI in Development46:20 Wrap-Up46:38 One More Thing...47:59 TagIntro music: "When I Hit the Floor", © 2021 Lorne Behrman. Used with permission of the artist.

Pastor Alan R. Knapp discusses the topic of "SEE: Living by Faith at the Edge of the Eschaton Part Twenty-One: The Wanderers" in his series entitled "Hebrews 2020: We See Jesus" This is Increment 416 and it focuses on the following verses: Hebrews 11:1-11, 13-16, 37

Pastor Alan R. Knapp discusses the topic of "SEE: Living by Faith at the Edge of the Eschaton Part Twelve: What is Your Aim?" in his series entitled "Hebrews 2020: We See Jesus (2X)" This is Increment 407 and it focuses on the following verses: 2 Corinthians 5:6-10, 19-21; Hebrews 11:2, 5-6

Pastor Alan R. Knapp discusses the topic of "The Three Appearings and the Triple-Hapax" in his series entitled "Hebrews 2020: We See Jesus (2X)" This is Increment 320 and it focuses on the following verses: Hebrews 9:24-28

Pastor Alan R. Knapp discusses the topic of "SEE: Living by Faith at the Edge of the Eschaton Part Twenty: Faith as Being Moved and Moving" in his series entitled "Hebrews 2020: We See Jesus" This is Increment 415 and it focuses on the following verses: Hebrews 11:1-10, 16, 31, 12:22, 13:10-14

Pastor Alan R. Knapp discusses the topic of "SEE: Living by Faith at the Edge of the Eschaton Part Nineteen: Abel's Sacrifice III" in his series entitled "Hebrews 2020: We See Jesus" This is Increment 414 and it focuses on the following verses: Hebrews 10:38; 11:3-4

Pastor Alan R. Knapp discusses the topic of "SEE: Living by Faith at the Edge of Eschaton Part Eighteen: Abel's Sacrifice II" in his series entitled "Hebrews 2020: We See Jesus" This is Increment 413 and it focuses on the following verses: Hebrews 11:4; James 2:17, 21-23, 25-26

Pastor Alan R. Knapp discusses the topic of "SEE: Living by Faith at the Edge of the Eschaton Part Seventeen: God's Divisive Judgment" in his series entitled "Hebrews 2020: We See Jesus" This is Increment 412 and it focuses on the following verses: Matthew 25:31-46; John 9:39, 12:47-50; Hebrews 11:4

Pastor Alan R. Knapp discusses the topic of "We See Jesus's Eyes" in his series entitled "Hebrews 2020: We See Jesus (2X)" This is Increment 110 and it focuses on the following verses: Hebrews 4:12-14, 19:14 cf. Matthew 9:4; Mark 10:17-22

Pastor Alan R. Knapp discusses the topic of "SEE: Living by Faith at the Edge of the Eschaton Part Sixteen: Abel's Sacrifice" in his series entitled "Hebrews 2020: We See Jesus" This is Increment 411 and it focuses on the following verses: Hebrews 11:4