@jofazepa I'll get around to doing an upgrade at some point. It's not hard, but does take some time, which I'm very short on.

FYI, all Gab domains I could find are blocked. If I find them more they will be blocked.

If you don't know what Gab is, consider yourself lucky.

Sorry for the downtime folks! I'm on leave and busy with family stuff. @blinks stepped up and solved it. And since he's amazing, he wrote a post-mortem: gist.github.com/blinks/dabac9f

Bad news: I was tagged in to a thread with some of my least favorite people to talk D&D/DW.

Good news: Because people were wrong on the internet I migrated some 8 year old posts on D&D and AW-style Principles and now you get to read them.


Supporting dice.camp: a few people have asked about how to support dice.camp. The short answer is you don't have to. But if you want to help us meet our costs (about $20/month) we now accept contributions at ko-fi.com/dicecamp.

dice.camp upgrades! The "A look inside..." preview on the non-logged-in home page will now show just (externally visible) posts from this instance, not the known fediverse, which should give potential joiners a better idea what's up here.

dice.camp upgrades! I've set a hero image so the initial sign in page and link preview when sharing the url will both look a little more custom and a little less default.

With G+ going away, I'm going to invest a little more time here to provide something a little similar (hopefully). To that end, expect to see a little more activity on a few fronts.

Folks should now reliable get notification emails, registration emails, all that. Which makes dice.camp self-serve!

Okay, so I am proud to say I think I have finally solved our email problems once and for all.

Hey folks, sorry for the momentary downtime. As part of looking in to our issues sending email I upgraded Mastodon on a whim. We're not back and on the latest and greatest.

dice.camp now sitting at around 800 users, which is a thing I never expected.

FYI, did a quick update this morning for an urgent security patch. Everything should be good now.

Best guess on problem: something went wrong in the database, which led to Mastodon being stuck in its regular cleanup task using the entire CPU.

The best way to get the db out of this state was the migration that happens as part of upgrades.

These are all wild guesses, nothing concrete enough to track as a bug on the Mastodon codebase.

And we're back!

Last night around 1 AM PST something maxed the CPU on our tiny virtual server. It was pegged so hard the machine was unresponsive. I restarted it, and it didn't come back up cleanly. Unable to get it to settle down, I went back to our last snapshot, which happened just before the machine went wild. (Maybe related to why it went wild?)

I was unable to stand that up either, and ended up upgrading that snapshot to the latest Mastodon code, which somehow unstuck it.

@not_another_mike notification emails? Registration emails are sending, like always, though a mail service which can in many cases get filtered. But they are still sending.

Show more

A Mastodon instance for tabletop gamers.