Skip to content
Browse lexicons
matching 74 lexicons
ink.branchline
20
Narrow ›
-
ink.branchline.bookmark
record
A bookmark the authoring account placed on a bud — a private-intent save pointing at a specific bud in a story. The AppView collapses bookmarks on the same ancestor chain into a single record: re-bookmarking a bud that is an ancestor or descendant of an existing bookmark rewrites the existing record's subject via putRecord rather than creating a second one. Navigation resolves the bookmark to the furthest-read bud on the path containing the subject, falling back to the subject itself.
-
ink.branchline.bud
record
A bud: one contribution to a story tree. Freshly written buds grow for 24h (not yet followable); after that they open as 'blooms' that other writers can extend; past 48h without children they lock into 'branches'. These lifecycle stages are views of the same record, not different record types. The AppView enforces a 500-word ceiling on `text` (counted via Unicode word segmentation); writes that exceed it are rejected as WordLimitExceeded.
-
ink.branchline.createBookmark
procedure
Bookmark a bud. The caller must be signed in. If the caller already has a bookmark in the same story whose subject is an ancestor or descendant of the new subject, the existing record is rewritten in place (putRecord) so the bookmark list stays one-per-thread. Otherwise a new ink.branchline.bookmark record is created in the caller's PDS and mirrored into the local read cache.
-
ink.branchline.createPollen
procedure
Pollinate a bud — a lightweight mark of appreciation. The caller must be signed in. The AppView writes an ink.branchline.pollen record to the caller's PDS and mirrors it into the local read cache. At most one pollen grain per (author, subject) is honored; retrying a call for the same subject is rejected with DuplicatePollen.
-
ink.branchline.editBud
procedure
Edit the title, text, and/or inline formatting of an existing bud. The caller must be signed in and must be the bud's author. The bud must have no children and must not be locked — edits to a bud with descendants would reshape text that later writers have already continued from, and locked buds are frozen by an admin. The AppView overwrites the ink.branchline.bud record in the caller's PDS via putRecord and mirrors the new row into the local read cache. `createdAt` and `bloomsAt` are preserved;
-
ink.branchline.getBranch
query
Get the full path of AT-URIs from root to bud in story order, oldest first.
-
ink.branchline.getBuds
query
Hydrate full bud views for a set of AT-URIs. Buds are returned in the same order as the input URIs. Unknown URIs are silently omitted from the response.
-
ink.branchline.getSeeds
query
Hydrate seed views for a set of AT-URIs. Seeds are returned in the same order as the input URIs. Unknown URIs are silently omitted.
-
ink.branchline.listAuthorActivity
query
Per-day bud counts for an author over the trailing 30 days in the viewer's local timezone, plus a current streak (consecutive days ending today with at least one bud). Powers the leaf-themed activity strip on profile pages.
-
ink.branchline.listAuthorBookmarks
query
List bookmarks authored by an actor, newest first. Bookmarks are public records; any viewer may list them.
-
ink.branchline.listAuthorBuds
query
List buds written by an author, surfacing only the terminal contributions per branch: a bud is included when the author has no descendant bud beneath it. Collapses back-and-forth exchanges so each chain the author participated in appears at most once, represented by their most recent bud in that chain.
-
ink.branchline.listAuthorPlantings
query
List trees planted by an author. A planting is a root bud (depth 0) authored by `actor`; each entry reports the root AT-URI and the height of the tallest branch descended from it.
-
ink.branchline.listAuthorSeeds
query
List seeds that an author can trade or plant
-
ink.branchline.listBlooms
query
List active blooms: every bud past its 24h growing window. Blooms never age out of eligibility; the 'pollen' sort's time-decay weighting is what sinks stale entries. Supports 'recent' (newest createdAt first) and 'pollen' (decay-weighted pollen score across the bloom and its ancestors).
-
ink.branchline.listNotifications
query
List unread notifications for the authenticated viewer. Requires a valid session cookie; responds 401 otherwise. Notifications are derived from indexed records (no separate notification table) and grouped by subject; a group counts as unread when its latestAt is newer than the viewer's stored readAt for that group (see ink.branchline.markNotificationsRead). Three kinds are emitted: 'continuation' (someone grew one of the viewer's buds), 'seedGrant' (someone gave the viewer a seed), and 'bookmark
-
ink.branchline.markNotificationsRead
procedure
Mark one or more notification groups as read for the authenticated viewer. Each entry stamps the viewer's readAt for that groupKey, hiding the group from ink.branchline.listNotifications until fresh activity pushes latestAt past the stamp. Responds 401 without a session.
-
ink.branchline.pollen
record
A grain of pollen the authoring account carried to a bud — a lightweight mark of appreciation. At most one pollen record per (author, subject) is honored by the AppView; tombstoning the record removes it.
-
ink.branchline.publishBud
procedure
Publish a new bud. The parent may be another bud (continuation) or a seed (planting a root bud). The caller must be signed in. The AppView writes an ink.branchline.bud record to the caller's PDS and mirrors it into the local read cache so the new bud is immediately navigable. Rejection reasons mirror ink.branchline.bud create validation — 500-word limit on `text`, 24h parent growing window, self-reply, seed chain/expiry/grantee checks, etc.
-
ink.branchline.publishSeed
procedure
Gift a seed. The caller must be signed in and must be the grantee of `grantor`; publishing passes that seed's planting right on to `grantee` as a new child seed. The AppView writes an ink.branchline.seed record to the caller's PDS and mirrors it into the local read cache. Root (grantor-less) seeds are not created through this endpoint — they are authored only by the branchline.ink repo.
-
ink.branchline.seed
record
A seed, the permission to plant a story tree.
ink.igav
13
Narrow ›
-
ink.igav.galaxius.temp.authPlayer
permission-set
The permission set a Galaxius player grants: write join records for the game they are joining, and delete them, and nothing else.
-
ink.igav.galaxius.temp.game
record
A Galaxius game: its map, its ruleset and the settings a server needs to run it.
-
ink.igav.galaxius.temp.join
record
A player joining a Galaxius game: who they are and the session key their orders are signed with.
-
ink.igav.galaxius.temp.map
record
not from the namespace authority
A Galaxius map: the star field, the seat count and the credits for one playfield.
-
ink.igav.galaxius.temp.period
record
One published period of a Galaxius game: the orders batch, the revealed secret and the state it produced.
-
ink.igav.galaxius.temp.result
record
The final record of a Galaxius game: the last period, the outcome and the standings.
-
ink.igav.galaxius.temp.ruleset
record
not from the namespace authority
A Galaxius ruleset: the engine's canonical constants, plus a name and a model.
-
ink.igav.galaxius.temp.seat
record
A seated player in a Galaxius game, written by the game master.
-
ink.igav.whatmealtodo.defs
defs
A person overrode the normalizer's proposal. Every one of these is a case the rules got wrong, which is why it is recorded rather than discarded.
-
ink.igav.whatmealtodo.getRecipes
query
The public recipe index, unfiltered and unauthenticated. It exists to prove the indexer works before there is a pantry to match against, and stays because an AppView that cannot show what it indexed is hard to debug.
-
ink.igav.whatmealtodo.getSuggestions
query
Recipes ranked by how much of them the caller's pantry already covers. The one query that needs both halves of this AppView: a network-wide public index, and one non-public repo. Neither source can answer it alone. Pantry items marked `kind: staple` are asymmetric here and callers should say so to their users: a staple counts towards a recipe that needs it, but never brings one up — candidates are drawn from held ingredients only, so a pantry of nothing but staples answers with nothing.
-
ink.igav.whatmealtodo.pantry
space
One person's pantry: what they actually have in the house. A personal-data space, so its authority is the owner's own DID and their PDS is both repo host and space host.
-
ink.igav.whatmealtodo.pantryItem
record
One thing in a pantry. Structured on purpose: a recipe ingredient is prose because recipe.exchange chose prose, but this lexicon is being written from scratch and has no reason to inherit that.
ink.resenha
41
Narrow ›
-
ink.resenha.actor.profile
record
not from the namespace authority
Marks an account as a Resenha reader. Resenha's server reads it to know who uses Resenha, and whether they agreed to be suggested to other readers.
-
ink.resenha.book.getBook
query
not from the namespace authority
A book's page from Resenha's index: an edition's readers with their readings, everyone's reviews of it, and its other editions with theirs. By BookHive ID or ISBN-13, so a book BookHive's catalogue doesn't know has one page shared by its readers. Readers the caller blocks are left out. Requires the caller's service token.
-
ink.resenha.book.getReaders
query
not from the namespace authority
How many readers have a book, by status.
-
ink.resenha.book.getReviews
query
not from the namespace authority
Reviews of a book from every source, newest first.
-
ink.resenha.book.resolve
query
not from the namespace authority
Every key Resenha's index knows for a book, and its other editions, from one key: a BookHive ID, an ISBN-13, an Amazon number or an Open Library work. Learned from BookHive's catalogue, readers' own links between their records in different apps, and Open Library. Public, no sign-in: any book app can fill the slots its records leave empty, such as Popfeed's hiveId or BookHive's ISBN. Answers come from the index alone; nothing is asked of any catalogue for them.
-
ink.resenha.bookLink
record
Which catalog book a book in the reader's library is, and which of the reader's records in each book app are that book. Resenha writes these when it matches a reader's Popfeed books to BookHive's catalog, so Popfeed's and BookHive's own records are never changed to hold the match.
-
ink.resenha.bookReview
record
Connects a book review, published as a site.standard.document, to the book it reviews.
-
ink.resenha.defs
defs
Views shared by the calls Resenha's server answers.
-
ink.resenha.discover.getBooks
query
not from the namespace authority
The books Resenha's readers started, finished or reviewed most lately.
-
ink.resenha.discover.getReaders
query
not from the namespace authority
Resenha's readers who agreed to be suggested.
-
ink.resenha.discover.getReviews
query
not from the namespace authority
Recent reviews by Resenha's readers.
-
ink.resenha.ebook
record
A book file the account keeps for reading in Resenha: an EPUB, a PDF or a comic archive. The file is a blob in the account's repository, which keeps it only while a record refers to it.
-
ink.resenha.ebookKey
record
Which key encrypts the account's ink.resenha.privateEbook files. The key itself stays on the reader's devices; this record only names it, and keeps a copy locked with a recovery key when the reader saved one.
-
ink.resenha.feed.comment
record
not from the namespace authority
A comment on a reader's book record, or a reply to such a comment: the conversation about a reader reading a book, for activities in Resenha's Feed that have no post to reply to. One subject per book per reader, so comments on their starting and finishing it are one thread. Written in the commenter's account; Resenha's server threads them and tells the reader.
-
ink.resenha.feed.like
record
not from the namespace authority
A like on a reader's book record (a BookHive book record or a Popfeed list item), for an activity in Resenha's Feed that has no post to like: started, finished, wants to read, abandoned, progress, or a review announced nowhere. Written in the liker's account. Resenha's server counts them for the Feed.
-
ink.resenha.friend
record
Marks that the account added another reader as a friend in Resenha. Friends are readers who follow each other; this record lets the other reader's app show the follow as a friend request.
-
ink.resenha.migrationChoice
record
What a reader chose while Resenha moves their Popfeed books to BookHive and Resenha readings: their changes to the proposed plan, the plan they confirmed, and which device is writing. These records are public, like every record in the reader's repository. Resenha deletes each book's choice when it writes that book, and the rest when the move finishes.
-
ink.resenha.moderation.getState
query
not from the namespace authority
Whether the caller is one of Resenha's maintainers, and how many reports await them. Cheap, for the Settings row and its badge.
-
ink.resenha.moderation.listRemoved
query
not from the namespace authority
The Resenha comments the maintainers removed, newest first, each with its words, so one can be put back.
-
ink.resenha.moderation.listReports
query
not from the namespace authority
The reports on Resenha comments, for a maintainer: open ones newest first, or the resolved ones.
-
ink.resenha.moderation.resolveReport
procedure
not from the namespace authority
A maintainer's decision on a reported Resenha comment: remove it from every reader's thread, keep it, remove it and hide its author from suggestions and the pack, or put a removed comment back. The record stays in its author's account either way.
-
ink.resenha.notification.dismiss
procedure
not from the namespace authority
Dismisses a follow or friend request from an account.
-
ink.resenha.notification.getUnreadCount
query
not from the namespace authority
How many notifications the caller hasn't seen.
-
ink.resenha.notification.listNotifications
query
not from the namespace authority
The caller's notifications from Bluesky, BookHive, Popfeed, comics and Resenha, newest first.
-
ink.resenha.notification.registerPush
procedure
not from the namespace authority
Registers a device for push notifications.
-
ink.resenha.notification.unregisterPush
procedure
not from the namespace authority
Stops push notifications to a device.
-
ink.resenha.notification.updatePreferences
procedure
not from the namespace authority
Chooses whose likes and quotes are pushed to the caller's devices.
-
ink.resenha.notification.updateSeen
procedure
not from the namespace authority
Marks the caller's notifications seen up to a time.
-
ink.resenha.parlor.getFollowers
query
not from the namespace authority
Who follows the caller, newest first: the readers among them by default, or everyone. The server pages the caller's followers from Bluesky's AppView once a week and hears new follows as they happen.
-
ink.resenha.parlor.getFollowing
query
not from the namespace authority
The readers among the caller's follows: how many books they keep, what they're reading now, when the caller followed them and when they were last active; with their names and pictures as the server has them.
-
ink.resenha.parlor.getRelationship
query
not from the namespace authority
How the caller and another reader stand to each other, as Resenha's server knows it: whether each follows the other, and which of the caller's follows follow them, for "followed by people you follow" on a profile.
-
ink.resenha.parlor.getReviews
query
not from the namespace authority
The reviews of the readers the caller follows, newest first: dated by when they were published from Resenha, else by when the book was finished or added.
-
ink.resenha.parlor.getStarterPacks
query
not from the namespace authority
The starter packs Resenha keeps in its official account, with their members, for an empty Parlor.
-
ink.resenha.parlor.getSuggestions
query
not from the namespace authority
Readers for the caller to follow when their Parlor is empty: Resenha's discoverable readers first, then BookHive's and Popfeed's active in the last six months, then anyone reviewing this year, by days active within a tier; never the caller or anyone they follow. Ranked once an hour.
-
ink.resenha.parlor.getThread
query
not from the namespace authority
The conversation about a reader reading a book: the Resenha comments and BookHive buzzes on their book record, with the likes count and whether the caller liked it.
-
ink.resenha.parlor.getTimeline
query
not from the namespace authority
What the readers the caller follows did with their books, newest first: started, finished, reviewed, wanted to read, abandoned, and progress; with their names and pictures and the books' covers as the server has them.
-
ink.resenha.parlor.reportComment
procedure
not from the namespace authority
Reports a Resenha comment to Resenha's maintainer, who can remove it from every reader's thread. Bluesky's moderators don't read these records, so the report comes here.
-
ink.resenha.parlor.updateState
procedure
not from the namespace authority
Whether the caller said Done to the readers-to-follow list, so it stays away on every device.
-
ink.resenha.privateEbook
record
A book file the account keeps for reading in Resenha, encrypted on the reader's devices before upload: an EPUB, a PDF or a comic archive. Only the reader's devices hold the key, so the file, its cover and its details can't be read from the account's server. Replaces an ink.resenha.ebook record with the same record key.
-
ink.resenha.reading
record
A reader's reading of a book BookHive's catalogue doesn't hold, or can't be matched to for certain: the home of last resort, so any book can be added to a library and reviewed. One per book. Status, dates, rating, review and progress live here as they do on a buzz.bookhive.book; the book is named in every key anyone uses, so any app that recognises one of them can show the reading. When BookHive's catalogue has the book, Resenha moves the reading there: it writes a buzz.bookhive.book with everyt
-
ink.resenha.storage.getUsage
query
not from the namespace authority
What the caller's account holds on Resenha's own server, pds.resenha.ink, as Resenha's server last measured it: every file, measured from the account's blobs; the database, when the host has measured it; and the share taken by the caller's eBook and comic files, which is what Resenha's plan counts. Only the caller's own figures.