HPR4344: 24-25 New Years Eve show episode 4

27 mars 2025 | min

HPR4343: Interviewing the Redot engine Founder

26 mars 2025 | min

HPR4342: How I use Git to blog on the web and gopherspace

25 mars 2025 | min

This show has been flagged as Clean by the host.

First, I create a Git repository some place on the server. This is the Git repo that's going to be populated with your content, but it doesn't have to be in a world-viewable location on your server. Instead, you can place this anywhere, and then use a Git hook or a cronjob to copy files from it to a world-viewable directory. I don't cover that here. I refer to this location as the staging directory.

Next, create a bare repository on your server. In its hooks directory, create a shell script called post-receive:

#!/usr/bin/bash
#
while read oldrev newrev refname
do
       BR=`git rev-parse --symbolic --abbrev-ref $refname`
       if [ "$BR" == "master" ]; then
               WEB_DIR="/my/staging/dir"
               export GIT_DIR="$WEB_DIR/.git"
               pushd $WEB_DIR > /dev/null
               git pull
               popd > /dev/null
       fi
done

Now when you push to your bare repository, you are triggering the post-receive script to run, which in turn triggers a git pull in your staging directory.

Once your staging directory contains the content you want to distribute, you can copy them to live directories, or you could make your staging directory live (remember to exclude the .git directory though), or whatever you want.

For gopher, I create a file listing by date using a shell script:

#!/usr/bin/bash
SED=/usr/bin/sed
DIR_BASE=/my/live/dir
DIR_LIVE=blog
DIR_STAGING=staging
DATE=${DATE:-`date --rfc-3339=date`}
for POST in `find "$DIR_BASE"/"$DIR_STAGING" \
-type f -name "item.md" -exec grep -Hl "$DATE" {} \;`;
do 
POSTDIR=`dirname "$POST"`
cp "$POST" "$DIR_BASE"/"$DIR_LIVE"/`basename $POSTDIR`.txt
echo -e 0Latest'\t'../"$DIR_LIVE"/`basename $POSTDIR`.txt > /tmp/updater.tmp

echo -e 0"$DATE" `basename $POSTDIR`'\t'../"$DIR_LIVE"/`basename $POSTDIR`.txt \
>> /tmp/updater.tmp
"${SED}" -i "/0Latest/ r /tmp/updater.tmp" "$DIR_BASE"/date/gophermap
"${SED}" -i '0,/0Latest/{/0Latest/d;}' "$DIR_BASE"/date/gophermap
/usr/bin/rm /tmp/updater.tmp
done

Provide feedback on this episode.

HPR4341: Transferring Large Data Sets

24 mars 2025 | min

This show has been flagged as Clean by the host.

Transferring Large Data Sets

Very large data sets present their own problems. Not everyone has directories with hundreds of gigabytes of project files, but I do, and I assume I'm not the only one.

For instance, I have a directory with over 700 radio shows, many of these directories also have a podcast, and they also have pictures and text files.

Doing a properties check on the directory I see 450 gigabytes of data.

When I started envisioning Libre Indie Archive I wanted to move the directories into archival storage using optical drives. My first attempt at this didn't work because I lost metadata when I wrote the optical drives since optical drives are read only.

After further work and study I learned that tar files can preserve meta data if they are created and uncompressed as root. In fact, if you are running tar as root preserving file ownership and permissions is the default.

So this means that optical drives are an option if you write tar archives onto the optical drives.

I have better success rates with 25 GB Blue Ray Discs than with the 50 GB discs. So, if your directory breaks up into projects that fit on 25 GB discs, that's great.

My data did not do this easily but tar does have an option to write a data set to multiple tar files each with a maximum size, labelling them -0 -1, etc.

When using this multi volume feature you cannot use compression. So you will get tar files, not tar.gz files.

It's better to break the file sets up in more reasonable sizes so I decided to divide the shows up alphabetically by title, so all the shows starting with the letter a would be one data set and then down the alphabet, one letter at a time.

Most of the letters would result in a single tar file labeled -0 that would fit on the 25 GB disc. Many letters, however, took two or even three tar files that would have to be written on different disks and then concatenated on the primary system before they are extracted to the correct location in primaryfiles.

