app.userinput.edit

A revision of a discussion or reply, written as a sidecar that points at the original (never mutating it). Only honored when authored by the subject's own author; the newest createdAt is the live content, and the full set is the edit history. Lives in the author's repo.

Repository @userinput.app did:plc:uyixj57k6nmxrdj7pjs2ss5s namespace authority
Details · record, key tid
Kindrecord
Record keytid
Authorityuserinput.app
Indexed

Record

record · key tid

Properties

body

string

Replacement body.

  • maxLength: 20000
  • maxGraphemes: 10000

createdAt

requiredstring · datetime

subject

requiredref

The discussion or reply being revised. Indexed by constellation at subject.uri. The pinned cid identifies the version this edit was authored against.

tags

array

Replacement tag values (discussion edits only), drawn from the space's tag list.

  • maxLength: 8
itemsstring
  • maxLength: 64

title

string

Replacement title (discussion edits only).

  • maxLength: 600
  • maxGraphemes: 300

Similar lexicons

semantic match

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

  • A reply on a discussion. Lives in the author's repo.

  • A piece of feedback posted into a space. Lives in the author's repo and points at the space.

  • An author.s request to admit an exact version of their own post. discussion distinguishes a reply opt-in from a root submission.

  • A reply in a thread. Lives in the author's repo. Flat by default; parent enables quote-chain threading.

  • app.voresky.edithistory

    record not from the namespace authority

    One revision of a post's text. Bluesky's AppView ignores updates to `app.bsky.feed.post` records, so an edit is expressed as a new record here rather than as a mutation of the post. Clients that understand this collection display the highest-numbered revision in place of the post's original text; clients that do not see the original, unchanged. The record key is `<postRkey>.<editNumber>` (for example `3abc123.1`); split on the LAST `.`, since TID-style record keys may themselves contain dots.