Alright here's what it looks like creating a domain limit in the settings panel.
It's very similar to the process of creating a domain allow or block, you just enter the domain you wanna limit, pick the ways in which you wanna limit it, add a comment etc if you want, and submit it.
The options for limits are (currently, though subject to some change):
content warning:
- if you want, you can automatically prepend a content warning to posts from the limited domain
media from the limited domain:
- no limit (default)
- always mark as sensitive
- don't download or process at all, just link to it instead (kinda how we do already for media that GtS couldn't download for whatever reason)
follows from the limited domain targeting an account on this domain:
- no limit (default)
- always require manual approval, even if the follow targets an unlocked account
- automatically reject unless the follow (request) is a "follow back", ie., the target account already follows or follow requests the account on the limited domain
- automatically reject all
statuses from the limited domain created by non-followed accounts:
- no limit (default)
- apply a "warn" filter to all statuses
- apply a "hide" filter to all statuses
non-followed accounts on the limited domain:
- no limit (default)
- mute <-- this is equivalent to Mastodon's "silence" functionality iirc
the statuses and accounts policies are designed in such a way that if you follow an account on a limited domain with one or more of these limits applied, you more or less aren't affected cuz you'll be able to see stuff that the account posts as normal; the fact that you follow them is taken as evidence that you wanna see their posts (I mean... why else would you follow them). However if you don't follow them you can make it so your instance functionally ignores their existence, from your perspective at least
the other policies allow you to follow accounts on instances that, for example, post lots of tits, ass, and genitalia (hurray!) but don't use content warnings or mark stuff as sensitive (boo!); you can just have your instance apply content warnings and mark stuff as sensitive for you
this shooooooould more or less allow you to federate with instances that are a bit shit overall, but which contain one or two cool people, without getting a massive headache and wanting to throw your laptop into the hole
docs to follow when the feature is actually on main and everything is working