There is a companion program to tar, called tarcat, that I used to combine 2 or 3 tar files split by length into a single tar file that could be extracted.

I ran engrampa as root to extract the files.

So, I used a tar command on the working system where my Something Blue radio shows are stored. Then I used K3b to burn these files onto a 25 GB Blu Ray Disc carefully labeling the discs and writing a text file that I used to keep up with which files I had already copied to Disc.

Then on the Libre Indie Archive primary system I copied from the Blu Ray to the boot drive the file or files for that data set. Then I would use tarcat to combine the files if there was more than one file for that data set. And finally I would extract the files to primaryfiles by running engrampa as root.

Now I'm going to go into details on each of these steps.

First make sure that the Libre Indie Archive program, prep.sh, is in your home directory on your workstation. Then from the data directory to be archived, in my case the something_blue directory run prep.sh like this.

~/prep.sh

This will create a file named IA_Origin.txt that lists the date, the computer and directory being archived, and the users and userids on that system. All very helpful information to have if at some time in the future you need to do a restore.

Next create a tar data set for each letter of the alphabet. (You may want to divide your data set in a different way.)

Open a terminal in the same directory as the data directory, my something_blue directory, so that ls displays something_blue (your data directory). I keep the Something Blue shows and podcasts in subdirectories in the something_blue directory.

Here's the tar command.

Example a:

sudo tar -cv --tape-length=20000000 --file=somethingblue-a-{0..50}.tar /home/larry/delta/something_blue/a*

This is for the letter a so the --file parameter includes the letter a. The numbers 0..50 in the squirelly brackets are the sequence numbers for the files. I only had one file for the letter a, somethingblue-a-0.tar.

The last parameter is the source for the tar files, in this case

/home/larry/delta/something_blue/a*

All of the files and directories in the something_blue directory that start with the letter a.

You may want to change the --tape-length parameter. As listed it stores up to 19.1 GB. The maximum capacity of a 25 GB Blu-ray is 23.3GB for data storage.

Example b:

For the letter b, I ended up with three tar files.

somethingblue-b-0.tar
somethingblue-b-1.tar
somethingblue-b-2.tar

I will use these files in the example below using tarcat to combine the files.

I use K3b to burn Blu-Ray data discs. Besides installing K3b you have to install some other programs and then there is a particular setup that needs to be done including selecting cdrecord and no multisession. Here's an excellent article that will go step by step through the installation and setup.

How to burn Blu-ray discs on Ubuntu and derivatives using K3b?

https://en.ubunlog.com/how-to-burn-blu-ray-discs-on-ubuntu-and-derivatives-using-k3b/

I also always check Verify data and I use the Linux/Unix file system, not windows which will rename your files if the filenames are too long.

I installed a Blu-Ray reader into the primary system and I used thunar to copy the files from the Blu-Ray Disc to the boot drive.

In the primaryfiles directory I make a subdirectory, something_blue, to hold the archived shows.

If there is only one file, like in example a above, you can skip the concatenation step.

If there is more than one file, like Example b above, you use tarcat to concatenate these files into one tar file.

You have to do this. If you try to extract from just one of the numbered files when there is more than one you will get an error. So if I try to extract from somethingblue-b-0.tar and I get an error it doesn't mean that there's anything wrong with that file. It just has to be concatenated with the other b files before it can be extracted.

There is a companion program to tar called tarcat that should be used to concatenate the tar files.

Here's the command I used for example b, above.

tarcat somethingblue-b-0.tar somethingblue-b-1.tar somethingblue-b-2.tar > sb-b.tar

This will concatenate the three smaller tar files into one bigger tar file named sb-b.tar

In order to preserve the meta data you have to extract the files as root. In order to make it easier to select the files to be extracted and where to store them I use the GUI archive manager, engrampa. To run engrampa as root open a terminal with CTRL-ALT t and use this command

sudo -H engrampa

Click Open and select the tar file to extract. Then follow the path until you are in the something_blue directory and you are seeing the folders and files you want to extract. Type Ctrl a to select them all. (instead of the something_blue directory you will go to your_data directory)

Then click Extract at the top of the window. Open the directory where you want the files to go. In my case, primaryfiles/something_blue

Then click Extract again in the lower right.

After the files are extracted go to your data directory in primaryfiles and check that the directories and files are where you expect them to be.

