A tastingspoons update
Unbeknownst to all of you readers, there’s been a problem brewing behind the “face” of my blog. Some hackers have created a robotic script and have been trying to gain access to my blog. Trying to take it down – just for the fun of it. No, we don’t know where they’re from. It’s a game to them – to try to access blogs or websites, go in and destroy stuff, so the website can’t operate. Such hackers are wreaking havoc all over the world doing this – it’s not just me or my blog. Once the blog is taken down by the hackers, the owner has to have a programmer recreate it to get it up and running again. You can’t prevent them from trying, although I’ve done various things to discourage the attempts. But they keep trying. Last month I had over 360,000 attempts to get into my blog. Can you imagine? Good thing I have a really strong password. Makes me think I need to create a new password that’s at least 160 characters long. With numerous numbers, symbols, capitol letters, etc. You know the drill on that stuff.
The problem was that all that robotic scripting (the login attempts) ran up my GPU usage, and I got dinged to the tune of about $50 last month on overage fees. Dang! So I had to take a hard look at my blog. Did I really want to keep doing this, running up these charges. Sara posts when she can, but she’s so busy at her full time job, she rarely has time, or remembers to take pictures of what she creates. Hard to do a post without a picture. So I’d almost decided I was going to close/shut my blog down altogether. But NO, I’m not.
I looked into some options, and have decided to move the blog to a different platform that doesn’t charge extra for those GPU overages. And, on top of that, my daughter in law, Karen, has decided that she’d really like to be part of the blog herself. She and Powell, and their son Vaughan, are all foodies of the first order. I’ve posted many recipes from Karen, or Powell, and some months ago I posted two recipes from Vaughan (13) who stayed with me for a few days.
Which means that I will be taking a more back-seat role here. After 14 years of food blogging, I’m cooking less, although I have to say I still feel that pressure to keep trying new recipes that might be blog-worthy. Sometimes they’re successes, sometimes not. Do I eat out much? No, not really, and not-at-all during this last Covid-year. Do I buy ready-made food? No, not at all. On a regular basis I eat a big green salad (with some kind of protein on it) about 6 evenings a week. Can’t really blog much about that, now can I?
I’ll still blog – I’m sure of it – because when I do make something new and fun, I’ll want to tell you about it. As I’ve explained before, when that happens, my fingers “itch” to get to the keyboard to tell all of you about it. Surely that will still happen.
As the next few weeks go by, I’ll introduce you to Karen, and Powell, and Vaughan, and hopefully going forward, you’ll get to know Karen’s cooking style. And Sara will chime in now and then too. I think I’m going to Powell & Karen’s for Mother’s Day, so perhaps we’ll take pictures and do a blog post from there. I need to spend some concentrated one-on-one time with Karen to acquaint her with how to blog.
There will be a difference on the posting face – we’re going to simplify how recipes are posted. Neither Sara nor Karen want to fuss with the programming stuff (that I do because I like the recipe to look “pretty) to create a box that goes around a recipe. Nor do they want to pdf or create a MasterCook file, either. So it’ll be a post (the narrative) plus a recipe. You’ll want to cut and paste it to use somehow. To make my blog more print-easy, would require major programming – an expense I’m not willing to take on. Remember, I don’t take any advertising on my blog, so anything I do is out-of-pocket. My pocket.
In the next week or so my blog will migrate to a different server – hopefully you’ll never notice a difference, although at some point the blog will be off line for a short while, I suppose. They say they’ll do it at night so you’d not notice. We’ll see how that part goes.
. . . Carolyn T