Although I admitted expected something more modern and Pop-oriented --it is Björk, after all-- the song is most definitely neither Pop nor Rock, but a folk tune. And I found it really cool to listen to.
Thursday, December 11, 2025
Attack of the Murder Floofs
Although I admitted expected something more modern and Pop-oriented --it is Björk, after all-- the song is most definitely neither Pop nor Rock, but a folk tune. And I found it really cool to listen to.
Thursday, November 20, 2025
False Positives
![]() |
| Observed on November 20, 2025. |
Thursday, September 25, 2025
Still More Technical Silliness
An addendum on my post on Tuesday...
Is there some circle of hell where Microsoft is better than Google at something? Asking for a friend.
I'm not being (very) facetious, because Microsoft's Bing Webmaster Tools has accepted Parallel Context's sitemap.xml file, but Google has not:
![]() |
| Microsoft's Bing Webmaster Tools... |
![]() |
| Google's Search Console... |
I even looked at the XML file just for curiosity's sake and discovered there are so many posts on PC that there's three sub-XML files. So, I tried uploading them directly to the Google Search Console with the same result as you see above. At this point I'm tempted to think that the problem is with Google, not with the XML file. After all, the sitemap.xml file is created by Blogger, not me, and last I checked Blogger is owned by Google.
Oh, and I got yet another response to my request for indexing after fixing my "Redirect error".
![]() |
| This came in on September 24, 2025. |
Yeah, right. I followed their analysis tools linked in the help section and discovered that they're being redirected to the mobile version of the website. Yeah, so... There's a mobile version. That's a problem how? If you're running a version of Chrome that is mobile in nature, you're going to get the mobile version.
/sigh
Anyway, I apparently had poor ratings for Accessibility, so I had to change PC's layout to one of the "new" standards, which is a slightly different colored version of the original, and got this:
![]() |
| This is for desktop, as of 9/25/2025. |
![]() |
| And mobile as of 9/25/2025. Note the comment about redirect in the listing. |
I had to change the mobile settings to show the full website, which I really dislike. The whole point of a mobile setting is to make it easier to read on a mobile device. So after some more tweaking and switching it back to what I consider a "better" mobile setting, I got this:
![]() |
| As of a bit later in the morning on 9/25/2025. |
Accessibility went down, but the other scores went up.
Still, there was one last trick to pull off, and one that I'd been meaning to do anyway, which was to change the main art piece.
![]() |
| It'll do for the time being. |
However, the result in the tools was a whole lot of "meh"...
Tuesday, September 23, 2025
How Do You Fix Something When You're Already Dead to Google?
Curiosity can be a real bitch at times.
After I’d made this post about how Shintar had discovered that Parallel Context wasn’t showing up in Google’s search results, Bhagpuss’s comment led me to investigating what the Google Console was all about. For a guy who likes to pride himself about being on the internet before the first browser was invented, the fact I never knew the Google Console or its Bing equivalent existed was a blow to my ego. Still, I swallowed my pride and poked around.
Once I started looking over the Google and Bing consoles, that was it. Like any kid who read his share of Encyclopedia Brown books (and Sherlock Holmes stories) I love a good mystery, and on the consoles I found mysteries in spades.
For starters, why was the Google Console telling me that I had a security alert on my blog?
I knew I hadn’t deliberately done anything stupid such as linking to a picture from a sketchy website –I’d gotten tired of picture links vanishing underneath me so I simply made local copies with citations—so it had to be a link to a website that had gone bad. Or worse, something about Blogger that had raised the ire of Google.* The Google Console was completely unhelpful as to which post or link was the offender, so I was left to my own devices to try to puzzle through this.
The best course of action was to start with the links on the main page, because those are found on every blog page. If that didn’t work, then I was going to have to slog through every single post to find the culprit. I began with the blogs with the longest period of inactivity and worked my way back toward the newest, and I eventually found the culprit: it was Hawtpants of the Old Republic, Njessi’s SWTOR blog. She’d had periods of inactivity followed by a few clusters of posts, but the last post on her blog had raised my eyebrows because it didn’t have Njessi’s authorial voice. I’d even fired off an email to her asking if her blog had been hacked, but I never got a response. This time when I clicked on the link, however, her blog simply exploded with all sorts of spam pop-ups and stuff completely unrelated to an MMO blog (such as online gambling). I cried a little inside, removed the link to Hawtpants of the Old Republic, and submitted the blog for security review to Google Console.
It took a few days, which surprised me given how quickly Google tends to yank people's access to things, but I got this emailed response:
![]() |
| This was on September 3, 2025, for the curious. |
Okay, so I then submitted the site for indexing, and several days later I got this response:
![]() |
| This was on September 14, 2025. |
WTF, Google. I tried hunting down what they meant by that, and at that moment I learned something important: Google's help pages aren't worth crap. There was very little in the way of anything resembling constructive assistance, probably because Google, like Microsoft, wants you to pay for the privilege of fixing your website. Eventually I figured out that there was another problem on the blog, likely a link that is going to a different location than what the link expects.
Well, this is going to suck trying to figure out which link is the problem. Just because the link doesn't go to where you expect --yet is NOT a link to a security risk-- shouldn't be a reason to not index the blog. My disgust with Google's lack of assistance aside, I started poking around once more.
![]() |
| "URL is not on Google". No shit, Sherlock. From September 20, 2025 |
Turns out it was this little widget that was the problem:
![]() |
| NOTE: This is the correct widget, not the one originally posted here. |
Surely, this couldn't be the root cause, could it? Could it? I tested the live URL, and...
![]() |
| It's the same result as I got a few days ago. |
Okay, we're getting somewhere. So I resubmitted the page for indexing and waited.
And waited.
And waited.
And I finally got a result:
![]() |
| Really? I mean, REALLY? From September 21, 2025. |
Basically they didn't index the page because the page hasn't been indexed. If that wasn't a truly abominable case of circular reasoning, I don't know what is.
So... I pretty much have gone as far as I can with indexing, because Google will eventually fix the "Crawled - currently not indexed" issue when it gets around to it.
At least on the bright side I cleared up a security issue and a couple of bad links, but nothing resembling a positive result. Parallel Context is still dead to Google.
*Oh, the irony of THAT one. If Google were complaining about its own Blogger service, someone should get these two to talk together. Well, maybe not, now that I think about it; Google might decide the easier course of action would be to kill off Blogger instead.
Tuesday, October 22, 2024
More Silence on the (Guild) Banking Industry
Saturday, October 5, 2024
No FDIC Insurance for Your Guild Bank
Tuesday, September 24, 2024
The Great Blizzard Bank Heist
Wednesday, June 12, 2024
Speaking of Pandora's Box
![]() |
| It's from Pinterest, but it's a screencap of HBO's Westworld. |
Thursday, August 17, 2023
Keeping the Fire Going
![]() |
| From Jinxed Thoughts. |
![]() |
| I had the top three books, but this is a sampling of what was put out. From u/aelphia on this Reddit thread. |
![]() |
| From the Lone Wolf Fandom Wiki. |
Saturday, April 15, 2023
It's All Filler in the End
![]() |
| This would have been one of the pics I'd have used in that GIF or plug-in. If nothing else, Guild Wars 2 has some fantastic graphics. And yes, Mikath is yet another redheaded bearded guy. |
![]() |
| Feels kind of weird seeing this graphic. I tried using this as a background for a short while but it was far too busy. This was even before my (brief) raiding career. |
![]() |
| Sith Inquisitors are the Warlocks (aka Purple Mages) of the SWTOR universe. |
![]() |
| The inner cover of the old Moldvay D&D Basic Set. Willingham's artwork still holds up to this day. |
Sunday, October 9, 2022
An Homage of Sorts
![]() |
| Something about Linna's Mona Lisa-esque smile fits that guild name perfectly. |
![]() |
| I try not to be a packrat, but with WoW you never quite know when some of this stuff might come in handy. |
![]() |
| "Yes, Mistress Elsharin. I like it too." |
Saturday, August 13, 2022
Security Alert
![]() |
| Oof. |
Tuesday, May 24, 2022
Someone Picked at a Scab
I saw this video today about "what's going away when Wrath Classic drops"
And I was sufficiently annoyed at his flippant "if you're one of the 4 or 5 people on your server who doesn't have an Amani Warbear" that I felt it merited a response.
If you've got Hyjal / BT gear, then yes, Zul'Aman is "a pretty chill raid." Even if you're in SSC/TK gear, you should be fine. But if you're in a raid with primarily Phase 1 gear or quest greens + pre-BiS, ignore what WillE is saying. It's a raid that is highly dependent on gear checks and having the right composition --such as having a Priest to do periodic mass dispels on the raid during the Vol'jin fight-- that if you don't have those you're not going to finish the raid.
And god forbid if your raid is caught in between about 6 other ZA raids --not to mention the other progression raids of other major guilds-- so most of the personnel for the critical slots (Tanks, Healers, the aforementioned Priest, Shamans) are already either locked or are busy. And those roles are ones that I have no desire to pug. I've been in enough pugs that I know that those roles are ones I want people I can trust with, and a random pug --assuming you can even put one together right now on the server-- isn't where you're gonna typically find them.
I suppose that the entire tone, which is a breezy "oh, this is some box you can check off before Wrath drops but everybody will have this anyway", really ticked me off.
Probably a good deal of it was because I'm not going to get the "Hand of A'dal" title because I never got a Kael'Thas kill in Phase 2. I never show my "Champion of the Na'aru" title anyway, and I'd certainly never bother showing a "Hand of A'dal" title if I got it, but the fact that I did get it would mean something to me. And here was yet another reminder that one of the few personal goals I had in this expac --to raid up until Illidan was downed in Black Temple-- was not going to get completed just kind of set me off.
***
I guess what drives my obsession about this is something I remembered back in original Wrath.
Remember the blog I Sheep Things/Oh My Kurenai? I certainly do.
And I remember Rhii's steady stream of updates on her guild's attempts to kill Arthas in ICC before Cataclysm dropped.
But more than anything else, I remember her despair at her realization that her guild wasn't going to be able to do it, and her GM --of all people-- took off to run with another guild and down Arthas instead of trying to finish the job in their own guild.
As I wasn't a raider at the time, I could only offer some sympathy to her plight, but I didn't really experience it firsthand. When I was a guest on the Twisted Nether Blogcast back in ancient history, there was some disbelief that it was a big deal to down Arthas by the end, with the hosts thinking it wasn't that hard by then because of the buffs and whatnot, and because I knew Rhii's struggles I disagreed. Now I have found myself in her exact same situation, knowing that one thing you wanted to get but you aren't going to get it, that hurts. It's not like a kick in the shins, because that is intense for a brief period of time and then fades, but it's closer to a long, slow burn, like when you've got acid reflux. Even when you think you've put it behind you, it's still lurking to spring out when you least expect it.
Like now.
Wednesday, July 7, 2021
A Brief Glimmer
Shintar, over at Priest with a Cause, posted today about her experiences lately in TBC Classic. In their own way, they provide a counterweight to my own impressions of the expac, given that while I started from L1, she was able to go to Outland from the moment the Dark Portal opened only to discover some of the same feelings of FOMO that I was experiencing. But as she explained in her post, what she thought initially was just FOMO has turned out to be something else, where her relationship with her guild has not been what she thought it would be when TBC Classic dropped. In its own way, her guild and my own are doing similar things, where they spend most of their time working on their individual checklists rather than enjoying the game as it is.
And in both of our cases, it can be an alienating experience, realizing that your relationship with your guild isn't where you thought it was.
In her case, she feels she's treated as just another flavor of the month Hunter, and some people in guild can't even remember her name right. That matches a similar situation I find myself in, where people can't remember that Card is no longer my main.
Once every couple of days I get a whisper from somebody saying that they miss running or raiding with me, but then in the next breath they say they're just too busy with other things. Well, out of game issues I understand, but in game? That's a choice that you make. You can make yourself feel better by a drive by hello, but the reality is that you have control over what you do in game. To have all of your boxes checked prior to entering Gruul's Lair or Karazhan is placing a lot of pressure on yourself.
Of course, there are limitations to that. A Mage will have to acquire tanking gear before they step foot into Gruul's Lair, and a tank will have to get enough of the right type of gear to make it even worth their while entering into the Phase 1 raids. But chasing 9/9 pre-raid BiS slots with a vengeance? Or getting all the patterns for Enchanting? Or who you hang with in game? That's a choice you make.*
***
I have some friends in game that I miss, not because they're not playing or anything, but because they server transferred. I was assured that they left because they felt the larger server would work better for them, but I can't help but think that if I had the chance to spend more time with them they might not have considered transferring so much.
At the same time, there's only so much of me to spread around. I have to make decisions based on the time I have, and I have to live with them.
***
I was contemplating all that when we were preparing for last night's Karazhan raid. We had almost enough people for two raids, but we ended up having to get a couple of puggers to fill the last two slots. We were trying to find a healer when I ran into one of our regular raiders from our Saturday Night Blackwing Lair runs. We hadn't spoken since the series of raids had ended, so we were catching up on what we'd been up to and I noticed that she was at L70, so I asked if she'd gotten into Kara yet.
"No," she replied, "I'm geared and ready to go but no luck."
I blinked.
"You know, we're in need of an extra healer for Monday night," I said. "Would you be interested?"
Her reaction was somewhere along the lines of "hell yes!", so she hopped onto our Discord and immediately signed up.
Shortly thereafter another regular from our BWL and AQ20 runs also hopped on to sign up as melee DPS.
Problem solved.
But as the raid approached, I grew nervous. This was not only going to be my second time entering into Karazhan, but a first as an actual lead for the place. And you can only read/watch so much before you have to go out there and actually get into the raid and do it. Thankfully, however, the overall lead was the lead for all of those ZG/AQ20/BWL raids I'd done over the last several months, and once we started I began to relax. It wasn't the same raid, but it was the same person.
She did a fantastic job distilling a fight to the most basic components, and while it was a learning experience for about close to half of the raid, it felt so much better and smoother than last week's run. Even when a disconnect zapped my macro for handling loot, we just rolled with it.
We got what is supposedly hardest opera event, the Wizard of Oz, and wiped twice, but the third attempt was as smooth as butter. We accidentally pulled Moroes early and wiped, but we recovered the next time.
And there was one memorable trash pull where everybody went down except for the Warrior tank, the Pally healer above, and me. We had three of those arcane creatures on us, and the tank kept aggro while the Pally healer kept him alive, and I improved my positioning enough that I didn't take damage so I could DPS down the trash. "I thought we were going to have a wipe," the raid lead admitted.
"I thought so too," I replied. "But that was an awesome job tanking!"
"An awesome job healing, you mean," the tank replied.
"Hell yeah!" And if I hadn't run into her randomly out in the Old World, that pull would have turned out completely different.
At the end, we hung around late --because of some trash wipes-- and we killed the Prince on our second try. It felt.... well... like we knew what we were doing. Even though I'll admit that I didn't.
Afterward, I sent the raid lead a message via Discord that she did a great job, and that I really missed this over the past month of leveling alone. I got a thanks as an acknowledgement, but really that message was as much for me as it was for her. I really had missed our regular raids together, with some of the regulars across several guilds, and how we came together and had fun.**
***
It felt... good.
Like I wrote to the raid lead, it was the best I felt in game in a month.
It doesn't cover up a host of faults I've discovered about this expac and how people are pursuing it, but it did provide a welcome respite from the in-game shenanigans. It also gave me some hope that perhaps I won't have to take the drastic route and leave the guild (at minimum) just to find my place in TBC Classic. There's still a couple of months of Phase One ahead of us, but this is the first glimmer of hope I've had in a while, and for now I'm holding onto it.
*One of the people I knew from Classic, upon hearing a gratz aimed at everybody in his guild who made it to L70 within two weeks, quipped about "that was only the 'no life' crew that sprinted to L70." To which I laughed.
**This doesn't mean I suddenly started liking Karazhan; I haven't. It's just that I liked the raid itself rather than what we were raiding.
Saturday, May 15, 2021
One Last Update
This morning I woke to receive a "re-evaluation" notice from Blogger, which said they didn't find any malware, so they restored the posts.
Hell, I could have told them that.
What I don't get is if they get a report about malware they don't have a quick scan of the offending pages. That'd shake out any malware present and not force them into a manual re-evalutation.
But hey, I only work in IT Security.
Friday, May 14, 2021
Oh, How Nice
Apparently PC has been reported as a "Deceptive Site", so I filled out a form to Google to dispute this.
This blog is so freaking old that I'll have to go back and see which link is the "bad one", which is likely an old blog that no longer exists.
Oh. Yay.
Wednesday, March 17, 2021
It is Mine Now
When I discovered there was no such thing as Azeroth After Dark as referenced in yesterday's post, I decided to jump on it.
I am now the proud (?) owner of azerothafterdark.wordpress.com.
What I intend to do with it I have absolutely no freaking idea, but at least it won't suffer the fate that internet users in the 90s will remember with whitehouse.com. Or that time when Dick's Sporting Goods didn't own the dicks.com website.
***
Oh, and Happy St. Patrick's Day! Now you can go have a good cry first....
And then cheer yourself up with a few happy jigs and reels....
Wednesday, March 10, 2021
A Short Mid-Week Boost
Courtesy of Shintar of Priest with a Cause (among other blogs).....
She sent it to me with the comment "Everybody who raids Naxx needs to see this..."
And she's absolutely right.
Saturday, December 5, 2020
Partway There
Before you ask, no, the blog hasn't been hacked.
And no, I don't believe this is the end point either.
I tried to put a background together, but Blogger just did not like the dimensions of my uploaded graphics, so I've got to come up with something that works.
But yes, after 2012 (roughly) I'm starting to make major changes to the blog design.
Back when black was edgy, the blog looked roughly current. But now, in the Age of Covid, it just looks like a funeral. And I've been to enough funerals this year.
So this is what I've got so far.
It's.... okay. Serviceable, brighter than before, and something I can work with for the time being while I clean stuff up. I've never been able to get a GIF that I liked for the title graphic because it costs money to buy a product that allows me longer frame times, so I'm going to have to pick something out of my screenshots and run with it.
And, truth be told, I need to clean up the sheer size of the sidebars and make it a bit more PC friendly rather than it looking like a MySpace page.
But hey, the black is gone, and that's fine with me.
Friday, August 25, 2017
Years in the Bunker
Her most recent post was about single player versus multiplayer games, their profitability, and the potential future of Mass Effect titles. While I think that ME will make a return after the bones of the system (the Frostbite engine in particular) are fleshed out enough to accommodate the RPG that Bioware wants to create, the lure of cashing in on ME style multiplayer might pull the game in a direction that fans of Bioware RPGs might not like.*
That said, a link to this article by Kotaku author Jason Schreier really caught my eye. It was a detailed article on the development process for ME:A, and everything that went wrong in development. (TL;DR: a LOT went wrong.) Schreier even mentions in the article that it was amazing that ME:A actually shipped at all, given all of the issues with the development process.
But for me, reading the article felt like deja vu.
As I alluded to in a previous post about the potential issues of new software releases, I worked for several years in a software development house. Those five years were some of the best years of my life, when I worked hard for bosses that both pushed me beyond what I thought my limits were and yet respected my effort and output. I made some friendships that are still going strong today, and the skills I learned during my years in the barrel (so to speak) still serve me well today.
But those five years were also among the most stressful I ever experienced.
When you're on the inside of a development house there is an occasional tendency to get consumed with the work that's right in front of your face. Teams who work together day in and day out develop the feeling that their (piece of the) project is the most important part and frequently miss warning signs. But if you can break out of that silo, you can also see a train wreck coming a mile away. Sometimes it's salespeople who overpromise to critical customers without asking in advance "can we do this?"; sometimes it's the defection of critical personnel that a company had relied upon for years as a hero to fix the emergencies at the last second; other times it might be the promotion of people who prove to be incompetent at managing a development team; and then there's the occasional directive from the top to change direction in a project. Sometimes you might just get three or even all four.
I've been in good releases and bad releases, but the one that still haunts me is the last release I was involved in, which was a real shitshow.
This particular release was a perfect storm of overcommitments to customers, loss of senior staff to higher paying jobs**, an inflexible deadline set by said commitments, and major stability issues with the development environment. In spite of all of the (new) development staff we had, there were personnel shortages during the entire release cycle as the company had underestimated the new devs' capabilities.*** I was our team's representative on the weekly release meeting, and every week there were major complaints from all of the QA teams about the quality and stability of the product. We felt that the product needed at least 2 months to straighten out all the bugs, but we were informed by upper management that was simply not possible.
Things were so bad that they had to create a tiger team dedicated to simply having a workable daily environment for devs to code with, because every other day it seemed like some new code change would crash the entire system. I got drafted into that team for a couple of months, and I lost a lot of sleep because my pager (remember them?) would go off multiple times a night letting me know that a build had failed and we needed to find what code change broke the system.
In the end, you can kind of guess what happened: the product shipped, it was incredibly buggy, and the company took a lot of flak for it. A year and a half later, the company was gutted of "overpriced personnel" and sold to a competitor.****
So yeah, I know what it's like to be in Bioware's shoes with the result of the ME:A release.
The thing is, the development cycle didn't have to be that way.
Blizzard is practically alone in not announcing a release date until it feels that the software is ready to go. But that's because while Blizzard has given themselves a ton of goodwill from the gaming community over the years, they have also their reputation as a producer of good and stable games at stake. Of course, they have had their share of release fiascos lately --such as Diablo III and Overwatch-- so they're not immune to problems either. But I do believe these issues also stem from the pressure that Activision is placing on Blizzard to release on a regular schedule, in much the same way that ME:A would have benefited from an extra year of work rather than release on a date set long in advance (whether internally by the staff or externally by the suits).
The ME:A release disaster was another perfect storm of staffing, management, focus, new tech, and time. And the Bioware Montreal office paid the ultimate price by being shut down and absorbed into EA Motive. But this disaster should be used by Bioware to focus on the weak points and improve them, not to go and hide. Shelving the (single player) Mass Effect franchise would be the wrong solution to the problems of ME:A.
Now, if only the suits would let Bioware work out the solutions...
*Think of it this way: Blizz was known for the Diablo, Warcraft, and Starcraft franchises. Now, along comes Heroes of the Storm, Hearthstone, and Overwatch. The money that Blizz gets out of the latter three have muscled aside the original three, and so guess where the development dollars go? While WoW still pumps out content but it is no longer the star of Blizzard's lineup, and that means that WoW will take a back seat to content for the new titles, which are correspondingly cheaper to develop and maintain. (Such as a lack of story content to the level that WoW/Diablo/Starcraft have.)
**This was the late 90s, when the original dot com bubble was inflating rapidly. I knew several of these people very well, and almost all of them cited the desire to a) make more money and b) feel appreciated. While this may sound at odds with my statement as to how I was respected, you have to realize that these people had been taken for granted by management that they'd be around to clean up everyone's messes. They'd been around for a decade or longer, and they'd realized that the internet revolution was passing them by, so they jumped ship.
***The new devs also had an alarming lack of discipline. If they were assigned to work on boolean logic issues, we'd frequently find them deep within the mathematical algorithms instead, claiming that they wanted to see where the bug led them. We had to explain numerous times that it's not your job to worry about the algorithms, we have an entire math team to handle that. Hand the bug off to them and let them deal with it. Curiosity is one thing, but when you've got 10 bugs to work on and you need to get them fixed in 3 days you don't have the luxury of drilling down past the code you know.
****By then I'd already left the company, as everybody could see that the CEO was going to cash in by selling us and getting his golden parachute.



























