pet.trezy.confessForgeries Documentation (EN)

main procedure

Looks for records of the caller's that an ingest guard refused, and if there are any, writes the note twice: once into the game's own repo through a linked repo, where the caller cannot reach it, and once into the caller's repo, where they can delete it. Called on sign-in. It changes nothing about what the account may do — the forged records were refused at ingest, so the ledger was never wrong — and it is safe to call on every visit: an unchanged list rewrites nothing.

Output

Encodingapplication/json

central string Optional

What happened to the game's copy — the one that matters. `written` is new or updated, `unchanged` means the note already said this, `unavailable` means the linked repo could not be reached and NOTHING was recorded durably.

Known values: written, unchanged, unavailable

error string Optional

Present instead of a result. `rejections-unavailable` means the store could not be read, which must NOT be treated as an innocent account — a caller that took it that way would overwrite a real note with an empty one.

Known values: rejections-unavailable

forgeries integer Required

How many refused records the caller has. Zero is the ordinary answer and the successful one.

message string Optional

No description available.

own string Optional

What happened to the caller's copy. `refused` is ordinary rather than alarming: they may simply not have granted the collection, and the durable copy does not depend on it.

Known values: written, unchanged, refused

Try It

Requests are sent directly from your browser. Some servers may block requests due to CORS.

Service Endpoint Base URL for XRPC calls (e.g., https://bsky.social)

View raw schema

{
  "type": "procedure",
  "output": {
    "schema": {
      "type": "object",
      "required": [
        "forgeries"
      ],
      "properties": {
        "own": {
          "type": "string",
          "description": "What happened to the caller's copy. `refused` is ordinary rather than alarming: they may simply not have granted the collection, and the durable copy does not depend on it.",
          "knownValues": [
            "written",
            "unchanged",
            "refused"
          ]
        },
        "error": {
          "type": "string",
          "description": "Present instead of a result. `rejections-unavailable` means the store could not be read, which must NOT be treated as an innocent account — a caller that took it that way would overwrite a real note with an empty one.",
          "knownValues": [
            "rejections-unavailable"
          ]
        },
        "central": {
          "type": "string",
          "description": "What happened to the game's copy — the one that matters. `written` is new or updated, `unchanged` means the note already said this, `unavailable` means the linked repo could not be reached and NOTHING was recorded durably.",
          "knownValues": [
            "written",
            "unchanged",
            "unavailable"
          ]
        },
        "message": {
          "type": "string"
        },
        "forgeries": {
          "type": "integer",
          "minimum": 0,
          "description": "How many refused records the caller has. Zero is the ordinary answer and the successful one."
        }
      }
    },
    "encoding": "application/json"
  },
  "description": "Looks for records of the caller's that an ingest guard refused, and if there are any, writes the note twice: once into the game's own repo through a linked repo, where the caller cannot reach it, and once into the caller's repo, where they can delete it. Called on sign-in. It changes nothing about what the account may do — the forged records were refused at ingest, so the ledger was never wrong — and it is safe to call on every visit: an unchanged list rewrites nothing."
}