You can also open a terminal in that directory and type

ls -l

to review the meta data.

When dealing with data chunks sized 20 GB or more each one of these steps takes time. The reason I like using an optical disk backup to transfer the files from the working system to Libre Indie Archive is because it gives me an easy to store backup that is not on a spinning drive and that cannot be overwritten. Still optical disk storage is not perfect either. It's just another belt to go with your suspenders.

Another way to transfer directories into the primaryfiles directory is with ssh over the network. This is not as safe as using optical disks and it also does not provide the extra snapshot backup. It also takes a long time but it is not as labor intensive.

After I spend some more time thinking about this and testing I will do a podcast about transferring large data sets with ssh.

Although I am transferring large data sets to move them into archival storage using Libre Indie Archive there are many other situations where you might want to move a large data set while preserving the meta data. So what I have written about tar files, optical discs, and running thunar and engrampa as root is generally applicable.

As always comments are appreciated. You can comment on Hacker Public Radio or on Mastodon. Visit my blog at home.gamerplus.org where I will post the show notes and embed the Mastodon thread for comments about thie podcast.

Thanks

Provide feedback on this episode.

HPR4340: Playing Civilization IV, Part 7

21 mars 2025 | min

HPR4339: Review of the YR01 smart lock

20 mars 2025 | min

HPR4338: 328eforth

19 mars 2025 | min

This show has been flagged as Clean by the host.

Review of the book the Arduino controlled by eforth by dr chen-hanson ting published in 2018

written by chen-hanson ting

Late Dr. ting was a chemist turned engineer. he earned a phd in chemistry at the U of Chicago in 1965. taught chemistry in Taiwan until 1975. became a firmware engineer until hI retirement in 2000. he was a forth advocate for more than 50 years, especially a forth called eforth that has been ported to many devices, including the micro chip atmega 328 found on the arduino uno board.

I found this book while searching for forths for the arduino uno boards. the source code and documentation for eforth is available in a lot of places I will put a few links in the show notes.

I believe I mentioned this forth in an earlier hpr where I talked about choosing a forth.

forth interest group https://forth.org

https://wiki.forth-ev.de

https://chochain.github.io (pdf)

When I first encountered dr tings forth for arduino I was interested for one reason, it was easily assembled using avra, the gnu port of the atmel assembler. this was nice because using atmels (now microchips) assemblers on Linux required installing wine and installing wine, in the past, on a 64 bit Slackware meant installing 32 bit libraries to have a multI lib Slackware. ( that not an issue now). assembling the forth code in avra is quick, its only a little bit over 5k in size in the end.

After playing with eforth for a while I became frustrated because I could create new words in the dictionary and the examples ran fine, but nothing persisted across reboot. so I dropped eforth and ended up using flashforth, which is a great, robust full featured forth. I still recommend flashforth if your starting out with forth on a microcontroller its solid software with good documentation.

At the end of last year I thought it would be fun to write my own forth. and after looking into doing that I revisited 328eforth and thought, no how about I fix the problems with eforth on the arduino. so I dug out the book and began reading.

Jones forth port at https://ratfactor.com/nasmjf

The book has 6 parts.

part 1 is dr tings musings on how he ended up creating 328eforth.

part 2 explains installing eforth.

the 3rd part begins exercising the arduino board using forth in the interactive interpreter.

part 4 explains 328eforth implementation and design decisions.

part 5 is the full commented source code of 328eforth and, this is the best part, dr tings explanation of what is going on in the code broken down by functional sections. a gold mine of information!

part 6 conclusions

The last part is his conclusions and examples to learn forth.

This is a great free software project. nothing is hidden. it is accessible to anybody who would take the time to read and dig into the code. its makes assembly language much less dark and foreboding.

I'll finish by reading a couple of paragraphs from dr tings book

dr ting concludes:

People using computers are trained to be slaves. You are taught to push certain buttons, and your are taught to push certain keys. Then, you get employed to push buttons and keys to work as slaves. Computers, programming languages, and operating systems are made complicated to enslave people.

Computers are not complicated beyond comprehension. Programming languages and operating systems do not have to be complicated. If you get a sharp knife, you can be the master of your destination. 328eforth is a sharp knife. Go use it.

