pet.trezy.getForgeries Documentation (EN)

main query

Every record of this account's that an ingest guard refused, one entry each, with the reason written out. Reads `trezy_pet_rejections`, which the guards fill as forged records arrive on the firehose — so this is a report of what was already stopped, not a check performed now. Nothing here changes what the account may do: the refusal happened at ingest and the ledger never saw the record.

Parameters

did string did Optional

Whose forgeries to report. Defaults to the caller. ⚠ ANY DID MAY BE ASKED ABOUT, DELIBERATELY. The whole purpose of this data is to be published — `pet.trezy.shameOnYou` puts it in a public repo moments later — so treating it as a secret in transit while broadcasting it afterwards would be theatre. It also lets the server that writes the public record verify the claim for itself rather than believing a client that says 'shame this DID'.

Output

Encodingapplication/json

error string Optional

Present instead of a report when there is none to give. `rejections-unavailable` means the store could not be read — which must NOT be shown as 'no forgeries', because an unreadable table would otherwise clear somebody's record by accident.

Known values: rejections-unavailable

forgeries array Required

Empty for the overwhelming majority of accounts, and an empty array is the successful answer rather than an absence.

message string Optional

No description available.

subject stringdid Required

Whose report this is — echoed so a caller that omitted `did` learns which account answered.

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://api.bsky.social)

Parameters

did Whose forgeries to report. Defaults to the caller. ⚠ ANY DID MAY BE ASKED ABOUT, DELIBERATELY. The whole purpose of this data is to be published — `pet.trezy.shameOnYou` puts it in a public repo moments later — so treating it as a secret in transit while broadcasting it afterwards would be theatre. It also lets the server that writes the public record verify the claim for itself rather than believing a client that says 'shame this DID'.

View raw schema

{
  "type": "query",
  "output": {
    "schema": {
      "type": "object",
      "required": [
        "subject",
        "forgeries"
      ],
      "properties": {
        "error": {
          "type": "string",
          "description": "Present instead of a report when there is none to give. `rejections-unavailable` means the store could not be read — which must NOT be shown as 'no forgeries', because an unreadable table would otherwise clear somebody's record by accident.",
          "knownValues": [
            "rejections-unavailable"
          ]
        },
        "message": {
          "type": "string"
        },
        "subject": {
          "type": "string",
          "format": "did",
          "description": "Whose report this is — echoed so a caller that omitted `did` learns which account answered."
        },
        "forgeries": {
          "type": "array",
          "items": {
            "ref": "#forgery",
            "type": "ref"
          },
          "description": "Empty for the overwhelming majority of accounts, and an empty array is the successful answer rather than an absence."
        }
      }
    },
    "encoding": "application/json"
  },
  "parameters": {
    "type": "params",
    "properties": {
      "did": {
        "type": "string",
        "format": "did",
        "description": "Whose forgeries to report. Defaults to the caller. ⚠ ANY DID MAY BE ASKED ABOUT, DELIBERATELY. The whole purpose of this data is to be published — `pet.trezy.shameOnYou` puts it in a public repo moments later — so treating it as a secret in transit while broadcasting it afterwards would be theatre. It also lets the server that writes the public record verify the claim for itself rather than believing a client that says 'shame this DID'."
      }
    }
  },
  "description": "Every record of this account's that an ingest guard refused, one entry each, with the reason written out. Reads `trezy_pet_rejections`, which the guards fill as forged records arrive on the firehose — so this is a report of what was already stopped, not a check performed now. Nothing here changes what the account may do: the refusal happened at ingest and the ledger never saw the record."
}

forgery object

No description available.

Properties

cause string Required

The reason as a sentence, composed here so every copy of it agrees and none of them is written by the accused's own browser.

noticedAt string datetime Required

An RFC 3339 formatted timestamp.

reason string Required

No description available.

maxLength: 64 bytes

uri string at-uri Required

An AT Protocol URI (e.g., at://did:plc:xyz/app.bsky.feed.post/abc).

View raw schema

{
  "type": "object",
  "required": [
    "cause",
    "uri",
    "reason",
    "noticedAt"
  ],
  "properties": {
    "uri": {
      "type": "string",
      "format": "at-uri"
    },
    "cause": {
      "type": "string",
      "description": "The reason as a sentence, composed here so every copy of it agrees and none of them is written by the accused's own browser."
    },
    "reason": {
      "type": "string",
      "maxLength": 64
    },
    "noticedAt": {
      "type": "string",
      "format": "datetime"
    }
  }
}