The issue with using Mastodon for an offsite status page is that it's hard to find an individual instance with a strong record of uptime -- the purpose of using a microblogging site as an offsite status page is not necessarily to reach the users of the service itself, it's because it's incredibly quick and easy to update during an outage, and the easier you make it to update during an outage, the more likely you are to actually do it. So for an offsite status page you want

1. a service with a really strong uptime record
2. that has memorable and easy to reach URLs
3. that allows outside people to view posts without an account
4. that shows the most recent posts first
5. and doesn't hide posts or require a few clicks to see them
6. and is as easy as possible for the person who's working on fixing the busted shit to update really really fast

Mastodon instances fail 1 and 2, Xwitter now fails 3 and 4, Facebook fails 4, 5, and 6, etc, etc, etc. Up until recentlyish, Bluesky failed 3 (and is still a little iffy on 2, but we did our best) but they changed that, and I'm satisfied enough with their uptime record now that it crossed my "okay, make the switch" threshold.

There is a bridge service that bridges posts from Bluesky to Mastodon if your instance admin hasn't blocked it! But this isn't a thing where we're going to be posting regularly or anything: it's just a location for "yeah, we know shit's broken, we're working on it" announcements if we or you can't reach dw_maintenance to see them.