The hacker ethos.

The next podcast I produce will cover installing eforth on an arduino board and solving that pesky loss of words between boots problem.

Provide feedback on this episode.

HPR4337: Open Web UI

18 mars 2025 | min

This show has been flagged as Explicit by the host.

OpenWebUI notes ...

Open WebUI installer: https://github.com/freeload101/SCRIPTS/blob/master/Bash/OpenWebUI_Fast.bash

Older Professor synapse prompt you can use: https://raw.githubusercontent.com/freeload101/SCRIPTS/refs/heads/master/Prof%20Synapse%20Old.txt

Fabric prompts you can import into openwebui !!! ( https://github.com/danielmiessler/fabric/tree/main/patterns ) https://github.com/freeload101/SCRIPTS/blob/master/MISC/Fabric_Prompts_Open_WebUI_OpenWebUI_20241112.json

Example AT windows task startup script to make it start and not die on boot https://github.com/freeload101/SCRIPTS/blob/master/MISC/StartKokoro.xml

Open WebUI RAG fail sause ... https://youtu.be/CfnLrTcnPtY

Open registration

Model list / order

NAME                                                   ID              SIZE      MODIFIED

hf.co/mradermacher/L3-8B-Stheno-v3.2-i1-GGUF:Q4_K_S    017d7a278e7e    4.7 GB    2 days ago

qwen2.5:32b                                            9f13ba1299af    19 GB     3 days ago

deepsex:latest                                         c83a52741a8a    20 GB     3 days ago

HammerAI/openhermes-2.5-mistral:latest                 d98003b83e17    4.4 GB    2 weeks ago

Sweaterdog/Andy-3.5:latest                             d3d9dc04b65a    4.7 GB    2 weeks ago

nomic-embed-text:latest                                0a109f422b47    274 MB    2 weeks ago

deepseek-r1:32b                                        38056bbcbb2d    19 GB     4 weeks ago

psyfighter2:latest                                     c1b3d5e5be73    7.9 GB    2 months ago

CognitiveComputations/dolphin-llama3.1:latest          ed9503dedda9    4.7 GB    2 months ago

Disable Arena models

Documents WIP RAG is not good .

Discord notes;

https://discord.com/channels/1170866489302188073/1340112218808909875

Abhi Chaturvedi: @(Operat0r) try this To reduce latency and improve accuracy, modify the .env file: Enable RAG ENABLE_RAG=true
Use Hybrid Mode (Retrieval + Reranking for better context)
RAG_MODE=hybrid
Reduce the number of retrieved documents (default: 5)
RETRIEVAL_TOP_K=3
Use a Fast Embedding Model (instead of OpenAI's Ada-002)
EMBEDDING_MODEL=all-MiniLM-L6-v2 # Faster and lightweight . Optimize the Vector Database VECTOR_DB_TYPE=chroma CHROMA_DB_IMPL=hnsw # Faster search CHROMA_DB_PATH=/root/open-webui/backend/data/vector_db. Optimize Backend Performance # Increase Uvicorn worker count (improves concurrency) UVICORN_WORKERS=4
Increase FastAPI request timeout (prevents RAG failures)
FASTAPI_TIMEOUT=60
Optimize database connection pool (for better query performance)
SQLALCHEMY_POOL_SIZE=10
So probably the first thing to do is increase the top K value in admin -> settings -> documents, or you could try the new "full context mode" for rag documents. You may also need to increase the context size on the model, but it will make it slower, so you probably don't want to do that unless you start seeing the "truncating input" warnings.
@JamesK
So probably the first thing to do is increase the top K value in admin -> settings -> documents, or you could try the new "full context mode" for rag documents. You may also need to increase the context size on the model, but it will make it slower, so you probably don't want to do that unless you start seeing the "truncating input" warnings.
M]
JamesK: Ah, I see. The rag didn't work great for you in this prompt. There are three hits and the first two are duplicates, so there isn't much data for the model to work with
[9:12 PM] JamesK: context section
I see a message warning that you are using the default 2048 context length, but not the message saying you've hit that limit (from my logs the warning looks like
level=WARN source=runner.go:126 msg="truncating input prompt" limit=32768 prompt=33434 numKeep=5
[6:06 AM] JamesK: If you set the env var OLLAMA_DEBUG=1 before running ollama serve it will dump the full prompt being sent to the model, that should let you confirm what the rag has put in the prompt
JamesK: Watch the console output from ollama and check for warnings about overflowing the context. If you have the default 2k context you may need to increase it until the warnings go away
[8:58 PM] JamesK: But also, if you're using the default rag, it chunks the input into small fragments, then matches the fragments against your prompt and only inserts a few fragments into the context, not the entire document. So it's easily possible for the information you want to not be present.

Auto updates

echo '0,12 */4 * * * docker run --rm --volume /var/run/docker.sock:/var/run/docker.sock containrrr/watchtower --run-once open-webui' >> /etc/crontab

Search

red note for API keys

Go to Google Developers, use Programmable Search Engine , and log on or create account.
Go to control panel and click Add button
Enter a search engine name, set the other properties to suit your needs, verify you're not a robot and click Create button.
Generate API key and get the Search engine ID . (Available after the engine is created)
With API key and Search engine ID , open Open WebUI Admin panel and click Settings tab, and then click Web Search
Enable Web search and Set Web Search Engine to google_pse
Fill Google PSE API Key with the API key and Google PSE Engine Id (# 4)
Click Save

Note

You have to enable Web search in the prompt field, using plus ( + ) button. Search the web ;-)

Kokoro / Open Webui

https://docs.nvidia.com/datacenter/cloud-native/container-toolkit/latest/install-guide.html

https://github.com/remsky/Kokoro-FastAPI?tab=readme-ov-file

apt update

apt upgrade

curl -fsSL https://nvidia.github.io/libnvidia-container/gpgkey | sudo gpg --dearmor -o /usr/share/keyrings/nvidia-container-toolkit-keyring.gpg   && curl -s -L https://nvidia.github.io/libnvidia-container/stable/deb/nvidia-container-toolkit.list |     sed 's#deb https://#deb [signed-by=/usr/share/keyrings/nvidia-container-toolkit-keyring.gpg] https://#g' |     sudo tee /etc/apt/sources.list.d/nvidia-container-toolkit.list

sed -i -e '/experimental/ s/^#//g' /etc/apt/sources.list.d/nvidia-container-toolkit.list

sudo apt-get update

sudo apt-get install -y nvidia-container-toolkit

apt install docker.io -y

docker run --gpus all -p 8880:8880 ghcr.io/remsky/kokoro-fastapi-gpu:v0.2.2

http://localhost:8880/v1

af_bella

Import fabric prompts

https://raw.githubusercontent.com/freeload101/Python/46317dee34ebb83b01c800ce70b0506352ae2f3c/Fabric_Prompts_Open_WebUI_OpenWebUI.py

Provide feedback on this episode.

HPR4336: The Everything-I-Know 20-minutes Show

17 mars 2025 | min

This show has been flagged as Clean by the host.

In here:

1- Carrying weight more safely

- When picking up weight in front of your body, embrace the core (tighten the abdomen);

- it gives you more stability, so you are more capable to do the task.

2- Microphone types

a) by connection

