eudaemon

Sitenotice is up. Thank you.

RE:communications I'd like to see more of.

1. The shutdown notice would have been one; important news, instead of only posting on Twitter and other social media. After a few tweets like "30,000 wikis!" (not all active, ahem), this just turns into noise.

2. Decisions made by the board. A summary will do.

3. Current or ongoing technical issues. Or do we have to go through the whole of outstanding Phabricator tasks?

This communication can be accomplished by subscription. I would then like to see a notification/bell made with a capsule of what's being shared and its location within the Miraheze maze.

On other business, check out Lithuania as a possible location. It's a very tech-oriented country, and I've worked on a MediaWiki-based wiki based there. I don't know the specific server farm or company.

It was your bog-standard disk crash as I understand it. Pros were (eventually) brought in for data recovery. But I also understand the backup for the wikis on that server (like mine, one of the dead ones) was on the same server, which doesn't sound like a very good plan. If a backup was stored elsewhere, the dead wikis would have been restored in a very short time. Lesson learned, I hope.

I got most all of my data restored, but there was a temporary problem of deleting and replacing files that the server programming thought still existed. That was fixed quickly.

Particularly at this point, I'd like to see better communication between the board and wiki members/crats/admins. No news has been the rule with Miraheze except for planned service outages and donation requests. The way I found out about the closure announcement was from a Tweet that rides in with a 503 error message. I know it's early days, but a message about proposing to continue Miraheze would be useful on that platform, yes?