app.matakite.flag

A public report that another app.matakite.* record violates community norms — spam, unresolvable criteria, private-individual target, harassment, duplicate, etc. Flags are signed records in the flagger's own PDS: public, timestamped, and attached to the flagger's DID. Frivolous flagging feeds the flagger's own quality record; the design mirrors app.matakite.dispute — the deterrent is reputational, not economic. Flags are inputs to appview indexing, display policy, and labelers; they are not censorship, and any appview may weight them differently.

Repository @matakite.app did:plc:vhycfha6sjn44hxepb5bmjax namespace authority
Details · record, key tid
Kindrecord
Record keytid
Authoritymatakite.app
Indexed

Record

record · key tid

Properties

createdAt

requiredstring · datetime

note

string

Optional reasoning, public. Required by convention when reason is 'other' — appviews may downweight noteless 'other' flags.

  • maxLength: 3000
  • maxGraphemes: 300

reason

requiredstring

Category of concern. 'unresolvable' = criteria and sources cannot yield a definitive outcome (Metaculus-style annulment candidate). 'duplicate' = substantively the same question already exists. 'privateIndividual' = record targets a non-public person. 'harassment' = record targets a person maliciously. 'spam' = low-quality or automated volume. 'other' = anything else; a note is expected by appview convention (the schema cannot require it conditionally).

  • knownValues: unresolvable | duplicate | privateIndividual | harassment | spam | other

subject

requiredref

The flagged record (uri + cid). Valid on any app.matakite.* record — questions, forecasts, resolutions, disputes. The cid pins the exact version being flagged; a later edit to the target creates a new cid and does not inherit flags.

Similar lexicons

semantic match

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

  • A report of inappropriate content on a beacon

  • A public counter-attestation against a resolution. With no bonds available (no money), the deterrent is reputational: disputes are signed records attached to the disputer's DID, so frivolous disputes cost the disputer. Disputes feed resolver track records ('N resolutions, M disputed, K upheld') that appviews surface when applying trust policies.

  • Appeal a previously taken moderation action