💾 Archived View for the.teabag.ninja › gemlog › 20221206-why-cant-people-read captured on 2024-05-26 at 14:47:58. Gemini links have been rewritten to link to archived content

View Raw

More Information

⬅️ Previous capture (2023-09-08)

-=-=-=-=-=-=-

Why the fuck can't people read

2022-12-06

A couple of things bring me to this rant.

The first, is on a Fediverse instance I help with.

We have Rules (as you do). These rules are front and centre as soon as you click the button to sign up. They take the entire page, and you have to agree to them before you can sign up. Ther are only a dozen or so, and can be skimmed in half a minute. No big deal.

Well, it seems that websites and software and freaking everything with a ToS you have to agree to, has conditioned everyone to blindly just click on through - except we put something in the rules you need to write in your application!

So in the morning we get a few sign ups that go straight through, and as they day passes we get less effort on the signups and rejections increase.

So... yeah.

The second, is the Akkoma Guide.

I posted in the Akkoma forum trying to help someone who was struggling. I am no expert, but hey I know my document works.

So then this person replies saying it still doesn't work. "What ever do you mean" I think...

Turns out, THEY ADDED STEPS. Because... of course they did.

They had been struggling, so I asked if my guide worked for them - and it did not. They posted the result where they enter the instance details, and said YES to rum indices and (nowhere in my guide does it say to install them) so of course it didn't work. The error it spat out even told them what to do to fix it. I pointed out my guide had nothing on rum indices, so why would they change from the default No... " oh it seemed like a good idea".

You have got to be shitting me.

I then perhaps foolishly said "well I don't really know what I'm doing, but my guide worked" but I was trying to be nice (and obviously I still had more of a clue than them) and this is the response I got.

I understand where you’re coming from Snott. As someone who earns his living writing technical documentation, I’ll humbly suggest to put it all down. Perhaps as a running note. We have this motto: “If it’s not documented, it does not exist”. So might as well dump all the messages and the troubleshooting steps, if any. As in, ‘what to do when a message is displayed? Ignore or do something?

So this person writes technical documentation for a job.

And can't follow instructions.

What the actual fuck.