Category Archives: Blogs

Apologies…computer problems have surfaced again

I know it’s been a problem to get to iLind.net for the past several days. It’s been off-line periodically. And I’ve been blocked from access most of that time as well.

The problem is apparently heavy external traffic that overloads the host’s resources. I’m still trying to understand what/who to blame, and figure out how to fix it.

And there’s a potentially related issue. Several people who have subscribed in the past report they have not been getting the emails alerting them to new posts.

This is all above my computer pay grade, so I’m struggling to cope. Hopefully I’ll get it resolved before too long!

In the meantime, cross your fingers!

About those dogs and cats

Here’s a Sunday “get ready to waste some time” post.

Someone asked me this week how long I’ve been taking photos of dogs on our early morning walks at dawn. I assumed he was talking about these Kahala dogs, and said I had started when we moved from our home in Kaaawa to the remodeled version of my parents’ home in Kahala. That answer was “about 9 years,” since we moved her in August and September 2015.

But then I thought about it, and the morning dogs actually go way farther back than that.

First, to be clear. We live in a feline-centric household. But we both love dogs, although introducing a dog into our world would be pure chaos, so we’ve avoided it. But it means that we’ve always enjoyed meeting and greeting other people’s dogs.

It’s complicated because I’ve been blogging here for more than 20 years. I registered the domain, iLind.net, on January 27, 2000, and shifted my small former site here soon afterwards.

To further complicate things, back then I was hand coding each day’s entry, and trying to manually provide ways to track back to prior posts.

Years later, I gave up and switched to using WordPress to do most of the heavy lifting.

Tracking back through posts done since the switch to WordPress is straightforward, although it can be time consuming, page by page.

Going back beyond that requires some digging through the original blog files that are kind of haphazardly organized.

Here is about the best I can do.

The earliest collection of dog photos I’ve found appeared here on June 11, 2001. Kamehameha Day. And the first dog in that first collection was Mr. Kolohe, who lived just at the end of our short street, where we had to walk past his house every morning.

And here’s what I wrote about Kolohe, the first dog pictured in that first collection 23 years ago. Click on his picture to see that first, long-ago collection of Kaaawa morning dogs.

Kolohe was the first dog. He lives just a half-block away, and would greet us every morning. Then I gave him a dog bone. Now he’s very polite about it, but he wants that bone. Every morning. His buddy & companion, Ricky, is gone. We haven’t wanted to ask what happened.

The rest is history.

I need an easier way to browse through the old collections of dog photos, but that will take some thought and quite a bit of work. Many of those early photos need an update using modern software to improve the quality.

For a period of years, I kept an updated list, which you can easily browse through using that link. That list included from the beginning of 2005 through early 2011. The photos didn’t stop then, but this path to finding them ended.

Same thing with cats. The photos of our cats also go way, way back, all the way to January 1998.

But that’s another story.

About those memoirs

The positive reaction to yesterday’s post from the memoirs of my great-great-grandmother encouraged me to start thinking about how to proceed.

Initially I just had a vague idea of going through the manuscript and dribbling out a bit at a time in a series of posts. But I quickly realized that’s more complicated than it sounds at first glance.

First task would be to decide how to carve out just enough for a single post. And how long should each single post be?

Not too long, I think. Maybe 1,000 words, max. That’s going to be an editing job, even if I only plan out a few posts at a time.

The manuscript is about 250 pages. Say that translates into two pages per post. Something over 100 posts. Perhaps one every several days. It could take a year to do. Too long? Will readers get hooked or bored? I don’t know.

Then there’s a simple decision. Do I double check my sister’s text against the original scans of the handwritten manuscript to see whether the typos or odd words are in the original? The editing job gets more complex if the answer is yes.

So I went ahead and looked at the first chapter. Well, actually, the first chapter was all about Ellen’s description of her family, based mostly on family lore. And those recollections are annotated by my sister, who found much of the information to be wrong, and more unsupported. So I skipped ahead to the first narrative chapter, looking to see if there are natural breaks that would assist in breaking it up.

As started reading, I could almost hear woman’s voice, perhaps with a slight southern accent, reading aloud and telling the story. My thought—A perfect serialized podcast! Oh, good idea, Ian. Even more work, editing for someone to read out loud in order to make the podcast.

Now I’m hopelessly mired in the potential complexities of it all.

I think I have to go back to the beginning. Think Little, as poet Wendell Berry once wrote. That’s the way to start. The rest can, perhaps, follow.

But then I start thinking that this is a project that could stretch out for quite a while. Does it need its own subdomain, where followers can bypass the rest of iLind.net? How hard is something like that to set up?

More complications, since we’re in Seattle for much of the next week. I shouldn’t start thinking of this kind of stuff while on vacation!

Today’s extended outage was just a server crash, not an attack

Well, after being knocked offline for about 18 hours, my hosting service got this blog, and others, back online somewhere around 3:30 p.m.

Here’s the message sent out to explain the outage.

Earlier today, an automatic update to the DirectAdmin service unexpectedly disrupted the Apache/LiteSpeed web service on some of our shared servers.

Our team immediately took action upon discovering the issue, and we worked diligently to resolve it as quickly as possible. We understand the inconvenience this may have caused, and we sincerely apologize for any disruption to your services and workflow.

Rest assured that the issue has been addressed, and all services have been fully restored to their normal functionality. We have implemented measures to prevent similar incidents from occurring in the future and are conducting a thorough review of our update procedures to prevent such issues from happening again.

We greatly appreciate your patience and understanding during this time. If you have any questions or concerns, please don’t hesitate to reach out to our support team, who will be more than happy to assist you.

I’ve been with this hosting service for many years, and this is the longest disruption I’ve experienced.

And thanks to all those who contacted me “just in case” it had gone down without my knowledge.