Welcome to #CheckIn for THURSDAY 2026-03-26


This work week so far has been consumed with horrific experiences with tech support, both GoDaddy and Microsoft. Make me feel better (?) and tell some of your horror stories from this arena.

This post comes to you from @((( David "Kahomono" Frier ))) via the official #checkin posting account. Program note: Please comment, and feel free to Like this post, but please resist the urge to Share/Boost/Repost it. Doing that creates an additional instance of a #checkin post for a given day, and tends to fragment or dilute the conversations.

The CheckIn team is looking for an additional mod with the loss of 2 of us from the rotation - @su ann lim and @Rod Mesa. Please contact @Cass to find out more.

To find out more about #CHECKIN, check our site

  • You can participate without being notified.
  • To get notified when the daily #CheckIn post is live just mention it in the comment. Tag @Cass for quicker response.
  • To get off the list let us know by commenting on the current post.

Have an idea for a topic – let us know or even be a GUEST HOST! Just send a message to @Cass

Greetings… Ahoj! Aloha! Bom dia! Bonjour! Bună! Ciao! G’day! Geia sas! Günaydın, صباح الخير , בוקר טוב 你好! Håfa Adai! Hi! Hei! Hello! Hallo! Hei! Hola! Howdy! Halō! Kamusta! Kia Orana! Kon’nichiwa! Mabuhay! Moi! Namaste! Ni Hao! Neih hou! Pagi! Saluton! Sawasdee! Shwmae! Γειάσας! Talofa!

Checkin Legends
@Aline
@Alexander
@Andreas G
@Nat Weaver 🏳️‍⚧️🏳️‍🌈
@Cats of Commons 💫
@Beej Cobalt
@DeanC
@David Calderon
@Dave Higgins [Main Account]
@davidamerland
@Debbie D. 🇨🇦 🇩🇪
@debo
@Deb Zaccaro-Rojas

@Don Little
@Paul Ferguson
@That Harp Guy
@Guy Geens
@gregg taylor
@Griff Ferrell
@Griff Ferrell
@hackbyte Antifa (friendica) 13HB1

@Holly Jahangiri
@Isaac Kuo
@Jacob C
@Janet Logan 🏳️‍⚧️
@Alrekr Járnhandr
@Jay Bryant
@John True Connection
@Jess Nut
@Samuel Smith
@Jodi
@John Hummel
@John MacLeod
@Joltrast
@Jon Alcibar
@Joseph Teller
@Joyce Donahue
@Karl Auerbach
@Katherine Bond
@Kenny Chaffin
@Klaus Lademann
@Lee Rothstein
@libramoon
@Mark Wollschlager

@Nora Qudus
@Michele Hax
@Pedro Subrosa
@Phil Setnik
@Susan ✶✶✶✶
@randy.galbraith
@Richard
@Rob Anybody
@Rod Mesa
@robb
@sheilanagig
@Phil Landmeier (ᚠ)
@smellsofbikes
@Lisa Stranger

@David Sterry
@Andrew Pam

Checkin Hosts, regular and occasional
@Cass
@((( David "Kahomono" Frier )))
@Muse
@Christoph S
@s banerian
@Bob Lai
@Carsten Raddatz
@su ann lim

In Memoriam
@Stan McCann (Uncle Pirate)

@Corinne Howell

We hope you’ll use the hashtag to keep track of the daily post and join in if you’re not on this list. The topic is always open 💕

in reply to CheckIn Posting

