I enjoy listening to audiobooks. It allows me to engage with a book while I do something else. Specifically, I enjoy listening while cleaning, running, or on long car rides. I do not like having all of the books I have purchased locked behind licenses. Here is my current set up for self-hosting audiobooks.
I found Libation a while back. It is, “a free, open-source application for downloading and managing your Audible audiobooks. It decrypts your library, removes DRM, and lets you own your audiobooks forever.”
It was shockingly easy to set up. I initially installed it on my Ubuntu laptop and when I add a title, I run the importer. It then delivers a DRM free version of my title
Audiobookshelf is pretty much Plex or Jellyfin but for audiobooks and podcasts.
They have a docker container, which I am running on my Raspberry Pi 4 for the server.
It was very straightforward to set up.
They also have an incredibly performant Android App (especially compared to Audible’s).
I was able to point to my Tailscale address for the audiobookshelf docker container from the app’s interface. Now I have all my audiobooks on the go without any pain. It saves my spot, has great metadata, and has features I have not even played around with.
Additionally, I set it up to capture podcasts which I want to have a personal archive of from the podcatcher interface.
Usually I do not re-listen or re-read books. There is just too much out there to experience. That is why I love the library. I use Libby which allows you to check out audiobooks using your local library. Unless a book is an exclusive on Audible or another service, or the library in question does not have the title, Libby is my first stop. It is a phenomenal service. Libraries are amazing. And you do not need to own everything.
]]>Over the next 10 weeks I am on parental leave with the latest addition to our family. I am very grateful that my employer and the state where I reside supports this bonding. Everyone has been relatively healthy and happy.
]]>I live in Minneapolis.
Renee Good was shot and killed by an ICE officer in our city.
My community, my neighbors, and my family will not be intimidated.
We are stronger because of the presence of an overpowered and cruel federally funded force.
We are communicating securely to track ICE activity near our schools, daycares, and homes.
We are decentralized and hyper local.
This is a war of attrition and we live here. This is a marathon, not a sprint.
We are domestic terrorists because we refuse to stand idly by while our neighbors and friends are abducted and beaten by undertrained bullies hiding behind masks.
We will continue to protest, we will continue to support one another, and we will not forget. We will be peaceful in the face of their violence.
We have whistles, we have each other, and we know we aren’t the baddies.
Update:
I wrote this early in the morning on January 24, 2026.
Since then, ICE has shot and killed another of citizen of Minneapolis.
This is our home. These are our friends. ICE needs to get out.
]]>I had two very different experiences using two different controllers.
SteamOS and all the hardware that Valve has created makes a great ecosystem for gaming. You can bring what you want and it either works right away or is easy enough to get up and running.
Windows is becoming more of a walled garden that is unpleasant and exclusive.
Let’s talk about the Steam Controller.
No, not that Steam Controller.
This Steam Controller (2015).
I am a sucker bespoke hardware.
I was excited when Valve was making moves into the hardware space in the mid 2010s. The OG Steam Machines, Steam Link, and Steam Controller.
But I was not excited enough to actually buy of those things when they came out. The latter two pieces of hardware were eventually discounted heavily and I snagged them (and they became mothballed by Valve).
I purchased the Steam Link in 2017 for $15.00.
I used intermittently when I built my gaming pc back in 2015/2016 to stream down to the TV. It worked great and actually installed the Steam Link app on a Raspberry Pi too. Valve released the software and now you can just use it for streaming.
Then I purchased the Steam Controller in 2019 for $5 (plus around $10 for shipping).
Honestly, the Steam Controller (2015) is not great. It is not very comfortable and it feels weird overall. The track pad is not the refined track pad of the Steam Deck.
Honestly, after my first couple of times using it, I tossed it into the big bin of random hardware.
I later became a huge fan of the Steam Deck, picking one up in April of 2022.
My partner and I have been playing some mystery games, specifically Return of the Obra Dinn and Case of the Golden Idol. These games are amazing couch coop games. One person needs to “drive” the game while also both of you discuss theories of the different mysteries on screen.
The set up is to plug my Steam Deck into the TV and play sitting next to each other on the couch.
I have a JSAUX Steam Deck Dock plugged into our TV. This dock works pretty well! It is nice to be able to set my Steam Deck down in a specific place while it charges and the dock does a fine job with the TV display.
Despite having a bunch of Xbox controllers laying around, they have not been helpful with couch mystery coop.
We have exclusively been using the 2015 Steam Deck Controller (and even using some of its gyro controls).
It just worked right away when I plugged in the USB dongle into the dock.
The Xbox One controller has been a nightmare.
I tried to get my Xbox One controller working on my Steam Deck via bluetooth.
It connected but then disconnected immediately, ping-ponging back and forth. This is a known issue with a resolution. I needed to update the firmware on the controller.
Apparently to update this controller, I need to use the Xbox Accessories App on Windows.
I built a gaming PC years ago and it is the only Windows device I own still. It is in storage. I went ahead and dusted it off and booted it up.
I installed the Xbox Accessories App.
However, I am still running Windows 10 (shame on me, but I never boot the thing up).
The Xbox Accessories App does not work on Windows 10 any longer, it only works on Windows 11.
I tried to find the firmware package to do the install somehow myself, but I could not figure out a work around.
So to update the firmware on my Xbox One controller, I need to update to Windows 11 in order to run the firmware update.
But I don’t want to update my Windows gaming PC (even if the upgrade from Windows 10 to 11 seems to be free). Time is too precious to babysit a Windows update just to use a controller.
Compare this to the plug and play experience I had with the Steam Deck Controller from 2015. And Valve’s continued open source software support.
I am less and less inclined to invest in these walled gardens, like Microsoft and Apple. If I own the hardware, I should be able to use it and maintain myself with the software I want on it (or firmware). I am wary of what Valve could become, but they keep releasing things the right way.
I’m not sure how cogent of a thought that is, but I know I am frustrated and just want to play my mysteries.
]]>During the pandemic I took a Coursera course The Science of Well-Being. As part of the course, I learned about the importance of gratitude.
I created a tiny script to help me write a gratitude journal each day. With the New Year, I thought it would be good to get out there and show off this script that, honestly, has helped me be more grateful.
It uses Google App Script, which is basically Javascript that has Google Office Suite API endpoints baked in.
This should be something you can copy and paste, make a tiny edit to the code, and get deployed in around 5-10 minutes without any prior knowledge regarding how to code.
Feel free to use this script in your life to help capture your moments of gratitude and create a sustainable and positive habit.
I have been using this daily since March 11th, 2021. It has captured everything from the feeling of having fresh sheets on my bed to additions to our family.
Each day at around 6:00 PM, a document is created in my Gratitude Journal Google Drive folder. I get sent an email with a link to the document.
I then fill out the journal, usually as I am going to bed, to capture what I was grateful for on the day.
Create a new Google Doc with the name, “Gratitude Template”.
Here is the text I use in the template for a prompt (I found it online years ago):
Instructions
Take 5-10 minutes to write down five things for which you are grateful.
Take a moment to be mindful of the things you are writing down (e.g., imagine the person or thing you’re writing about).
Some samples:
What’s something that you are grateful to have today that you didn’t have a year ago?
What’s something or someone that makes you feel safe?
What did you accomplish today?
How are you able to help others?
What’s something or someone that makes you feel safe?
Response
Create a new Google Drive folder called, “Gratitude Journal”.
The above names are essential for the script to work. Feel free to update them as you see fit, but you will also need to update the references in the script.
Navigate to script.google.com
Create a new project.
Feel free to copy and past the below code.
function triggerSetUp() {
ScriptApp.triggerSetup('createNewJournal')
.timeBased()
.atHour(18)
.everyDays(1)
.nearMinute()
.create()
}
function createNewJournal(){
var gratitudeFolder = DriveApp.getFoldersByName("Gratitude Journal").next()
var template = gratitudeFolder.getFilesByName('Gratitude Template').next()
var formattedDate = Utilities.formatDate(new Date(), "GMT", "yyyy-MM-dd")
var name = 'Gratitude ' + formattedDate
var newTrackingDoc = template.makeCopy(name, gratitudeFolder)
emailTrackingLink(newTrackingDoc, formattedDate)
}
function emailTrackingLink(newLink, formattedDate) {
// email link to newly created document to myself
var htmlText = "<p>Remember to do your gratitude journal for " + formattedDate + ". <a href='" + newLink.getUrl() + "'>Here is the direct link</a>. "
MailApp.sendEmail({
to: 'YOUREMAIL@EMAILCOM',
subject: "Gratitude Journal " + f.ormattedDate,
htmlBody: htmlText
})
};
Make sure you update your email in the to: 'YOUREMAIL@EMAILCOM' line.
I believe the UI on the Google App Script will give you an option on the interface for a “function to run”. It may default to triggerSetUp.
Either way, select the triggerSetUp from the UI toolbar and that will create the scheduled job (effectively a cron job).
Then, around 1800 AKA 6:00 PM (give or take 10 minutes) you should receive an email to your account from your Google account with the link to your new Gratitude Journal for the day.
]]>Similar to my Goals Achieved post, I want to try to capture media I enjoyed each year. I do not want to use Letterbox (in some small part because I don’t really watch movies anymore) or Backloggd. I want to own these lists.
I realize I did not watch many movies besides what the kids wanted to watch, so I am skipping that category.
A majority of this media will not be from 2025, but is media I consumed in this year.
I am writing this New Year’s Eve and currently have COVID-19, so the goal is to get this out the door this year.
I will limit each category to five pieces of media in no particular order.
I did have a draft which I went into details about why I enjoyed each piece of media. I want to do that in the future.
Enshittification by Cory Doctorow
Rose/House by Arkady Martine
Piranesi by Susanna Clarke
Dungeon Crawler Carl by Matt Dinniman
Project Hail Mary by Andy Weir
Celeste OST by Lena Raine
Fragments by Bonobo
Good For You - Aminé
I rewarded myself by purchasing some expensive running headphones. And I have yet to use them on a run.
I did not do as good of a job of rewarding myself materially, but the family and I took multiple trips that were really restorative and made some great memories.
Next year, here are the goals I have. Notably, we are expecting our third child early in the year. Last time we had a new addition to the family, I stopped running. So, my running goals have shifted to be more of “maintenance”.
I am currently on the fence about these, but I want to document them for next year.
When trying out a new Docker container, exclude the restart: unless stopped flag. Or any restart flag really.
You will thank me! This is a post for me to reference in the future but maybe you will learn something too.
This is especially important if you are running things on a lower powered device, such as a Raspberry Pi.
I tried out Stirling PDF, a service I hope to use in my homelab.
PDFs are terrible in general and the software built up around them is aggressively commercialized (ahem Adobe).
I am more comfortable using docker-compose files over just using a docker command.
In my experience, it is easier to replicate things by capturing the configs in the yml file instead of them being lost in the terminal history.
I converted the docker command into a docker-compose file and ran it.
The Pi I was using (along with the other containers) couldn’t run it due to the required overhead. I think the CPU was the chokepoint as Stirling PDF uses Java, but I am not positive.
I restarted the pi (forcibly removed the power cord, I know, bad practice).
And then, upon restart…it became unreachable again because the CPU hungry service kicked off again.
I finally had to forcibly reboot (sorry again), then ssh to the device as soon as possible, then I did docker compose stop from within the Stirling PDF directory to free myself from the disastrous loop.
This has happened to me twice, and I’m writing it down here as a reminder.
If you are testing out a service with docker, never add the restart: unless stopped.
This is not an original idea, it is something that came across some podcasts I listen to and my RSS Feeds.
The Wavelengths podcast discussed it in the episode with Stephen Hilger.
Additionally, The Verge’s Installer newsletter issue 105 interviewed Ryder Carrol, who created the Bullet Journal Method.
In that newsletter Carrol gives the following advice:
“Delete all algorithmic apps: I could quibble forever with the precise definition here, but I support the theory of getting rid of anything designed to keep your attention as long as possible”
It is a nice heuristic and a way to simplify my digital life.
Clearly my attention and focus is worth something! Companies have devoted resources in order to grab it and never let go.
Recently I was really into Youtube Shorts because it kept drip feeding me skateboarding and Hollow Knight Silksong content.
Looking at my history and the time that I wasted, I disabled that feature (as much as I could, Youtube makes it very difficult to get rid of this completely).
I deleted my Facebook, Twitter, Instagram, and Reddit years ago. I have curated my own feeds and I have discussed it before.
I am Discord and Linkedin, the former of which is a real problem some days. On the rare occasion I open Linkedin, the endless scrolling tends to get its hooks into me more than I would like to admit.
I limit my time on Discord by not having the app installed and using LeechBlock to limit my time each day.
That friction is important.
My attention and focus are finite resources which are valuable.
Algorithmic feeds are created to dominate those resources for the benefit of the companies which created them.
I have to imagine at some point, that attention translates into some type of cash flow for the company.
I want to profit off of my attention, not some giant tech company.
]]>To quote my last post, “I got very lucky, nothing on the card was important data.”
Yeah, about that.
I was running a service that I have fallen in love with, LubeLogger, and it is NOT what you think.
I always found car maintenance daunting. My dad is very mechanically inclined. I am not.
LubeLogger created a structure around basic car care and allowed me to feel like I could track things and, more importantly, know I had a single source of truth.
Anecdotally, it has saved me money. We have jumped between different mechanics and so, they do not have a whole history of our car. Being able to say that the differential fluid was actually flushed at a different shop, even though the manufacturer does recommend it is serviced at the current mileage reading, felt really validating.
It even got me to replace the battery in the car myself on New Year’s Day this last year. I felt like I could actually track this stuff and, because I could track it, I could potentially do some of it.
Too bad I didn’t back it up.
The micro SD card that powered the Raspberry Pi that I ran LubeLogger on died. I did try to restore it and I learned about some useful tools. My approach lasted a weekend and was very scattershot.
I could not restore it.
I did learn about fsck, dd, and ddrescue
I removed the card and tried to mount it on my laptop, which is running Ubuntu.
Here is the error message that popped up.
error mounting /dev/mmcblk0p2 at /media/MYUSERNAME/rootfs: wrong fs type, bad option, bad superblock on /dev/mmcblk0p2, missing codepage or helper program, or other error
I did some research and found the following potential leads:
https://unix.stackexchange.com/questions/315063/mount-wrong-fs-type-bad-option-bad-superblock
https://unix.stackexchange.com/questions/494491/sd-card-recovery-without-data-loss-or-corruption
https://www.cgsecurity.org/wiki/TestDisk_Step_By_Step
I tried to get more info on my situation by running lsblk -f
sdb
├─sdb1
│ vfat FAT32 boot 29F5-65C4 224.3M 12% /media/jft/boot
└─sdb2
ext4 1.0 rootfs
cbe4d267-24de-4402-9a4b-1413a1da5eb8
I started with DDrescue.
DDRescue can copy data and create an image from that data. Pretty cool! It also have utilities built in to try to fix corrupted data.
I installed DDRescue sudo apt install gddrescue
The goal at this phase was to dump the contents of the microSD card into an image that I could interact with rather than having to try to get the data off of a dying/dead microSD card every time I tried to restore the data.
After reading the above, I tried sudo ddrescue -d /dev/sdb backup.img backup.logfile
This was successful! I got an image of the corrupted card.
I also tried to repair the image off the micro SD card (I should have, and probably could have done this with the image I just created).
ddrescue -f -n /dev/sda /dev/sdb sda.img
The -f flag is for “force” which “Force overwrite of mapfile.”
The -n flag is for “Skip the scraping phase. Avoids spending a lot of time trying to rescue the most difficult parts of the file. “
I’m not sure if those are the best flags to use, but the guides I read recommended them.
This ran a long time. At one point, it said it was going to take at least 24 hours, but ultimately it finished in around hours.
GNU ddrescue 1.23
Press Ctrl-C to interrupt
ipos: 32026 MB, non-trimmed: 0 B, current rate: 29687 kB/s
opos: 32026 MB, non-scraped: 0 B, average rate: 1514 kB/s
non-tried: 0 B, bad-sector: 0 B, error rate: 0 B/s
rescued: 32026 MB, bad areas: 0, run time: 5h 52m 23s
pct rescued: 100.00%, read errors: 0, remaining time: n/a
time since last successful read: n/a
Finished
This looked promising! It said everything was rescued!
I wiped the old micro SD card.
I tried to use the very powerful dd to reflash the image on the recently wiped card.
So I tried writing sudo dd if=mmcblk0.img of=/dev/mmcblk0
This ran the on the old card, but resulted in the same issue. It could not mount the root file structure and the boot partition was in read only.
I then bought a new microSD card and tried the same sudo dd if=mmcblk0.img of=/dev/mmcblk0, with the destination being the new card.
The image was succesfully written, then I tried fsck the card to repair the corrupted partitioned.
fsck is a file system check. It can also be used to repair file systems.
fsck from util-linux 2.37.2
e2fsck 1.46.5 (30-Dec-2021)
ext2fs_open2: Bad magic number in super-block
fsck.ext2: Superblock invalid, trying backup blocks...
fsck.ext2: Bad magic number in super-block while trying to open /dev/mmcblk0
The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem. If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
or
e2fsck -b 32768 <device>
Found a dos partition table in /dev/mmcblk0
So, after trying some command line incantations, buying new hardware, and lot of patience I am unable to recover any data from the card. I suspect I could pay some money to get the data back. If you have any suggestions, please reach out.
Most of the important data from LubeLogger was transcribed from invoices I saved elsewhere. Other than that, it was a lot of data related to gas mileage. I will lose that, but I am OK with that.
I need to re-enter the data I have, but that is fine.
Now, that I actually lost data due to carelessness, I will set up a backup plan. I think I will start with some very basic rsync commands. But I learned some cool and potentially useful commandline tools along the way.
]]>