Alright so internet community management thread pt11111, the bloody off-topic section.
Alright so as these gerbil fanciers get to know each other and start bonding over their love of specific tangentially-gerbil-related media, they start opening up about explicitly non-gerbil-related media, and then about non-gerbil topics in general.
This is fine, this is what happens when communities get to know each other. But are you still running a gerbil enthusiast website at this point?
It's gonna be a little nag in the back of your head, "Is this or is this not a gerbil website," and honestly the best thing to do with this may well be to just let it slide! So the site goes a bit off topic every now and then, that's alright - put a little extra effort in keeping individual threads more or less on the topic of the thread so that they're still useful for folks searching, but as long as there's a healthy vibe don't mess with it.
At least, until you get some newbie turning up and going "Uhhh, so is this a gerbil site or not?" or some grumpy veteran saying the same.
So now you're bollocksed, because you've observed it. Everyone will chime in and say it's one or the other and nobody will agree on what it is. Its wave function is collapsing!
So that's when you start your off-topic section. If you're a forum, this is easy, couple clicks and a think about where to draw the line on topics likely to lead to flamewars, you're done. If you're a Facebook group, this is where you splinter or implode, because you can't do subgroups on FB. Don't use FB for internet community building, it's incredibly rudimentary even compared to early-2000's PHPBB days, and not at all fit for purpose.
Anyway a thing to be aware of, especially if your forum is about things that people might have only a fleeting interest in, is that you may well get to the point where nobody's talking about gerbils anymore, they're just chatting.
I mean that's fine. Heck look at what happened with Twilight fan forums, the fans grew up and aged out very quickly but had made lots of friends and stuck around.
But now folks are showing their non-gerbil selves and talking about other stuff...
...and Politics and Religion might come up.
On Improbable Island we've gone back and forth on the "No politics or religion" rule, because we're a relatively old website. We've scrapped "no politics" for now because Gamergate redefined what is and is not "political" in a way that's relevant to our particular subculture until it was no longer possible to in good conscience keep the rule (people of colour in games = political, whites only = not political, guess we're political then).
Now this dynamic may or may not be applicable to your site, it really depends on a lot. You could make the argument (and you wouldn't have to try very hard) that having a "no politics" rule is in itself a political statement, as it only reinforces a status quo - one that's increasingly unfit for purpose, at least here in America. But that brings me to another point; if you allow political chat and you have an international audience, you'll end up with a LOT of American politics especially.
Also, out of the over 300 websites on the internet, over FIFTY of them are exclusively focused on politics, and have mods and admins experienced in dealing with moderating political subjects, where people will likely have a better experience than you can provide. You're a damn gerbil website, you're not set up for that. Remember, you're not trying to be the only site on the internet here.
So on Improbable Island we scrapped the "No politics" rule, talked about why we were scrapping it, but also made it clear that politics was not the primary focus of the site.
This has worked alright for us, but it's not something I'm comfortable saying EVERYONE should do in the same way that I'm comfortable saying everyone should have a Code of Conduct, everyone should allow avatars, everyone should have a clock and an FAQ, that kind of thing. You'll have to decide for yourself.
Also, it is in the Off Topic section that you find out things about your members you may have been more comfortable not knowing. Expect the first few months of Off Topic to be tumultuous.
Internet Ent Community Management Thread, pt999
I just updated my Code of Conduct (which is over eleven thousand words - it's PROBABLY not the biggest CoC on the internet, I'm sure others have longer, but it's certainly a lot for most people) to include a bit on using the chat channels as a support group.
We had a few people come in and just vomit their family drama and interpersonal problems aaaaalllll over the global, public chat channels. And as I type this I'm realising "vomit" is the word
Like, if someone's doing the rainbow yodel, they're clearly having a bad time and they could use some help, and it's a bonding moment to hold someone's hair while they're talking on the great white telephone. But if someone's laughing at the pavement and you're a stranger to them, you're gonna react to their technicolour yawn with more of a yearning for it to be over and cleaned up quickly.
The context matters, here.
We can extend this awful metaphor even further, because we all know the experience that a public call to Ralph can often set off others, and that's exactly what's been happening - this behaviour gets normalized VERY quickly. It tends to go unchallenged because nobody wants to be the one to say "Dude, I don't know you, I don't know your godawful housemates, dumping your problems on strangers who didn't ask to hear them is a crummy thing to do, take it to DM's."
That's YOUR job! 😬
Some folks, upon being told "Hey, talk about that kind of thing with your mates, not with strangers," might respond with "But I don't have any mates 😔"
Gee I bloody wonder why
Internet Fogey Community Management part "my knees hurt," SLURPING UP THE DRAMA WITH A STRAW
A subthread to this thread had me asking a reader to write down a chronicle of the internet drama leading up to a fracture of a long-established forum, so that I could rubberneck at my leisure.
At an earlier point in my life this would feel like asking someone to bottle their farts so I could enjoy them later, but these days I've leaned into it and it's more like watching table saw accident videos.
It's important as an admin for you to spend some time reading ancient accounts of site implosion, fractures and general Internet Drama. In doing so you can get a feel for the shape of an "incident" before it forms, and try to decapitate it before it gains power. You'll recognise notes in clashes that happened before, you'll notice that the same things keep happening, and you'll realise that it's never actually about gerbils but about personalities.
These days I read about Ravelry's catastrophic site redesign and I go "Haha yeah I know ALLLLL these people" and I can pretty readily predict exactly what's gonna happen. That comes not from just running a big site for years and years but from rubbing my hands together while poring through the agonizing details of other site implosions.
Reading drama-summary posts and comparing them with actual posts made on the site is often instructive!
The summary posts are often useless on their own because they give more of a general "feel" of what went down than actual details of who posted what when - it's normal to read a drama summary post and then go check out the referenced posts and go "What, THIS is what they're talking about? Gerbil food?"
well of course it's not about the gerbil food dummy, it's about a narcissist using the subject of gerbil food as a crowbar to split a community into pro- or anti-sunflower-seed, it's about an absent admin who won't ban the narcissist because then the pro-sunflower-seed side will be angry with them, it's about well-meaning people being played like fiddles or talking past each other or caricaturing each other, it's about strawmen and polarization and the rich controlling the working class wait um
Anyway the drama-summary posts give an exaggerated lens to the drama, either magnifying the original issue if they were written by someone involved or downplaying the fulcrum and concentrating on the personalities involved. Either way they don't tell the full story, but neither do the posts in the actual community (there's always behind-the-scenes stuff, bitches eating crackers (search it), and deleted posts). So the summary threads are really only an appetizer.
Clarification, I compared slurping internet drama to watching table saw accident videos, earlier - for context, I got a table saw recently, so I'm watching the videos as instruction on how accidents happen so that I can Not Do That. Watching people horribly maim themselves on table saws while NOT owning a table saw would be a pretty weird and maybe unhealthy thing to do (but people do it anyway because people are weird). So yeah, I dramaslurp for the same reason.
(it's MEDICINAL dramaslurping. I can stop any time I want.)
Anyway yeah, pop on encyclopedia dramatica, poke around fandom drama LJ's, get a good snootful of petty website drama. This will make you a better admin. It might make you a worse person, but you'll be a better admin.
Online community management thread pt "numbers are meaningless"
Remember when I said early on that the user interface goes a long way in setting the initial tone of the site?
Go read this massive thread by @zensaiyuki about that. https://mastodon.social/@zensaiyuki/102683452946911475
Internet Community Management Thread continued: earlier in the thread I talked about tactics abusers use to abuse and how it's important to be aware of those tactics and to make your site members aware of them too, in order to build community immunity. Here's a Fediverse deep dive into DARVO courtesy of @hafnia:
https://wandering.shop/@hafnia/104997378933311199

Content warning: that thread about DARVO
Wandering ShopThe current Big Thing I'm working on in Improbable Island is an interface overhaul.
These are FRAUGHT. Bigger sites than mine or yours have collapsed because of getting new interfaces - either the new UI was too different to the old UI that people loved, or the new UI just plain sucked even outside of comparison to the old one.
Ravelry's ugly and migraine-inducing New Look is a famous recent example.
Ravelry's redesign is a series of mistakes which compounded one atop the other until things got really, really bad. The mistake train stretches even past the interface redesign and into their handling of the pushback of the redesign, and it's still chugging along.
This compounding of mistakes is actually pretty common. It's easy for us to see a series of bad decisions and go "Why didn't they correct things at X point?" but c'mon, we've all been there. A mistake early on leads to more.
Ravelry's first mistake was in doing an interface redesign in the first place.
Ideally you should never do a complete, ground-up redesign of an existing, well-loved site. There are reasons why people love the site!
Folks tend to get into complete redesigns because of reasons that don't actually matter.
Example 1 (Ravelry): You're doing a brand overhaul, changing your logo, and you want the site to match.
I promise you, you are the only person in the world who cares about brand cohesion.
Example 2 (metafilter & others): You're doing a new interface because google says you have to.
Again, your users don't care what google thinks. Why would they? Your search rank dropping is your problem, not theirs, and thrusting an unnecessary interface change on folks is just an attempt to take google's problem (which google made your problem) and make it into their problem.
And that's problematic.
(while we're on the subject, I just want to emphasize how much of a fool's errand it is to try to get into the top page of google results. You'll spend months and months doing it, and then someone in some sweatshop will rewrite your article in a weird stilted keyword-stuffed voice, add a table of contents in a blue box and big headings marked INTRODUCTION and CONCLUSION like they're back in high school, and knock you off the top with a worse article, because search engines generally suck)
Example 3: Your codebase is old and creaky and your site is still laid out in tables etc, and you just tried adding some new feature and it's a big pain in the bum because of all the creakiness, so you decided to recode it all and heck, why not give it a new coat of paint, since you're in there already.
Again, your users don't care! Who gives a heck if your site uses tables! That just means it'll probably still work in twenty years!
The only people who care about your HTML or will ever even look at it are other web designers, and as I'm sure you're aware by now, nobody cares what web designers think.
(except other web designers of course)
So these are all bad reasons to do a big ground-up site redesign. In general there aren't good reasons!
Example 4: you're redesigning your layout to make the header smaller, or take stuff from the top of the page and put it on the side instead, because computer monitors keep getting shorter.
This is actually legit. At least until we get the whole screen situation under control and start making computer monitors again instead of just small tellies, we're gonna have to deal with lousy displays, and putting stuff on the side instead of the top can help in that regard.
(but don't be tempted to put in a javascripty three-line menu thing. If something that used to take one click now takes two, that's a bad redesign)
Anyway, Improbable Island's retheme falls into category 3, rewriting because the old one was a big pain in the bum.
Because this ain't my first rodeo, the very first thing I did was to recreate the old theme, as near as "to the pixel" as I could, in modern HTML/CSS.
The second thing, because Ravelry is fresh in my mind, was to LOUDLY and PUBLICLY and ENTHUSIASTICALLY and REPEATEDLY open the beta testing period to *every community member.*
Seriously, whenever I'm in chat I'm asking folks how they like the new theme, getting feedback, and converting people over to the new theme.
Ravelry only opened their beta theme test to a handful of people. Don't be like ravelry.
Next, I made some very small improvements and ran them past the people using them. Most were small quality-of-life improvements, adding spacing on specific elements to avoid finger mistakes on mobile, that kind of thing.
Then, I made one big dramatic change, but tied it to a new feature (backgrounds that change depending on what you're doing in the game) that would be impossible in the old interface.
And people love it and are excited about it.
You *can* do an interface change humanely!
To do a successful interface overhaul, you have to be intimately familiar with the reasons why people love your site, and the things they love your site in spite of. Fix the second and leave the first well alone.
The things in the middle, the things people are indifferent about, can retroactively become people's favourite things if you mess with things too much.
Make your new skin a carbon copy of the old one, and slowly file off the rough bits. Do this live! Don't make a bunch of big changes on your test server then upload them to make a big change all at once, that freaks people out. Let them see the improvements happen as you make them and talk about them.
You want your members to feel that you're being slow and careful and considerate. To have them feel that way, first you have to actually BE slow and careful and considerate. Second you have to SHOW them that you're being slow and careful and considerate, by making changes gradually - testing locally and then uploading and asking for feedback on each one.
Let users be a part of the process and make it clear that this redesign is for THEM more than it is for you.
Barometers to see whether it's going well:
* Someone says "I just swapped back to the old skin and it looked WEIRD and BAD"
* People talk about interface *improvements* rather than interface *changes*
* People talk each other into trying the new skin
* People are curious about upcoming changes
* People ask you to fix other little rough edges while you're in there