Other staff: I’m having trouble logging in to website A. My password doesn’t work.

[Me thinking: That’s weird. When I set up your account, the password worked. I told you to change it. So maybe you forgot your new password. We haven’t changed anything to about the login process.]

Me: I reset your password. [sends new password]

Other Staff: The new password doesn’t work. But I can log in with Google.

Me: 😶 Website A does not have sign in with Google. What website are you actually on???

Morning! Good day for phishing, ain’t it?

Hopefully one of those corporate phishing trainings

Other staff got owned good sir. Best to take away any devices from them, fire them, and recommend them to pursue a career as a goat herder.

Luckily this wasn’t phishing. It did scare the shit out of me when this staff person made this claim though.

Website A has this weird setup where the homepage will redirect to Website B homepage. Website B has Google sso. And logging in to Website A CMS goes to the homepage and then Website B homepage. So after log in, a user has to directly go to a CMS page on Website A if they want to get to the CMS.

It’s a stupid setup. I did not come up with this stupidity. But I’m going to use this as more evidence of why my employer needs to retire website A. My brain is 🤯 after learning how much time and money was spent with a software development company for a load of 💩.

@Lensflare hu ha!

@Lensflare I understood that reference 😀

Why not merge B into A and use just A?

You need a nice girlfriend who treats you well. I'll find you one. A man shouldn't be alone

@max19931 Website A was intended to be a CMS that staff could use and not contact the software development company to build out pages on site B. All this happened before I was added to the staff. A lot of money spent trying to not spend more money 😵‍💫

@AvatarOfKaine I’m just glad marijuana had been legalized where I live. So I can check out with gummies and cookies.