Waking up this morning, I noticed that my blog’s whole alignment was messed up because I had mistakenly updated the theme… so I had to hunt down the old version of the theme that I was using, and had been using for years, and reinstall that on here. That still leaves me with a few minor things to do like adding the word count back to blog posts since I had incorporated that into each post I made (and posts viewed through the main URL), and I might have to put the Google Analytics code back on this blog. Next time WordPress tells me that there’s something available to update I’m going to be extremely careful about what I allow it to update. Although I love earlier versions of this theme, I do not like the changes that were and have been made to later versions. And sadly, it’s not like you can just go back and undo theme updates.
I also installed one of the fonts that the theme recommended trying to fix this, and I love how that looks.
I think this might have been using a second choice font according to the CSS, and I installed the first font that it’s been asking for today. Everything continues to be aligned just the way I want it, although it looks a lot sharper and I have no regrets at all about that. I just wish I hadn’t accidentally upgraded the blog theme…
This is a screenshot of me and a friend ripping on Tumblr’s “site security”. They continue to refuse to acknowledge that there was a recent data breach, or data leak, even though passwords have now been brute-forced into plain text (they did not use SHA-1 cryptography to hash their passwords, let alone salt them… and I’m not going to get into the fact that passwords hashed with SHA-1 cryptography are now easier to brute-force, that site managers should look into using higher-leveled cryptography). But it is what it is, and I tried to alert them to the problem. It’s out of my hands now. It’s not my problem. I don’t have an account on their site, so none of my data is going to continue to be compromised, especially since I use burner e-mails for fandom accounts and do not replicate passwords. However, I can’t say the same for their other users. I can’t speak for them. But even the barest of statistical analyses would have to say that some of them would have to be using professional e-mails for these sorts of things, that they were replicating passwords, or even that they were using universal passwords (in 2022 of all years, which I am not even going to get into… heh).