I get my tech support mostly from the Linux Users Group of Victoria. If anything happened to Andrew, I would have to become a proper member in order to justify the help for which I would be asking! (I've mostly justified my hanger-on status by regularly giving talks about how I have used open-source to run my theatre shows.)

Too tired to think about horror stories, but I did switch from Microsoft to Linux after MSs operating system irredeemably ate the first couple chapters of my PhD thesis!

in reply to CheckIn Posting

My horror story ---- I run a website for a historical preservation group (ctrc.org). We signed up for Google AdSense and started posting ads.

At first we got paper checks, then direct deposit, and then silence ...years of silence except for an occasional email from google that said nothing.

So I began to wonder - I tried to sign into our account. I could not log on. Google had screwed up the credentials. But how to fix it? You had to log in in order to fix the broken login - Full blown Catch 22.

It took me three years to get it fixed. Finally via private channels I got someone to walk the halls of Google and knock on doors. They had combined databases and managed to totally screw up my account - all the time collecting our money.

in reply to CheckIn Posting

Well, let’s see there was the time (well two times) I broke Amazon. Took them six months to fix the first problem and maybe four or five the second time (but that wasn't as severe).

And they would contact me, but I couldn't get directly in touch with the people in the right place. So each time they responded, I had to call or email and go through the whole thing all over again. Finally sent Jeff Bezos an invoice for my time. Didn't expect them to pay, but it got their attention.

in reply to CheckIn Posting

At one point in time we had several satellite offices in our district. One of them was in a building that had once housed a student loan call center.
They had lots of high speed connections that once terminated there, was a Verizon fiber ring on the campus. Should be easy to keep a 6 person office with a T1 up and running. You would be wrong. The T1 went down one day and a trouble ticket was opened with Verizon.
It took weeks before the problem was corrected. The resulting trouble ticket detail, when printed out in 12p font on a plotter was 7ft ( ~2m ) long. We kept it up on the wall and I got to take it home when I retired. It was truly a keystone cop situation of miscommunication between different Verizon departments, techs that couldn't find stuff in central offices, etc. Many escalations. Good times, except for the folks in the office that made due with flaky ISDN connections.
in reply to CheckIn Posting

I am the tech support. But there's plenty I still need to call in for that I can't do myself. But having spent time on the other end of the phone I'm probably more patient than most, but I also know what to say and how to say it to get what I want. Or knowing when to hang up and call back to get someone else on the line.

Oprah, years ago, told all her audience that if you call customer service and you aren't getting what you want that you should yell louder, which was terrible advice then and it still is now. She started the whole Karen movement. Trust me when I tell you that acting like a decent human being who is talking to another human being who does actually want to help you where they can... you'll get a lot more out of it. Would you want to go out of your way to help someone, even suggesting discounts and perks, if that person is yelling at you, calling you stupid, and hurling slurs? Well the person on the other end of the line doesn't want to either. I've gotten so many discounts, free add-ons, and going the extra mile over the years because I was able to be decent. Now I've raised my voice before, when the person wasn't listening or was trying to dick me around, but it that parent firm tone, not a raving banshee. And if it's really bad, just hang up and get someone else. You never know if the person you are talking to is their first week or they've been there 10 years, if they know what they are doing or just riding a desk for a paycheck. Don't feel like you are stuck with the first person to answer the phone if you really aren't getting anywhere with them.

in reply to CheckIn Posting

We're trying to get a couple of the kids to Guam for the husband's mom's funeral. Both were born there. We're leery of having them travel as just the pair as they were both born on the island, and we're fearful that the Naz-ICE won'trecognize thier citizenship, though the husband served in the Armed Forces. What a totally fucked-up country this is.
in reply to CheckIn Posting

i did less and less person to person tech support as i spent more time in work. more time dealing with servers, network.

i don't recall any horror stories. some people were more challenging. the worst issues we had were dealing with a "collaborating" institution that really just wanted to force us to do things their way. they wasted so much time and money, and effort.

in reply to CheckIn Posting

Drawing a blank on tech support rn, but there was that time that a huge tree took down the power line to our house—and multiple people in different departments at the utility (who clearly did not communicate with each other*) kept telling us they were going to take care of the tree work—til one week after the deadline for us to put in for govt cleanup assistance, when they finally said womp womp, we don't own any trees, that's on you. WHY STRING ME ALONG??

*omitted: lots of speed bumps like phone tag/multiple transfers, "that number is not supposed to be on voicemail"/"oh wow it is on voicemail", etc.

Our power line is still tied to a palm tree, and the pole it used to live on is still laying flat in our yard. That was 2.5 yrs ago.

That was also the incident where I had to go out in the Mad Max hellscape to buy an entire-ass phone on a different service because we were completely incommunicado—our cell carrier had taken a massive crap, and obviously we didn't have our VoIP. (One intersection was so badly flooded, I wasn't sure the big truck was going to make it through without stalling. I later saw on the news that officials had used canoes there for a while.) So after going through all that to get the phone to stay in touch with FPL... 😒

I miss POTS. It just worked.

in reply to CheckIn Posting

Nothing recent to report, I'm getting to know Claude, Nono, and Goose. So much that my (unrelated, lalala) new t-shirt sports this friendly Riot Goose:

No LiteLLM involved, so very happy.

In other news, I liked the procedure of doing a what was supposed to be a boring support call once - this was quite a handful of years ago. Fellow employee had issues with something something Windows, and we thought why not just call for support. Which we had never ever done.
So I did, after I elicited the number to call from a chat. No bots then, just humans.

The issue we had could not be solved by $person over the phone, then $issue was escalated. I took great care to be concise, friendly, and refer to the previosly shared information every time.

The 4th person (or nth, I forgot) picked up the phone and upon my first sentence angrily replied WHERE DID YOU GET THIS NUMBER FROM TELL ME THE NAME and made me say the name of the previous contact. (Sorry Chadenguna, you sure meant well.) I was unimpressed, except for the obvious fact that obviously the support dept did not know what they were doing, and complied. I may or may not have added insult to surprise by bothering the person with how important using the product was for us.

The issue was solved, as in "suddenly it works the next day", after a 1287 digit code was relayed to me by phone, but boy must MS version licensing have been a mess in their backoffice. Globally distributed system, my ass.

I guess this was the equivalent of the error message saying "this error message should never be shown", and a debug log somewhere that was found and quietly fixed later.