Oh, looks like I found a bug in my whitelist code!!!
Awoo.space is a Mastodon instance where members can rely on a team of moderators to help resolve conflict, and limits federation with other instances using a specific access list to minimize abuse.
While mature content is allowed here, we strongly believe in being able to choose to engage with content on your own terms, so please make sure to put mature and potentially sensitive content behind the CW feature with enough description that people know what it's about.
Before signing up, please read our community guidelines. While it's a very broad swath of topics it covers, please do your best! We believe that as long as you're putting forth genuine effort to limit harm you might cause – even if you haven't read the document – you'll be okay!
This bug has been fixed, confirmed, and deployed already.
If anyone's interested you can see it in the following commit-
https://github.com/vahnj/mastodon/commit/6b7ee3076860236a258f7bd7a50b5b822aaf803d
Somehow in rebasing changes, the placement of where we call a single new AllowDomainService (a service to abstract between blacklist/whitelist) got put after where we check whether we allow domains or not.