i) USB: connects directly to the computer, in the universal serial bus port. Plug and use!

ii) XLR: needs a USB audio interface , with XLR input, to connect to the computer. There are more options of microphones and, if you can spend on an interface, quality is generally better.

XLR connectors: female (left) and male. ( Image by Michael Piotrowski / Wikimedia Commons – CC BY-SA 3.0 .)

b) by diaphragm

i) condenser: captures the voice in more detail, with deeper bass, more detailed treble… Most of the USB microphones uses this technology. As a disadvantage, they catch even minimal sound details of the environment, vibrating with little sound waves around, even distant. That’s why you might get as recording result the clear details of noise from the street, or reverberation (echo) of an untreated room if you use it without the best environment. (If it’s ok for you even in these situations, it’s a merit of other factors, not a merit of the condenser diaphragm) . Usage : A favorite of singers in studio, among several other applications. As you can see on videos of professionals singing, one don’t talk on top of it (which might produce a low and undesired muffled sound) but on the side — and on the correct side, because most models of microphones have a cardioid pollar pattern.

A side-adress microphone (captures the sound from one specific side), condenser-type. (Image by Arthur Fox / https://mynewmicrophone.com/diaphragm.)

ii) dynamic: responds to the audio source (voice, instrument) very close to the diaphragm, do not capture sound more than some centimeters (or some inches) away. It’s the best for amateur use, or in a room without acoustic treatment. Usage : Musicians performing live use dynamic microphones so the instruments (and crowd) around don’t get their sound amplified by this artist’s microphone. Radios prefer dynamic mics, because it goes to a more impactful voice, rejects eventual sounds from noisy mixers or keyboards nearby that the radio host might be operating.

