pet.trezy.getForgeries
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.
Details · query
| Kind | query |
|---|---|
| Authority | trezy.pet |
| Indexed |
Query
query · GETParameters
query stringdid
string · didWhose 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
application/jsonerror
stringPresent 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
Empty for the overwhelming majority of accounts, and an empty array is the successful answer rather than an absence.
message
stringWhose report this is — echoed so a caller that omitted `did` learns which account answered.
#forgery
objectSimilar lexicons
semantic matchLexicons whose schemas describe something close to this one. Check them before publishing a new one that overlaps.
-
pet.trezy.shameOnYou
recordA note that somebody was caught forging records. Written in TWO places for two different reasons: one copy in the game's own repo, keyed by the offender's DID, which they cannot delete and which is the durable account; and one copy in the offender's repo, which they can delete the moment they notice — and noticing is the point of that one. Neither is a punishment. Nothing in the game reads these records or behaves differently because one exists; the forged records were already refused at ingest,
-
pet.trezy.confessForgeries
procedureLooks 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.