Reports which optional parts of the service this instance exposes.

Whether this instance writes down who fetches a share.

false by default. When true, every retrieval records the visitor's address and browser string, and the visitor is the person it happens to, so a client should say so on the page where the share is collected. Nothing else will.

Whether a new account password is checked against known breaches, so a form can look it up while typing; see GET /auth/pwned/{prefix}.

Shortest account password this instance accepts, so a client can say so before the round trip, not after it.

Named for what it governs, because there are two minimums and they differ. See share_password_min_length.

Whether an account password needs a digit.

Whether an account password needs both an uppercase and a lowercase letter. Character classes are defined on PasswordPolicy; a client that classifies differently will accept passwords the server refuses.

Whether an account password needs a symbol. A space is not one.

Whether accounts exist at all on this instance.

false means no registration, no login and no session: the shape for a personal instance behind a VPN.

Whether the administrative endpoints are mounted.

The administration front-end is a separate deployment, so this says only that the API half is present.

Whether a caller without a session may upload.

Independent of accounts: an instance can have accounts and accept anonymous uploads, the default.

Number of characters in a retrieval code on this instance (share.code_length), so the page that collects one can draw the right number of boxes. Codes already issued keep the length they had, so this is what new shares get, not a promise about every code in existence.

How long a share lasts when the uploader does not choose, in hours.

The upload form needs this to say what "leave it alone" means. null when this instance lets shares live forever by default.

Whether an upload may be end-to-end encrypted. See docs/encryption.md.

The longest lifetime an uploader may ask for, in hours.

null when there is no ceiling. A form that knows this can bound its own control instead of offering a date the server will refuse.

Largest single file this caller may send, in bytes.

The narrowest of their own limit, their role's and server.max_body_bytes. So an operator who raised the instance figure for themselves does not have it reported to every stranger, and a client is never shown a number bigger than what it may send.

Whether this instance can send a password reset link.

false when no relay is configured, the default. A client that drew the "forgot password" link regardless would send people to an endpoint answering 404, so this is the difference between a missing feature and a broken one.

Who may create an account. Meaningless when accounts is false.

Whether registering sends a confirmation link instead of creating the account outright.

true means POST /auth/register answers 202 and nothing exists until the address is confirmed, so a client must show "check your inbox" instead of treating the response as a sign-in. false means it answers 201 with a session, as an instance sending no mail does.

Shortest password an uploader may put on a share.

Lower than the account minimum by design. A share password is a second factor on a link that is already unguessable, and it gets read out over the phone. A form that validated share passwords against the account rule would refuse the four-digit code the server would have accepted.

Whether this caller may run a speed test.

Per caller, not per instance: an instance can offer the test to accounts but not visitors, and a visitor should see the same as on an instance without the test.

How much room the caller has left, in bytes.

Whichever ceiling refuses them first: their own quota, then their role's. Callers who may read instance statistics also see the instance ceiling. null if none applies.

storage.max_total_bytes is not in everybody's answer because on a public instance it is the operator's capacity planning, and telling every anonymous uploader how close the disk is to full invites them to finish it off. Their own quota is theirs to know, and a client holding it can say so before they pick a file.

Version of the running server, for a client that wants to warn about a mismatch with the contract it was generated from.