Upvote AT Protocol lexicons #
The canonical schemas for upvote.at's public records and XRPC interface.
at.upvote.signal: a TID-keyed upvote whose subject is a canonical AT or HTTP(S) URI.at.upvote.comment: a TID-keyed Markdown comment.subjectis the immediate target; optionalrootSubjectpreserves the resource context independently of missing parents.at.upvote.settings: a public singleton atself. Preserve fields written by other clients when updating it.
The current HappyView instance supports toggleSignal, toggleFollow, toggleRecommend, toggleSubscription, createComment, deleteComment, and putSettings for managed sessions. toggleSignal accepts subject. toggleRecommend (a document) and toggleSubscription (a publication) write or delete standard.site's own site.standard.graph.recommend and .subscription records in the caller's repo, TID-keyed as Leaflet writes them. Settings writes are unconditional replacements after a client-side merge; Lua failures may be returned in HTTP 200 bodies. Comment counts use getComments?all=true.
The "Elsewhere in the Atmosphere" queries read other apps' public records from the instance's index, display-only: getSembleSaves (Semble cards and collections), getStandardSiteRecommends and getStandardSiteSubscriptions (standard.site's graph; the latter can also count a publication's subscribers), getStandardReaderMarks (Standard Reader reads and bookmarks), getGleanLikes (Glean likes, matched by URL with or without tracking parameters), getBlueskyDiscussion (the Bluesky post a document's bskyPostRef names, read from the AppView), and getElsewhereSummaries (a page of subjects at once: each source's crowd size and newest few markers, or BatchUnavailable when the instance has no raw index read).
getShelfRecords lists shelf.cafe votes or comments a page at a time, each with its item's URL. A vote on an item counts toward that page's points.
The setSignal, setFollow, getCommentEdges, and normalizeSubject schemas are not implemented by this HappyView instance and are excluded from the website's HappyView sync. Subject normalization is available through the website's server route. Changes must use the existing HappyView runtime and Lua APIs; runtime patches are outside this project's scope.