pet.trezy.setFeatureConsent

Say yes or no to the caller's pets being Pet of the Week. Yes writes pet.trezy.featureConsent/self into the caller's repo; no deletes it. Idempotent both ways.

Repository @trezy.pet did:plc:ollch4g7tes2reb5eceiwuol namespace authority
Details · procedure
Kindprocedure
Authoritytrezy.pet
Indexed

Procedure

procedure · POST

Input

application/json

consenting

requiredboolean

Output

application/json

consenting

boolean

The answer now on record. Present only on success.

error

string
  • knownValues: not-authenticated | invalid-input | save-failed

message

string

Similar lexicons

semantic match

Lexicons whose schemas describe something close to this one. Check them before publishing a new one that overlaps.

  • This keeper is happy for their pets to be Pet of the Week on Bluesky, with an @mention. The record existing is the yes; deleting it is the no. ⚠ PUBLIC ON PURPOSE, unlike pet.trezy.preferences: the weekly pick has to read it and cannot read a permissioned space, and agreeing to be posted about in public says nothing private. Not signed: forging your own consent is consenting, and a copy in anybody else's repo is never read.

  • The featured keeper's answer for one week: a note to quote in the post (text, may be empty) or decline: true for 'not this time'. Writes pet.trezy.featureReply/<week> into the caller's repo. Refuses unless the caller is that week's keeper and the post has not gone out yet.