We started producing shows as Today with a Techie on 2005-09-19, 14 years, 9 months, 24 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 9 days.
Please help out tagging older shows !
Hosted by HPR Volunteers on 2020-07-06 is flagged as Explicit and released under a CC-BY-SA license.
Tags: Community News.
Listen in ogg, spx, or mp3 format.
Series: HPR Community News | Comments (0)
There were no new hosts this month.
These are comments which have been made during the past month, either to shows released during the month or to past shows. There are 23 comments in total.
There are 6 comments on 5 previous shows:
There are 17 comments on 11 of this month's shows:
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:
http://hackerpublicradio.org/pipermail/hpr_hackerpublicradio.org/2020-June/thread.htmlWith the kind permission of LWN.net we are linking to The LWN.net Community Calendar.
Quoting the site:
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.
Most of the shows we process require us to make some level of modifications to get them posted. This ranges from fixing tags to a complete rewrite of the shownotes, or verifying whether intros were actually added or not.
Each modification that we make means that it requires more human intervention and prevents us from being able to completely automate the upload process. In addition there is a non trivial amount of time needed to "fix" these issues. This can range from a few minutes to an hour or more per show, and with 260 shows a year this mounts up.
We normally don't contact hosts about these issues as it is usually quicker to fix the issues than composing emails, and waiting for the reply that may never come. For the most part our experience has been that hosts are more than willing to fix these issues if they are aware of them.
As part of the ongoing steps toward automation, would hosts be open to the idea of getting a processing report once we have posted the show? This would list all the issues the test tools found and the steps that we needed to take to rectify them.
Sometimes an error or omission in notes for an HPR episode isn't noticed until the show is posted to the site. In recent times a few hosts have sent in their changes by way of comments. This not ideal:
archive.org, so such corrections will not be seen by people reading the notes thereThe HPR admins would prefer changes to be sent in the form of emails to admin at hackerpublicradio.org. They will then be applied to the show notes and the archive.org version updated in step.
Thanks to the following contributor for sending in updates in the past month:
Windigo
Over the period tags and/or summaries have been added to 10 shows which were without them.
If you would like to contribute to the tag/summary project visit the summary page at https://hackerpublicradio.org/report_missing_tags.php and follow the instructions there.
Hosted by Ken Fallon on 2020-07-03 is flagged as Explicit and released under a CC-BY-SA license.
Tags: TWRP,Tweakers,LineageOS,scrcpy,tektab.com,bootloader,fastboot,Sony Xperia XA2,pinephone.
Listen in ogg, spx, or mp3 format.
Comments (0)
Affordable phone that support school apps, and allow firewall.
Don't, unless you are willing to loose the money you are paying.
Getting a brand new phone means that Developers have not had time to release code.
Older phones are no longer available for purchase, and actually become more expensive.
Too old a version and apps are no longer supported.
I use a site called Tweakers.net which allows you to do parameter search.
Set the maximum price you are willing to pay.
The current version of Android is 10 so select only those. You want your phone to be supported for as long as possible.
Make any other selections that you think are critical, like memory, processor etc but be prepared to adjust this later.
In my case I selected a minimum of 4G Ram and 64G Storage the first time.
Sort by price low to high, and loop through, finding what support there is for TWRP. That will tell you how open the phone is. If the Manufacturer support (the spirit of) unlocking, then remove them from the list.
After finding a phone that can be unlocked and rooted, then check to see if there is an official version for LineageOS
If no phone meets all the requirements then try the next one.
It's very likely you will not find a phone. You are then faced with the choice of adjusting your parameters, for example picking a more expensive model, but at the end of the day be prepared that you may not find a phone.
If you do find a phone, it's very likely that it may be a different version than the one supported. I have had to return several phones that I had unlocked and just hoped that the supplier would take them back and refund me.
Even on supported phones, especially newer ones, it's quite often that a major piece of functionality will not work. I have had issues with no GPS on one phone, and bluetooth/wifi not working on another until files were manually edited on each reboot.
Do not do this if you want a stress free life, and also if you are not willing to accept the waste of all the money, and time involved.
Good day to all in HPR land, this is Tony Hughes coming to you again from Blackpool in the UK. To recap this is the 4th in a series of shows about my hobby of restoring Matchbox and other Die cast models. In the last show I went through the process of stripping the models down to their component parts. In this episode I will discuss the process I use to remove the paint and prepare the casting for repainting and reassembly.
So first off, and I should have said this last episode, a health and safety warning. If there are young people listening to this some of the things talked about on today's show require parental supervision, and are not recommended for young people unless properly supervised. So with that public service announcement out of the way let's get on with the show.
So before the base can be put in the paint stripper the wheels and axles need to be removed. As you can see from the picture there are flanges holding on the wheels to the metal axle and one side is only a small flange.
Picture 000
This can be removed with a small needle file or a small rotary file attachment for my rotary tool. Once removed the bases can be put in with the rest of the casting for paint removal.
Picture 001
So let's talk about paint removal, obviously the first one you will think of is some kind of chemical paint stripper and I use 2 different methods of this. The first and probably the safest in the first instance is a commercial paint stripper from one of the chain DIY stores here in the UK, B&Q. There is a local store about 10 minutes drive from me so it is convenient during normal shopping times just to pop in and grab a 2.5Ltr container of their own brand DIAL paint stripper that is fantastic for this job and quite economic.
The second is a little more aggressive if you need fast results but requires a little more in the way of care when using it as it is very corrosive and can be harmful if the fumes are breathed in, or the product gets onto your skin or in your eyes. This is caustic soda and I buy this through eBay and have it delivered in 1Kg pouches. It needs to be stored in an air tight container in a dry environment to keep it from getting damp as this is a potential fire hazard as if it gets contaminated buy moisture a chemical reaction starts which generates heat. So if you go with the caustic soda method you need to take adequate safety precautions. With the Jaguar I mainly used the caustic soda method to remove the paint but one casting I put in the paint stripper to show that method.
With the caustic soda place the castings in a jar with enough room to cover with just boiled water so that it does not overflow when the caustic soda crystals are added slowly, I use a long handle tea spoon and add 2-3 tea spoons of the soda until it has a good fizz. Then leave for about 15 minutes but the longer the better, I sometimes do this and leave over night and this gives a great result. Remember to wear gloves when doing this to prevent getting the caustic on your hands.
Picture 002
Picture 003
Picture 004
Picture 005
With the paint stripper I have a plastic click lock box with this in that I immerse the casting into and leave for several hours for best results. This can be reused many times as you can see in this picture keeping it an economic method as most of the stripper is left in the box when you remove the casting. The results for both methods are similar, but I find the caustic although you need to be careful, is the less messy of the two options, and the casting is easier to clean after paint removal.
Picture 006
So after removal of the paint the castings are polished up with either a hand wire brush or a wire brush attachment for the rotary tool. You can see the base before and after and a picture of the polished main casting in the notes.
Picture 007
Picture 008
So we now have a casting ready for repainting, which I will cover in the next episode. So until next time this is Tony Hughes saying goodbye to all those in HPR land. Keep safe until the next instalment.
Hosted by Zen_Floater2 on 2020-07-01 is flagged as Clean and released under a CC-BY-SA license.
Tags: OpenBSD,Fuguita,Desktop,Portability,Sanity.
Listen in ogg, spx, or mp3 format.
Comments (1)
I cover many issues about using OpenBSD based Fuguita as your Desktop. I wouldn't have it any other way, I use Fuguita for my main Desktop these days.
First implementation: 14 character long with 6 letters and 8 digits
#!/usr/bin/env python3
# file: passgen-v1.py
import random
LETTERS = "abcdefghijklmnopqrstuvwxyz"
if __name__ == "__main__":
passwd = []
for i in range(6):
passwd.append(random.choice(LETTERS))
for i in range(8):
passwd.append(random.choice("1234567890"))
print("".join(passwd))
The passwords that come out of this are a bit difficult to type so I forced it to alternate between the left and right hands
#!/usr/bin/env python3
# file: passgen-v2.py
import random
LEFTS = "',.pyaoeui;qjkx"
RIGHTS = "fgcrldhdhtns-bmwvz"
if __name__ == "__main__":
passwd = []
for i in range(6):
if i % 2 == 0:
passwd.append(random.choice(LEFTS))
else:
passwd.append(random.choice(RIGHTS))
for i in range(8):
if i % 2 == 0:
passwd.append(random.choice("123456"))
else:
passwd.append(random.choice("7890"))
print("".join(passwd))
The regularity of switching between left and right hands (intuitively, and almost surely) decreases the entropy of the password, so use markov models to make that happen for the most part but critically NOT enforce it.
#!/usr/bin/env python3
# file: passgen-v3.py
import random
Ls = [
"aoeui", # L1
"',.py", # L2
";qjkx", # L3
"123456", # L4
"-snthd", # R1
"lrcgf", # R2
"zvwmb", # R3
"7890" # R4
]
A = [[ .03, .03, .03, .01, .27, .27, .27, .09],
[ .03, .03, .03, .01, .27, .27, .27, .09],
[ .03, .03, .03, .01, .27, .27, .27, .09],
[.004, .003, .003, .09, .03, .03, .03, .81],
[ .27, .27, .27, .09, .03, .03, .03, .01],
[ .27, .27, .27, .09, .03, .03, .03, .01],
[ .27, .27, .27, .09, .03, .03, .03, .01],
[ .03, .03, .03, .81, .004, .003, .003, .09]]
pi = [ .41, .03, .03, .03, .41, .03, .03, .03]
def sample( l ):
l_partial = [ sum(l[:i+1],0) for i in range(len(l))]
u = random.uniform(0,1)
for j,v in enumerate(l_partial):
if v > u:
return j
if __name__ == "__main__":
passwd = []
s = sample(pi)
for i in range(20):
s = sample(A[s])
passwd.append(random.choice(Ls[s]))
print("".join(passwd))
For increased entropy should also consider peppering in a few upper case characters.
#!/usr/bin/env python3
# file: passgen-v3.py
import random
Ls = [
"aoeui", # L1
"',.py", # L2
";qjkx", # L3
"123456", # L4
"-snthd", # R1
"lrcgf", # R2
"zvwmb", # R3
"7890" # R4
]
A = [[ .03, .03, .03, .01, .27, .27, .27, .09],
[ .03, .03, .03, .01, .27, .27, .27, .09],
[ .03, .03, .03, .01, .27, .27, .27, .09],
[.004, .003, .003, .09, .03, .03, .03, .81],
[ .27, .27, .27, .09, .03, .03, .03, .01],
[ .27, .27, .27, .09, .03, .03, .03, .01],
[ .27, .27, .27, .09, .03, .03, .03, .01],
[ .03, .03, .03, .81, .004, .003, .003, .09]]
pi = [ .41, .03, .03, .03, .41, .03, .03, .03]
UPPER=.1
def sample( l ):
l_partial = [ sum(l[:i+1],0) for i in range(len(l))]
u = random.uniform(0,1)
for j,v in enumerate(l_partial):
if v > u:
return j
if __name__ == "__main__":
passwd = []
s = sample(pi)
for i in range(20):
s = sample(A[s])
c = random.choice(Ls[s])
u = random.uniform(0,1)
if u < UPPER:
c = c.upper()
passwd.append(c)
print("".join(passwd))
Finally, generating the matrix by hand was a bit of a pain, so I made it a bit easier by making a small procedure with few control knobs (the variables SWITCH_HAND and SWITCH_CHAR which control how likely it is that a character pair will result in a hand switch, or a switch between general characters and digits).
#!/usr/bin/env python3
import random
import numpy
# this version uses a markov chain to make it more likely to alternate hands
# (in dvorak) so that the password is easy to type (in dvorak)
Ls = [
"aoeui", # L1
"',.py", # L2
";qjkx", # L3
"123456", # L4
"-snthd", # R1
"lrcgf", # R2
"zvwmb", # R3
"7890" # R4
]
SWITCH_HAND = .8
SWITCH_CHAR = .3
UPPER=.1
def prob( i , j ):
switch_hand = int(i / 4) != int(j / 4)
to_num = (j % 4) == 3
from_num = (i % 4) == 3
prob = 1
if to_num and from_num:
prob *= (1 - SWITCH_CHAR)
elif to_num:
prob *= (SWITCH_CHAR)
elif from_num:
prob *= (SWITCH_CHAR / 3)
else:
prob *= ((1 - SWITCH_CHAR) / 3)
if switch_hand:
prob *= SWITCH_HAND
else:
prob *= (1 - SWITCH_HAND)
return prob
A = numpy.array([ [ prob(i,j) for j in range(8) ] for i in range(8) ])
pi = [ 1.0 / 8 for i in range(8) ]
def sample( l ):
l_partial = [ sum(l[:i+1],0) for i in range(len(l))]
u = random.uniform(0,1)
for j,v in enumerate(l_partial):
if v > u:
return j
if __name__ == "__main__":
passwd = []
s = sample(pi)
for i in range(20):
s = sample(A[s])
c = random.choice(Ls[s])
u = random.uniform(0,1)
if u < UPPER:
c = c.upper()
passwd.append(c)
print("".join(passwd))
Postgres
Listen to our two OAP interviewing Bruce
Momjian, Postgres evangelist and long-time supporter of this popular SQL
database. Expect lots of strong language around SQL and NoSQL topics and
some ranting about MINT's attitude towards snaps, a fun breach of a health
service provider in the UK and why broadcasters should stick to
monopolies.
Hosted by Ahuka on 2020-06-26 is flagged as Clean and released under a CC-BY-SA license.
Tags: Camera, Waterproof Camera, Action camera.
Listen in ogg, spx, or mp3 format.
Comments (0)
Action cameras are becoming very popular, and many incorporate a waterproof feature. If you want to try this with something less expensive than a GoPro, take a look at this review.
As usual, the HPR AudioBook Club took some time to review the beverages that each of us were drinking during the episode
Quarter Share by Nathan Lowell
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.
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.
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:
Threshold: -30db
Noise Floor: -50db
Ratio: 3:1
Attack Time: 0.2sec
Decay Time: 1.0 sec
"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.
Hosted by Ken Fallon on 2020-06-24 is flagged as Clean and released under a CC-BY-SA license.
Tags: extensions,add-ons,firefox,chromium,chrome,thunderbird.
Listen in ogg, spx, or mp3 format.
Comments (0)
I started getting popups while going to safe websites in chromium-browser. I disabled all browser extensions and then turned them back on individually. I found one that which was causing the problem and it is no longer on the app store. It was however still working and had not been revoked on my browser.
Please check your extensions and add-ons to make sure they are regularly updated.
Hosted by clacke on 2020-06-23 is flagged as Clean and released under a CC-BY-SA license.
Tags: webcomics, rfc5005, atom, rss, feeds.
Listen in ogg, spx, or mp3 format.
Comments (0)
An interview with two passionate RFC 5005 fans on how to handle big Atom feeds
This conversation took almost an hour, so I split it into two shows:
This is part 2.
In this show I’m talking to:
Get a full list of all our shows.