table td.shrink {

white-space:nowrap

}

New hosts

Welcome to our new host:

enistello.

Last Month's Shows

Id

Day

Date

Title

Host

3761

Mon

2023-01-02

HPR Community News for December 2022

HPR Volunteers

3762

Tue

2023-01-03

Existence is pain

operat0r

3763

Wed

2023-01-04

The Baader-Meinhof Phenomenon

Mike Ray

3764

Thu

2023-01-05

My text-focused journey into tech

enistello

3765

Fri

2023-01-06

Fixing clock events in GBA pokemon cartridges

Celeste

3766

Mon

2023-01-09

ACER Nitro 5 laptop review

Bookewyrmm

3767

Tue

2023-01-10

LP article from Wikipedia

Archer72

3768

Wed

2023-01-11

Jeep Ignition Repair

Stache_AF

3769

Thu

2023-01-12

Crouching laptop, hidden server (part 0).

Some Guy On The Internet

3770

Listen to me cook / fail / hack Boba Green Tea!

Links

Wikipedia's

article on Bubble or Boba tea

Many services implement 2FA (Two factor authentication) by sending

you a OTP (One Time Password) using an SMS with a random code, but this

forces you to give them your valuable phone number. What alternatives do

exist?

Let's dive into the HOTP,

used by some banks years ago through a physical token and the recent TOTP,

which both let you generate completely offline codes without

using any phone number or any other personal detail. They use the HMAC technique usually

with a SHA-1 one-way hashing function, but other hashing functions can

be used too.

Useful links:

a little visual explanation I found here

Aegis

android OTP generator

use TOTP in KeepassXC for a desktop generator guide

Let's keep Webauthn maybe for a

future episode, I'm still exploring it and have to do more research.

Accessibility,

and Navigating the HPR Web Pages with a Screen Reader

Some time in the last year there has been some discussion on the HPR

mailing list about some of the problems I was having, particularly with

the tags page, on the HPR site.

Here is a show in which you can hear both me and my screen reader, as

I navigate the HPR home page, and then the HPR tags page.

Dave Morriss has made a nice job of fixing the issues I had, and made

the tags page a lot more friendly for blind and visually impaired

users.

It's quite a long podcast, and it took a lot of editing. So most of

the polish wore off by the time I 'finished' it and decided enough was

enough.

Wikipedia

article

The Joule Thief is a delightfully simple circuit that can light an

LED that requires 2V or more from a battery that is depleted to 1V or

less. There are three components in addition to the battery and LED: an

NPN transistor, a resistor and a double wound inductor. The key thing

about the inductor is that the same core shares two windings but in

opposite directions.

The explanation of how it works is simple enough, as long as you

already understand how inductors and transistors work. In other words,

it isn't simple at all! In short, the double wound inductor and

transistor conspire to generate a transient high voltage spike and so

turn LED on and off so rapidly that the human eye cannot perceive

it.

The idea of such a circuit is approaching its centenary but the name

itself is only around 20 years old. I recommend you check out Big Clive's web site as it was

he who came up with the name "Joule Thief". I also recommend this video in

which he constructs a circuit using some ninja-level soldering

skills.

One of the things I love about the Fediverse is that there is constant activity and development. As I mentioned in the previous report on Bookwyrm, it is not unusual to return to an app a few months later and see new features have been added that make it better. In this report I want to highlight three news stories that I think may be of interest.

Links:

https://www.starshipchangeling.net/mastodon/

https://www.theverge.com/2018/8/31/17801404/mastodon-harassment-wil-wheaton-mobs-twitter

https://fediverse.info/

https://golangexample.com/gotosocial-a-fediverse-server-project-written-in-golang/

https://apps.apple.com/us/app/metatext/id1523996615

https://wordpress.org/plugins/activitypub/

https://www.zwilnik.com/better-social-media/bookwyrm/

Hello Hacker Public Radio fans. This is Trey, and I am throwing this

recording together for several reasons:

The queue of shows is abysmally sparse. There are far more

openings for shows in the next few weeks than there are shows

posted.

This show is a pitiful excuse for why I haven't posted any shows

recently

If you like what you hear on Hacker Public Radio, please express your

gratitude by recording your own show. It doesn't need to be long, or

sound professional, or anything. Introduce yourself and share something

you find interesting.

If you do not like any or all of what you hear on Hacker Public

Radio, then it is the perfect opportunity for you to take a few minutes

and record a short (or long) podcast of your own which "fills the gap"

of what you might feel is needed on HPR.

Alright. Enough preliminaries.

A long time ago, at an undisclosed university far, far away, I took

my first class about Ethics. One of the things I remember most was the

question of "Just because you can do a thing, does that mean you should

do the thing?"

This was applied to many different scenarios - from nation states

building weapons of mass destruction, to authoring computer viruses, and

even to saying what you are thinking at any given moment.

It should quickly become obvious that you should not always do a

thing simply because you can do it. And today, I would like to relate

that to DIY home improvement projects, especially as we work our way up

in years.

For regular listeners, you may recall my series "Everything You

Always Wanted to Knox about PEX" recorded and shared in May through July

of 2022 (hpr3604, hpr3614, hpr3624 & hpr3634). In

this series, I recounted the process of replumbing my home using PEX

with helpful advice for anyone else who wants to try it. What I did not

realize at the time I was doing the project was the toll that doing so

much work overhead, by myself, was taking on my old shoulder joints. It

was only one straw, but a rather significant one, which eventually broke

the camel's back. Or, in my case, resulted in several severe tears in my

rotator cuff and bicep tendon.

Therapy was marginally effective, and surgery was eventually required

to put things back together the way they belonged. My effort to save

money and do the project myself "Because I could" helped lead to

significantly more expenses and more than a year of recovery.

I am not sharing this for sympathy, but rather because I learned

something important. Now that I am getting older, as I decide which

projects I should do myself and which to pay professionals to do, it is

important to factor in the potential impact on my body, my mind and

those around me, even if all goes well.

Just because you can do a thing does not necessarily mean you should

do a thing.

Unless that "Thing" is recording a podcast for HPR. THAT is something

you can and should do.

I have a discussion about my Android "WIPING" and how it affected my

2 factor authorization with Google. Further I "beein" some more about

Android not being able to authenticate against a known chromebook using

GOOGLE SECURITY, what a "beeing" , "beeing"!!!!

And I also cover Google's lousy support for chromebooks through

Android, not sharing bandwidth via the cell communication channels. I

cover easytether and ask why Google hasn't given chromebooks the same

bandwidth access any Android phone would have??? WHY???

Google is so piggish and stupid that Android and chromebooks are

almost as if they were separate companies who are in competition with

each other instead of two products from the same company.

I also cover the overbearing Android growth via QR codes and programs

like healio.

Bhyve - The BSD Hypervisor

https://bhyve.org/

vm-bhyve - Management system for FreeBSD bhyve virtual

machines

https://github.com/churchers/vm-bhyve

Haiku - Open-source OS inspired by BeOS

https://www.haiku-os.org/

UEFI Booting Haiku

https://www.haiku-os.org/guides/uefi_booting/