Of Mastodon, Culture Clashes, and BBSs

TL;DR: Avoiding Mastodon because you’ve heard it’s problematic makes as much sense as avoiding the internet because you’ve heard it’s problematic.

So.

Back in the antediluvian times before the Internet existed — you know, when great beasts like dinosaurs and, um…mastodons…roamed the earth — there were these things called Bulletin Board Systems, or BBSs.

Each BBS was a single computer sitting in someone’s house, connected to a telephone line (the physical kind that came out of the wall). BBS users could use a modem (generally a little box with blinky lights that screamed at you when you started using it, but the really neat but slow early ones you’d actually place an telephone handset into) to place a telephone call from their computer to the BBS computer to see who had posted messages since the last time they called in, respond to those messages if they wanted, and upload or download tiny, low-resolution, 256-color .bmp images, often of impolite subject matter.

The really fancy BBS systems could connect to two or three phone lines at a single time, so that more than one user could log in at the same time. This would let them type back and forth at each other, much like a modern chat session, only they’d have to actually use real words, because this was also before emoji were invented.

Each BBS tended to have its own particular culture and rules. Some BBSs were regional for an area; others might have a Star Trek theme, or a Star Wars theme, or a Dr. Who theme. I think that was it, because those were the only approved geek interests at the time. People with particular interests would join BBSs that supported those interests, so they could have conversations with other people that shared those interests.

Eventually, BBS systems gained the ability to dial into each other and exchange messages. Suddenly conversations could involve not just the users on an individual BBS, but also users on other BBSs. Once a day or so, one BBS would call another one, send a bunch of replies to discussions that had been posted in the past day over, and receive a bunch of replies to discussions.

Of course, even when one Star Trek BBS was talking to another Star Trek BBS, they might not have exactly the same rules. Subjects that were fine one one server might be anathema on the other. Maybe a user who had gotten into a fight with someone on one server had started using another one, but now those two servers were talking to each other. Basically, people are people, and as every good Depecehe Mode listener knows, that doesn’t always work out.

But still, people generally like to meet and talk to other people about things they enjoy (not to mention exchange tiny, low-resolution, 256-color .bmp images of impolite subject matter), and so these differences were dealt with, and different servers found ways to get along. Or, if there were simply too many differences to overcome, the servers would simply stop calling each other to exchange messages.

Basically, we all either figured out how to get along, or if there was a known problem server, we just stopped dealing with it.

But we didn’t say that, “Oh, I heard BBSs were a problem, so I don’t do that.”

Well, okay, sure, I’m sure there were people who had that attitude. But the rest of us knew that you didn’t have to throw the BBS out with the bathwater (there’s a risk of electrical shock when doing that anyway) — all you had to do was ignore the BBS that was the problem, not ignore BBSs altogether.

Fast forward a few decades.

Now every computer talks to every other computer. Some of those computers host discussions from a number of different people. Some of those groups of people are perfectly pleasant, reasonable people, whose only concerns are ensuring that everyone they know has a lifetime supply of puppies, kittens, and rainbows. Some of those groups of people are…otherwise interested.

They all exist on the same internet, but they’re on different systems, using different software, much of which doesn’t easily talk to the other kinds of systems and software out there. So when you run across a part of the internet that has all the appeal of free diving into depths of the New York City sewer system, the easiest solution is to simply not explore that part of the internet. (And hopefully, you escape before attracting their notice, so they don’t follow you wherever you go.)

So we (most of us, at least) don’t avoid the entire internet because we know that there are some parts of it that are not places you’d want to wander through late ate night (or, sometimes, even in the broad light of day).

One of Twitter’s major problems is that it is a monolithic system: If you’re on Twitter, you’re in the same system as every other Twitter user. And because Twitter had dodgy and poorly enforced protocols and methods for protecting its users, there was no good way to say, “I don’t want to deal with this unpleasant group of Twitter users”. Everyone’s in the same room at the same party, and there’s no real way to escape short of leaving the party entirely, even if that means having to abandon all the partygoers that you like to get away from the partygoers with the funny little mustaches who are being jerks.

Mastodon, however, isn’t monolithic. It’s not a single system. This is where you start hearing the words “decentralized” and “federated” and your eyes glaze over, but all that means is, just like the BBSs of ye olden days, it’s a bunch of individual servers that can to talk to each other. The biggest difference is that where in the BBS days, BBS owners had to find each other and set up the connections intentionally (opt-in), Mastodon’s default is for servers to talk to each other unless they choose not to (opt-out).

Some servers are puppies and kittens and rainbows, some aren’t. But when the owner of the Mastodon server puppieskittensrainbows.social realizes that the users from newyorkcitysewer.social keep harassing people, causing problems, and being generally unpleasant, they can just decide not to talk to that server anymore. Poof! Problem solved, no more sewer rats skittering around biting people.

So, is Mastodon a problem? No more than BBSs are a problem, or the Internet is a problem. Individual Mastodon instances may be, but they can be dealt with.

And, of course, nobody can spend $44 billion to run Mastodon into the ground in two weeks.

If Twitter Falls Over…

A friend on Facebook asked:

Leave Twitter or stay*?
If you’re leaving, where are you going?

My response:

For myself, I’ll likely keep my account active (deleting an account doesn’t remove it from being followed, and means that username is up for grabs, which means a bad actor/spammer could grab it and start showing up in the feeds of anyone who was still following that username), but I may start scaling back my usage (even more than I already have). There are still a lot of people on there that I value following, but if the ratio starts to change, so it goes.

My personal preference (at least in an ideal world) is for my own personal website. I own it, I can put what I want on it, and I’ve had a blog running there for more than 20 years now. How frequently I post to it varies depending on how much I’m sucked into Facebook or Twitter at any given time, but I’ve never let it totally die off, and maybe this will (once again) be impetus to start babbling there again.

Of course, the down side to personal blogs is that for “most people”, they’re not as visible — you have to either go to them, or have some form of RSS newsreader set up, which isn’t difficult, but if you don’t know about that as an option, it doesn’t do any good — because they’re not being algorithmically pushed into people’s faces, so you get fewer readers. And without “like” buttons or similar functionality (which I’ve not bothered to figure out how to do on mine), if the readers you do have don’t comment, then you don’t have the gratification of feedback. I’m well aware that this is one of the things that keeps sucking me back to Facebook: I can post the same thing here and on my blog, and I have no idea if anyone ever sees my blog, but here I’ll get reactions and comments.

I also have accounts on both Mastodon and Cohost, and will every so often check back in to see what’s going on there. As always, if more people I know use those more often, I’m more likely to participate more often.

📚 The Howling Man by Charles Beaumont

48/2022 – ⭐️⭐️⭐️

Overall not a bad collection of short stories, and I can see why the book got the high-profile list of authors to do introductions and provide their memories of Beaumont. However, many of the stories haven’t aged well; they may have been “dated but still worthwhile” when the collection was published in the late ’80s, but forty years further on, they’re just “dated and cringeworthy”. Don’t regret reading it, but definitely won’t be keeping it in my collection, either.

Michael holding The Howling Man

🎥 Thor: Love and Thunder

Thor: Love and Thunder (2022): ⭐️⭐️: It was…okay? I mean, it more or less held my interest. There were amusing moments, and I wouldn’t really say I was bored through much of it. But the tone was just weird. It felt less like it was done by the same director as Ragnarok, and more like it was done by his understudy who almost but not quite understood what made Ragnarok work so well.