A top-adress microphone (captures the sound from the top), dynamic-type. (Image by Arthur Fox / https://mynewmicrophone.com/diaphragm.)

The RE20 from Electro-Voice (not the photo above) is a favorite of radio stations, in part for being dynamic, in part for reducing the proximity effect (that is, the sound “exploding” when the source gets too near to the capsule) because of its technology, named Variable-D.

A word about captation pattern (no, the name is polar pattern): it says about the directional response. For example, some are omnidirectional (captures sound equally from all the sides); most of them are cardioid, capturing the sound coming from the front (the speaker, the instrument directed to it), but rejects sound from the rear.

3- Microsoft Word (or Libreoffice Writer) “templates”

- So, you do use templates for text archives, to facilitate the doing of commonly used documents. To know what to change, you highlight in yellow, right? Or do you put the text in red?

- Well, my recommendation is to use, instead, * or {} : asterisk, curly brackets or any other symbol that you can type easily and not use as text in any document.

. So you can easily find what is the part you have to change or write, and only delete the * when you do that part. At the end, you can check if there is any * remaining, if not, the document is ready.

- So, isnt’ it the same with colors, to indicate what to change in the document?

. No. For formatting you need to use your vision (and may lose something) and have to remove the formatting manually. It’s possible to use the Find tool, but not as easily as finding a character.

To illustrate: print of an official document template for the bidding process for information and communication technology services. (Author: Brazil, Advocacia-Geral da União. Modelos da Lei 14.133/21 para bens e serviços de TIC. Link: https://www.gov.br/agu/pt-br/composicao/cgu/cgu/modelos/licitacoesecontratos/14133/bens-e-servicos-de-tic). Changes to be made were marked in red and italics, but brackets [] and “XXXX” were used also.

- Ah:

. there are forms, real templates you can use, but, hey, if you're part of the 90% that saves “templates” in the common format (.docx, .odt) and does not use the very special tools for the template kind of document, knowing and using some tips like this is ok and is satisfying.

- Not on templates, but in editing, I have worked on the revision of books using this, to know where to come back later to check, or where I have stopped on some day, with good result. Extra: give a look on the comment options, they are easy to use and practical, see if you adapt with it for your necessities.

4- A recooording tip

- Always record at least 3 seconds, totally quiet, before starting the show (that is, before talking). This “silence” is the room tone, which you may use:

. as adequate silence in the editing proccess (in place of a cut part), or

. you may take it for noise reduction profile IF needed, or

. which you can only delete in the end if you don't find what to do with it.

- Recording knowledge number 2 and final: save an uncompressed version of the raw of your recording, and keep it intact. Work on copies, keep the original saved as .wav (or, if prefered, .flac).

5- Permissions for apps

Be careful with free apps. Don’t install any and everything. See their permissions.

- Ads? Why more things being offered to you, trying to give insatisfaction? If there is an option without ads, you may prefer.

. Also, the ad system of some apps uses more battery (downloading different ads, sending more information of you to personalize ads, using the notification system, meaning running in the background).

- In-app purchases: with it, you’ll get angry with an app, because it’s not free to do what you thought it would do when you installed. And it may use recurring payments, pay for each feature, and worst, you don’t know beforehand. If it’s to pay, prefer the ones you buy (once) in the download and has no in-app purchases.

- With apps in that you input your data (like e2ee, or “e2ee” communicating, or browsers): see permissions, what data they keep and share, or at least choose open source and well-renowed developers.

- Please don't download any app that promises performance enhancement. The system (Android or iOS) is already optimized for what it is, third party apps can do little or, most commonly, nothing, and is more space and features loading your system.

. Want speed? Delete the apps that are not absolutely necessary (I’m talking to you, solitaire game with access to internet and that notifies you to play from time to time), or disable notifications of every app and put them to deep sleep (so they don’t run in background, only when you open them).

- So much said, let’s take it in one sentence: install only what needed, and see permissions and ads before choosing.

6- Mobile phone battery

- You use your phone all day and still have more than 20% of battery? Or recharges 2 times a day? (or 3!)

- If it’s the last option, and your phone is less than 3 years old and you never use uncertified chargers, you can try to have a worry-free all-day phone usage doing what said before: disabling apps that run in the background (uninstall, or put to deep sleep). It’s a one by one process, but once for all.

. If it’s this way because of intense use, nothing to do; enjoy your product!

✶ Final word

We did not enter on details: no explanations or reasons abounding, no. We didn’t even go to number 7 , which would be perfection ; because I have not a seventh good idea.

Only the bits of what I think I know & that I value as precious. A hug!

bye!

Credits: sound used (author – sound)

luvvoice.com , English (Nigeria), Abeo (Male) voice – tts “20 minutes show”.

luvvoice.com , English (UK), Ryan (Male) voice – tts on the paragraph about polar pattern of microphones.

Crab_Audio / Pixabay – My Style [Transitions]

freesound_community / Pixabay – Dictaphone .

Robinhood76 / Freesound.org – 01893 do it again spell (CC-BY-NC 4.0).

attic13 / Pixabay – calm background piano [beautiful, thank you; I hope the simple use here honors your work, friend].

SieuAmThanh / Freesound.org – RớtĐônHổ [angry expression] (CC0 1.0).

patchen / Freesound.org – Beautiful 85 (CC BY 4.0).

Provide feedback on this episode.

HPR4335: Responce to Antoin's H P R 4 3 1 3

14 mars 2025 | min

Hacker Public Radio

Hacker Public Radio is an podcast that releases shows every weekday Monday through Friday.

Om podden

Avsnitt

HPR4344: 24-25 New Years Eve show episode 4

HPR4343: Interviewing the Redot engine Founder

HPR4342: How I use Git to blog on the web and gopherspace

HPR4341: Transferring Large Data Sets

Transferring Large Data Sets

HPR4340: Playing Civilization IV, Part 7

Links:

HPR4339: Review of the YR01 smart lock

HPR4338: 328eforth

Review of the book the Arduino controlled by eforth by dr chen-hanson ting published in 2018

written by chen-hanson ting

HPR4337: Open Web UI

OpenWebUI notes ...

Open registration

Disable Arena models

Documents WIP RAG is not good .

Discord notes;

Auto updates

Search

Note

Kokoro / Open Webui

HPR4336: The Everything-I-Know 20-minutes Show

1- Carrying weight more safely

2- Microphone types

a) by connection

b) by diaphragm

