A lexicon-driven AppView for ATProto. happyview.dev
backfill firehose jetstream atproto appview oauth lexicon
8
fork

Configure Feed

Select the types of activity you want to include in your feed.

docs: language cleanup

Trezy adafd4a4 26564c65

+5 -7
+1 -3
packages/docs/docs/getting-started/quickstart.md
··· 49 49 50 50 ## Next steps 51 51 52 - Here's where to go from here: 53 - 54 - - [**Statusphere tutorial**](../tutorials/statusphere.md): end-to-end walkthrough building a complete AppView with record, query, and procedure lexicons 52 + - [**Statusphere tutorial**](../tutorials/statusphere.md): full walkthrough building a complete AppView with record, query, and procedure lexicons 55 53 - [**Lexicons guide**](../guides/lexicons.md): target collections, backfill flag, network lexicons 56 54 - [**Lua Scripting**](../guides/scripting.md): custom query and procedure logic 57 55 - [**Configuration**](configuration.md): environment variables and tuning
+1 -1
packages/docs/docs/guides/backfill.md
··· 19 19 20 20 ## Job lifecycle 21 21 22 - A backfill job moves through `pending → running → completed` (or `failed`). Unlike earlier versions of HappyView that relied on Tap, the job is only marked `completed` once every discovered repo has been processed end-to-end — there is no separate downstream queue. Progress is visible in real time on the dashboard's Backfill page. 22 + A backfill job moves through `pending → running → completed` (or `failed`). Unlike earlier versions of HappyView that relied on Tap, the job is only marked `completed` once every discovered repo has been fully processed — there is no separate downstream queue. Progress is visible in real time on the dashboard's Backfill page. 23 23 24 24 If a job fails midway, the `error` field contains the failure reason. Re-running the backfill resumes from scratch but is idempotent (records are upserted by URI). 25 25
+1 -1
packages/docs/docs/reference/scripts/paginated-list.md
··· 37 37 38 38 ## Use case 39 39 40 - A straightforward list endpoint for feeds, timelines, or browsing records by collection. The `cursor` value returned by `db.query` is an opaque string. Clients pass it back as the `cursor` parameter to fetch the next page — don't parse or modify it. 40 + A list endpoint for feeds, timelines, or browsing records by collection. The `cursor` value returned by `db.query` is an opaque string. Clients pass it back as the `cursor` parameter to fetch the next page — don't parse or modify it.
+2 -2
packages/docs/docs/tutorials/statusphere.md
··· 108 108 109 109 See [XRPC API](../reference/xrpc-api.md) for the full default query behavior. 110 110 111 - ## Step 4: Enhance the query with a Lua script 111 + ## Step 4: Customize the query with a Lua script 112 112 113 113 The default query behavior works, but let's customize it with a [Lua script](../guides/scripting.md). The script will handle single-record lookups by URI and paginated listing with an optional DID filter. 114 114 ··· 216 216 - [XRPC API](../reference/xrpc-api.md): Understand how the generated endpoints behave 217 217 - [Admin API](../reference/admin-api.md): Automate lexicon management via the API 218 218 - [Statusphere example app](https://github.com/bluesky-social/statusphere-example-app): See the full Statusphere frontend 219 - - [ATProto Statusphere guide](https://atproto.com/guides/applications): Deep dive into how the app works at the protocol level 219 + - [ATProto Statusphere guide](https://atproto.com/guides/applications): How the app works at the protocol level