The previous owner of our property believed in letting nature run its course entirely without human intervention. As a result our front yard had been a long outstanding project that we’d been afraid to tackle. In addition, we had some serious drainage problems that led to standing water in the driveway, and sump pumps that just dumped out into the front yard surface.
This year we decided to change all that and had For Garden’s Sake do some landscaping for us. In addition to dealing with the drainage, and overgrowth, we wanted them to fix the front yard that AT&T had dug up numerous times, as well as connect our awesome new front porch to the driveway in a nice looking way. I would say mission accomplished – but you can judge for yourself looking at the following before and after shots:
It’s a huge improvement, and the galleries above should give you an idea of the overall project and progress for the entire front yard. We’re happy with the work and looking forward to watching all of these new native plants grow.
Best of all, there is no more standing water to worry about!
Search all titles and lead paragraphs for the word ‘actually’ or [\d+] [things|ways] and give me a way to hide them, block the article or entire site, or compose a letter to their editor with a list of their offenses.
It seems like everyone is doing it these days with actually and listicles in my feed, but maybe there are just one or two offenders I could block to scrub for content quality.
However, maybe they’re doing me a favor by providing a ‘click bait’ metadata tag so I know to stay far away. Maybe they should keep doing it. What do you think?
This blog has been alive in some form since 2002. As you can imagine a lot has changed in 18 years. The blog has moved physically from servers under desks, servers in closets, to finally virtual machines in the cloud. Even those VMs have changed AWS instance sizes and Ubuntu LTS versions over time. The blogging platform has also changed. I started this thing with a custom set of PHP pages that I wrote myself to pull entries from a MySQL database. I migrated to something called Serendipity for a while to get more features and then finally to WordPress. All the while the MySQL backend has been pretty much the same.
My photo sharing strategy has also changed. I moved from a directory of images, to Menalto Gallery, to Gallery3, and recently to Piwigo. Gallery3 has been unsupported for a VERY long time, but the nail in the coffin was that it required me to keep an older PHP version on the server. The switch to Piwigo allows me to ditch my Ubuntu PPAs for old PHP versions, and lets me use a photo sharing platform that receives updates, has themes, and works well on mobile.
The problem I face now is that in 18 years I’ve linked to a LOT of photos directly from the blog posts. In some places I wrote the HTML directly, in other places I inserted a link to an image using a WordPress block. In almost all of those cases I’m linking to Gallery3 album pages that no longer function. ALL of the older JPG images are still in the Gallery3 folders, taking up lots of space since they also exist in Piwigo.
I’m left with a few options:
Go back and edit every single blog post that linked to images with the new Piwigo links.
This may be easier if I create a LOT of permalinks inside Piwigo’s “category” structure for albums.
Create some complicated mod_rewrite rule that intercepts the old links and sends to the new link.
This will REQUIRE that I create a lot of permalinks in Piwigo.
Put some boilerplate text at the top of every old post that points to the new high level photo gallery.
Not great, because if I’ve learned anything – this won’t be the last platform migration I ever do.
Do nothing. Leave the old links and images broken. Think only of now.
This is tempting, but there is a lot of nostalgia in those old posts.
Wish me luck on this project. I still have some work to do, and next week I should have some time to focus on it.
Crazy twist. I reinstalled a BUNCH of PHP packages from a custom PPA and replaced them with the default Ubuntu repo packages and now my old Gallery3 is working again. I suppose this gives me an option to keep old images on Gallery3, and new images in Piwigo. Still more thought needed here.
Our amazing friends Brendan and Anneka (henceforth known as Brenneka) got married in Colorado on New Years Eve 2019/2020. It was an awesome time and we used the trip to see old friends, get outdoors, and just have a great time.
Side note: This trip in December was also what partially inspired my “Dry January”.
We spent the first few days of the trip with Mark and Jennifer, Kat’s flight attendant friends who live in Denver. We had a good time exploring local breweries and hanging out while we were snowed in. They may THE BEST breakfast – definitely a great visit! We were a little jealous of how much they get to travel. So many great photos on the wall from so many places.
After two days in Denver we got picked up by Rama and Graciela and took a trip to Rocky Mountain National Park. It was freezing cold up there so we decided to go on a hike around the like, and even hike out onto a frozen lake.
At the end of the park day we headed back south to Como, Colorado to stay in a tiny AirBnB cabin. It was a neat little place up on a very cold very windswept plain right next to the town of Fairplay, which is apparently the hometown that South Park is based on.
Waking up in the frigid -15 F temps we decided to take it a little easy and roll on up to Breckenridge around 9ish for cross country skiing. We bundled up like crazy and even though it was below zero we were still sweating and had to drop layers.
After getting our skis under us we headed straight back to Denver for night 1 of friend hangout and partying. Day 2 we met friends for brunch in a giant group, took a quick nap, then had an amazing New Years Eve wedding and reception downtown.
This was a fantastic trip. It had been such a long time since the gang was all together. It was nice to mix up some exercising, exploring, and partying all in one trip.
Kat bought our house around the same time that I bought my condo in 2014, before we even met! It’s an amazing property on a large wooded lot with nice privacy and set back a bit from the street in a quiet neighborhood.
The house had a great back deck with room for an outdoor dining table. Being in the woods and in NC means we had quite a few usable months for the porch – but our nemesis, the Aedes aegypti mosquito, made the outdoors pretty much a no-go-zone whenever it was above freezing for a few weeks.
For years we were spraying for mosquitoes trying to keep the situation under control. We weren’t happy about having a service spray chemicals, but the mosquitoes were so thick in the air as to create a visible blood-sucking cloud.
We stopped the spray service when our next-door neighbor started raising bees and at that point we ceded control back to the mosquitoes. We needed to take more drastic (and expensive) measures to maintain an outdoor dining experience.
Last year, we decided we were going to replace the rotting front and rear decks with new long-lasting Trex Deck material and build a covered screened in section in the back. Along the way we cut down a number of trees, replaced the roof, and are nearing the final point where the back porch gets a screen added. Check out the album below to see the house as it changed over time.
We’re excited to use the new covered section as the temperatures warm up. We even plan on spending a few of our work from home days out there. We made sure there was PLENTY of power and that the WiFi signal covers the area!
There are still a few finishing touches we’re waiting on in addition to the screens. We need gutters and downspouts, to finish the paint on the outside siding, a few more lights and switches wired in, and some interior trim.
The next part of this crazy project is landscaping – but that may have to wait a while. What do you think of the new porch and the new look?
It’s been a dream of Kat’s to explore Peru and hike Machu Picchu for years now. Thanks to her influence it also became a dream of mine.
Before we get started on the details, here’s a link to the curated photos of our trip. I took thousands of photos, and these are the ones that stood out the most. Click each of these images below to open up a gallery for that part of the trip.
Last year we were able to make this happen! We trained for MONTHS leading up to the Peru trip with all sorts of hiking and biking to get ready for the physical part of the challenge. We spent hundreds at REI getting all the right packs and gear we thought we’d need. We took all this gear on hikes all over the Southeast in preparation (like Mt. Mitchell in NC and Dragon’s Tooth in VA). Kat even went all-out and put dive weights in her pack to prepare for climbing at higher elevation.
We found a guide company, Kusa Treks (who we’d highly recommend), and invited some of our closest friends to make the adventure with us. It wound up being a trip with 5 people total. This was fantastic as we got what amounted to a private trekking experience.
I’d like to write up a post in the future that contains some more details.
The cast of characters
Kat & Jason
Nicole & Justin
Best part of the trip
New thing that we learned
Thing that surprised us the most
I think the format should probably be one post for the trip overview, and then one post for each individual section. It seems like I’m looking at a lot of writing work. Consider this post the pre-overview. Leave a comment if you’d like to see anything else covered.
I’ve been using dynamic IP address services from no-ip.com for a long time to give a DNS name to my dynamic home IP. I remember having a no-ip.com address in college around the early 2000s for my dorm, then apartment, computer. I went through a hiatus after college where I managed my domain name to IP mappings manually for a few years (and my own Bind setup), until it seemed like the ISPs started giving me a new address monthly and the burden was too much. I also sold the hardware the DNS server ran on at some point during my moves.
I was happy to see that after over 10 years away, no-ip was still there, and got signed up right away. I have an Ubuntu Linux system as my home desktop (and server really) and was glad to find a client that seemed to run on it. It was a little finicky to get going and was a black box sort of client to install. That wasn’t a good sign to start.
Then came the emails. Oh my god, the emails. Every 30 days they want to make sure you’re still there, and have you verify your domain name. They give you a 1 week notice too, so this means every 21 days you’re getting an email to verify that you’re still there. If you don’t verify – they say they’ll delete your account. When you try to click the email and go to the site it’s VERY clear they’d rather have you sign up for a paid account. Every 21 days for a few years I got nagged until I couldn’t take it any more! They clearly told me that I should go somewhere else for my business if I didn’t want to pay.
This sort of things just bugs me.
At the Open Source conference All Things Open, someone mentioned DuckDNS and I decided to give it a try. It’s been a night and day difference from no-ip so far, for the better.
Here’s what I like:
There is no black box app or script to install on my Linux box. They just use cron and wget.
The instructions are clear and easy to copy and paste.
No one has emailed me anything yet, and since they have ZERO marketing team, I’m assuming no one will.
If you want to get started I highly recommend them. If you’re running a Linux server it’s dead simple.
The whole idea is that you sign up on duckdns.org and get a unique key for your desired domain name. You take this unique key and their copy and paste script and run that every 5 minutes as a cron job.
Every 5 minutes, your server uses wget (called via cron) with the duckdns URL and key and their server figures out your external IP and updates it accordingly. It was ridiculously easy to get started and used systems I already know and love (bash and cron).