v4: an instance that takes no users of others still blocks instances its own users may not sign in to — with GERBEUR_FEDERATION_INCOMING=0, /manage hid its list of instances, though a blocked one still kept the instance's users from signing in there, and no admin could block another. The list now stays while federated sign-in goes either way: without incoming sign-ins it shows and adds only blocked instances, the trusted ones kept for when they're back, and says what blocking does there. Where both ways are on, its note now says that users here can't sign in to a blocked instance either.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

api/config.ts

@@ -237,10 +237,11 @@ export const FEDERATION_ALLOW_PRIVATE: boolean =
  *
  * - `incoming` (`GERBEUR_FEDERATION_INCOMING`): users of other instances sign
  *   in here. Off, the login and register pages offer no other instance,
- *   `/manage` no list of instances to trust or block,
- *   `federation-service.ts` refuses their sign-ins, and the accounts that came
- *   from one are signed out (`getSessionState`) until it is on again. Their
- *   homes' events are still applied, so that none is lost meanwhile.
+ *   `/manage` lists only the blocked ones, which this instance's users can't
+ *   sign in to (and none with `outgoing` off too), `federation-service.ts`
+ *   refuses their sign-ins, and the accounts that came from one are signed
+ *   out (`getSessionState`) until it is on again. Their homes' events are
+ *   still applied, so that none is lost meanwhile.
  * - `outgoing` (`GERBEUR_FEDERATION_OUTGOING`): this instance's users sign in
  *   to others. Off, `identity-provider-service.ts` lets no instance sign them
  *   in, and its metadata says so, which the others check before sending