3- Microsoft Word (or Libreoffice Writer) “templates”

4- A recooording tip

5- Permissions for apps

6- Mobile phone battery

✶ Final word

HPR4335: Responce to Antoin's H P R 4 3 1 3

Hacker Public Radio

Hacker Public Radio is an podcast that releases shows every weekday Monday through Friday.

Om podden

Avsnitt

HPR4344: 24-25 New Years Eve show episode 4

HPR4343: Interviewing the Redot engine Founder

HPR4342: How I use Git to blog on the web and gopherspace

HPR4341: Transferring Large Data Sets

Transferring Large Data Sets

HPR4340: Playing Civilization IV, Part 7

Links:

HPR4339: Review of the YR01 smart lock

HPR4338: 328eforth

Review of the book the Arduino controlled by eforth by dr chen-hanson ting published in 2018

written by chen-hanson ting

HPR4337: Open Web UI

OpenWebUI notes ...

Open registration

Disable Arena models

Documents WIP RAG is not good .

Discord notes;

Auto updates

Search

Note ​

Kokoro / Open Webui

HPR4336: The Everything-I-Know 20-minutes Show

1- Carrying weight more safely

2- Microphone types

a) by connection

b) by diaphragm

3- Microsoft Word (or Libreoffice Writer) “templates”

4- A recooording tip

5- Permissions for apps

6- Mobile phone battery

✶ Final word

HPR4335: Responce to Antoin's H P R 4 3 1 3

Note