From a5b7a833eb52e52e1073a2ac7d4d5a7759db4bee Mon Sep 17 00:00:00 2001 From: Trezy Date: Sat, 1 Aug 2026 10:32:43 -0500 Subject: [PATCH] chore: the great atproto renamening Signed-off-by: Trezy --- .../content/docs/api-reference/admin/meta.json | 1 + .../docs/api-reference/admin/service-entries.md | 2 +- .../docs/api-reference/admin/service-identity.md | 4 ++-- .../content/docs/api-reference/lua/database-api.md | 2 +- .../docs/content/docs/api-reference/lua/meta.json | 1 + .../content/docs/experimental/spaces/changelog.md | 2 +- .../docs/content/docs/experimental/spaces/index.md | 4 ++-- .../content/docs/experimental/spaces/invites.md | 2 +- .../content/docs/experimental/spaces/records.md | 2 +- .../content/docs/getting-started/configuration.md | 2 +- .../docs/content/docs/getting-started/dashboard.md | 2 +- .../docs/getting-started/deployment/docker.md | 2 +- .../docs/getting-started/deployment/other.md | 2 +- .../docs/getting-started/deployment/production.md | 4 ++-- .../docs/getting-started/service-identity.md | 14 +++++++------- packages/docs/content/docs/guides/backfill.md | 2 +- .../docs/content/docs/guides/background-jobs.md | 2 +- packages/docs/content/docs/guides/permissions.md | 2 +- .../docs/content/docs/guides/record-scripts.md | 2 +- packages/docs/content/docs/index.md | 6 +++--- packages/docs/content/docs/reference/glossary.md | 8 ++++---- .../docs/sdk/oauth-client-browser/overview.md | 2 +- .../content/docs/sdk/oauth-client-node/overview.md | 2 +- .../docs/content/docs/tutorials/statusphere.md | 4 ++-- 24 files changed, 39 insertions(+), 37 deletions(-) diff --git a/packages/docs/content/docs/api-reference/admin/meta.json b/packages/docs/content/docs/api-reference/admin/meta.json index e93ac1b..6def23e 100644 --- a/packages/docs/content/docs/api-reference/admin/meta.json +++ b/packages/docs/content/docs/api-reference/admin/meta.json @@ -17,6 +17,7 @@ "domains", "script-variables", "api-clients", + "linked-repos", "plugins", "dead-letters", "service-identity", diff --git a/packages/docs/content/docs/api-reference/admin/service-entries.md b/packages/docs/content/docs/api-reference/admin/service-entries.md index eefebc7..6152cb2 100644 --- a/packages/docs/content/docs/api-reference/admin/service-entries.md +++ b/packages/docs/content/docs/api-reference/admin/service-entries.md @@ -146,7 +146,7 @@ curl -X POST http://127.0.0.1:3000/admin/service-entries \ | Field | Type | Required | Description | | -------------- | ------ | -------- | ----------------------------------------------------------- | | `fragment_id` | string | yes | DID document fragment (e.g. `#feed`, `#happyview`) | -| `service_type` | string | yes | AT Protocol service type (e.g. `BskyFeedGenerator`) | +| `service_type` | string | yes | atproto service type (e.g. `BskyFeedGenerator`) | The entry is created with `access_mode` set to `all`. The endpoint URL is derived from `PUBLIC_URL`. diff --git a/packages/docs/content/docs/api-reference/admin/service-identity.md b/packages/docs/content/docs/api-reference/admin/service-identity.md index 0e1656e..7f16f3b 100644 --- a/packages/docs/content/docs/api-reference/admin/service-identity.md +++ b/packages/docs/content/docs/api-reference/admin/service-identity.md @@ -2,7 +2,7 @@ title: "Service Identity" --- -Manage the service identity configuration: the DID and identity mode that HappyView uses to identify itself on the AT Protocol network. All endpoints require the `settings:manage` permission. +Manage the service identity configuration: the DID and identity mode that HappyView uses to identify itself on the atproto network. All endpoints require the `settings:manage` permission. ```ts tab="TypeScript" tab-group="language" const TOKEN = "hv_..."; // your API key @@ -86,7 +86,7 @@ Returns the current service identity configuration, or `null` if no identity has | ---------------- | ---------------------------------------------------- | | `did_web` | HappyView derives a `did:web` from its public URL | | `did_plc` | HappyView manages its own `did:plc` identity | -| `attach_account` | HappyView uses an existing AT Protocol account's DID | +| `attach_account` | HappyView uses an existing atproto account's DID | | `not_exposed` | No service identity is exposed on the network | ## Update service identity diff --git a/packages/docs/content/docs/api-reference/lua/database-api.md b/packages/docs/content/docs/api-reference/lua/database-api.md index 434a019..cfabebd 100644 --- a/packages/docs/content/docs/api-reference/lua/database-api.md +++ b/packages/docs/content/docs/api-reference/lua/database-api.md @@ -181,7 +181,7 @@ Available internal tables: | Table | Contents | | --- | --- | -| `happyview_records` | indexed AT Protocol records | +| `happyview_records` | indexed atproto records | | `happyview_record_refs` | backlink index | | `happyview_labels` | applied labels | | `happyview_lexicons` | uploaded lexicons | diff --git a/packages/docs/content/docs/api-reference/lua/meta.json b/packages/docs/content/docs/api-reference/lua/meta.json index 09bfb19..573546e 100644 --- a/packages/docs/content/docs/api-reference/lua/meta.json +++ b/packages/docs/content/docs/api-reference/lua/meta.json @@ -8,6 +8,7 @@ "atproto-api", "json-api", "jobs-api", + "linked-repos-api", "utility-globals", "standard-libraries" ] diff --git a/packages/docs/content/docs/experimental/spaces/changelog.md b/packages/docs/content/docs/experimental/spaces/changelog.md index a4d3776..125f2c9 100644 --- a/packages/docs/content/docs/experimental/spaces/changelog.md +++ b/packages/docs/content/docs/experimental/spaces/changelog.md @@ -29,7 +29,7 @@ Aligns with the merged [Proposal 0016](https://github.com/bluesky-social/proposa ## v2.10.0 — Proposal 0016 Alignment -Major restructuring to align with [AT Protocol Proposal 0016](https://github.com/bluesky-social/proposals) (Permissioned Data). +Major restructuring to align with [atproto Proposal 0016](https://github.com/bluesky-social/proposals) (Permissioned Data). ### Namespace split diff --git a/packages/docs/content/docs/experimental/spaces/index.md b/packages/docs/content/docs/experimental/spaces/index.md index ead6d27..5931712 100644 --- a/packages/docs/content/docs/experimental/spaces/index.md +++ b/packages/docs/content/docs/experimental/spaces/index.md @@ -3,7 +3,7 @@ title: "Overview" --- -Permissioned Spaces are experimental and the API will change. This implementation follows [AT Protocol Proposal 0016](https://github.com/bluesky-social/proposals) (Permissioned Data). HappyView uses the `com.atproto.space.*` and `com.atproto.simplespace.*` namespaces. The previous `dev.happyview.space.*` endpoints remain available as backward-compatible aliases until v3. +Permissioned Spaces are experimental and the API will change. This implementation follows [atproto Proposal 0016](https://github.com/bluesky-social/proposals) (Permissioned Data). HappyView uses the `com.atproto.space.*` and `com.atproto.simplespace.*` namespaces. The previous `dev.happyview.space.*` endpoints remain available as backward-compatible aliases until v3. Spaces are containers for permissioned data in atproto. Unlike regular public records that live in a user's repo, space records are gated by membership — only members can read or write data within a space. @@ -142,7 +142,7 @@ Spaces also support **delegation** — adding another space as a member, which t ## Alignment with Proposal 0016 -HappyView implements [AT Protocol Proposal 0016](https://github.com/bluesky-social/proposals) (Permissioned Data) with some HappyView-specific extensions. +HappyView implements [atproto Proposal 0016](https://github.com/bluesky-social/proposals) (Permissioned Data) with some HappyView-specific extensions. ### Protocol features implemented diff --git a/packages/docs/content/docs/experimental/spaces/invites.md b/packages/docs/content/docs/experimental/spaces/invites.md index 3cb0a6f..7402b07 100644 --- a/packages/docs/content/docs/experimental/spaces/invites.md +++ b/packages/docs/content/docs/experimental/spaces/invites.md @@ -9,7 +9,7 @@ This API is experimental and will change. See the [Permissioned Spaces overview] Invites let space authorities distribute membership tokens without knowing recipients' DIDs in advance. -Invites are a HappyView-specific feature, not part of the AT Protocol spaces spec. They may be replaced by a different mechanism in the future. +Invites are a HappyView-specific feature, not part of the atproto spaces spec. They may be replaced by a different mechanism in the future. ## Creating an invite diff --git a/packages/docs/content/docs/experimental/spaces/records.md b/packages/docs/content/docs/experimental/spaces/records.md index 4ddca14..378e350 100644 --- a/packages/docs/content/docs/experimental/spaces/records.md +++ b/packages/docs/content/docs/experimental/spaces/records.md @@ -6,7 +6,7 @@ title: "Records" This API is experimental and will change. See the [Permissioned Spaces overview](../spaces.md) for context. -Space records are stored separately from public AT Protocol records. They use the `at://` scheme with a `space` path segment to distinguish them from public records: +Space records are stored separately from public atproto records. They use the `at://` scheme with a `space` path segment to distinguish them from public records: ``` at:// did:plc:abcdefghijklmnop1234567890 / space / com.example.forum / main / did:plc:author / com.example.forum.post / abcdefghijklmnop1234567890 diff --git a/packages/docs/content/docs/getting-started/configuration.md b/packages/docs/content/docs/getting-started/configuration.md index 207a888..07e06e6 100644 --- a/packages/docs/content/docs/getting-started/configuration.md +++ b/packages/docs/content/docs/getting-started/configuration.md @@ -39,7 +39,7 @@ HappyView is configured via environment variables. A `.env` file in the project | `POLICY_URI` | no | --- | URL to privacy policy. Overridden by database setting if set via admin API | -ATProto OAuth loopback clients are registered with `127.0.0.1`. If you set `PUBLIC_URL` to `http://localhost:3000`, OAuth sign-in will fail because the redirect URI won't match the loopback client ID. Always use `http://127.0.0.1:3000` for local development. +atproto OAuth loopback clients are registered with `127.0.0.1`. If you set `PUBLIC_URL` to `http://localhost:3000`, OAuth sign-in will fail because the redirect URI won't match the loopback client ID. Always use `http://127.0.0.1:3000` for local development. ## Example `.env` diff --git a/packages/docs/content/docs/getting-started/dashboard.md b/packages/docs/content/docs/getting-started/dashboard.md index 9b78664..1e60df2 100644 --- a/packages/docs/content/docs/getting-started/dashboard.md +++ b/packages/docs/content/docs/getting-started/dashboard.md @@ -99,7 +99,7 @@ View the audit log of admin actions. Events include user creation, lexicon uploa ### Service Identity -Configure the AT Protocol service identity for your HappyView instance — either a `did:web` derived from your public URL, a `did:plc` you control, or a linked atproto account. This determines the DID that signs service-level interactions on the network. +Configure the atproto service identity for your HappyView instance — either a `did:web` derived from your public URL, a `did:plc` you control, or a linked atproto account. This determines the DID that signs service-level interactions on the network. ### Experiments diff --git a/packages/docs/content/docs/getting-started/deployment/docker.md b/packages/docs/content/docs/getting-started/deployment/docker.md index 0032897..b626035 100644 --- a/packages/docs/content/docs/getting-started/deployment/docker.md +++ b/packages/docs/content/docs/getting-started/deployment/docker.md @@ -19,7 +19,7 @@ cp .env.example .env Edit `.env` and set at least `PUBLIC_URL` (e.g. `http://127.0.0.1:3000`) and `SESSION_SECRET` (at least 64 characters). The defaults work for everything else. See [Configuration](../configuration.md) for the full list of environment variables. -ATProto OAuth loopback clients are registered with `127.0.0.1`. If you set `PUBLIC_URL` to `http://localhost:3000`, OAuth sign-in will fail because the redirect URI won't match the loopback client ID. Always use `http://127.0.0.1:3000` for local development. +atproto OAuth loopback clients are registered with `127.0.0.1`. If you set `PUBLIC_URL` to `http://localhost:3000`, OAuth sign-in will fail because the redirect URI won't match the loopback client ID. Always use `http://127.0.0.1:3000` for local development. ## 2. Start the stack diff --git a/packages/docs/content/docs/getting-started/deployment/other.md b/packages/docs/content/docs/getting-started/deployment/other.md index 69b12e3..5cfe3a0 100644 --- a/packages/docs/content/docs/getting-started/deployment/other.md +++ b/packages/docs/content/docs/getting-started/deployment/other.md @@ -27,7 +27,7 @@ SESSION_SECRET=change-me-in-production ``` -ATProto OAuth loopback clients are registered with `127.0.0.1`. If you set `PUBLIC_URL` to `http://localhost:3000`, OAuth sign-in will fail because the redirect URI won't match the loopback client ID. Always use `http://127.0.0.1:3000` for local development. +atproto OAuth loopback clients are registered with `127.0.0.1`. If you set `PUBLIC_URL` to `http://localhost:3000`, OAuth sign-in will fail because the redirect URI won't match the loopback client ID. Always use `http://127.0.0.1:3000` for local development. Or if you prefer Postgres: diff --git a/packages/docs/content/docs/getting-started/deployment/production.md b/packages/docs/content/docs/getting-started/deployment/production.md index edd589b..23c65f0 100644 --- a/packages/docs/content/docs/getting-started/deployment/production.md +++ b/packages/docs/content/docs/getting-started/deployment/production.md @@ -49,7 +49,7 @@ The base path is applied at container startup without rebuilding the image, so p ### XRPC endpoints -ATProto clients expect XRPC endpoints at `/xrpc/*` on the domain root. When using a base path, configure your reverse proxy to rewrite `/xrpc/*` requests so they reach HappyView under its base path. Here's an example using Caddy: +atproto clients expect XRPC endpoints at `/xrpc/*` on the domain root. When using a base path, configure your reverse proxy to rewrite `/xrpc/*` requests so they reach HappyView under its base path. Here's an example using Caddy: ``` example.com { @@ -63,7 +63,7 @@ example.com { redir /hv/ permanent } - # ATProto XRPC — rewrite to base path before proxying + # atproto XRPC — rewrite to base path before proxying handle /xrpc/* { rewrite * /hv{uri} reverse_proxy happyview:3000 diff --git a/packages/docs/content/docs/getting-started/service-identity.md b/packages/docs/content/docs/getting-started/service-identity.md index 8a0bcd8..a20f7b7 100644 --- a/packages/docs/content/docs/getting-started/service-identity.md +++ b/packages/docs/content/docs/getting-started/service-identity.md @@ -2,7 +2,7 @@ title: "Service Identity" --- -An AT Protocol service identity lets your AppView authenticate itself to other services on the network. When a user's PDS routes a request, it verifies the destination by resolving the AppView's DID — without a service identity, standard AT Protocol app routing won't reach your instance. +An atproto service identity lets your AppView authenticate itself to other services on the network. When a user's PDS routes a request, it verifies the destination by resolving the AppView's DID — without a service identity, standard atproto app routing won't reach your instance. HappyView can operate without a service identity using its built-in auth, but configuring one is recommended for full network compatibility. @@ -29,7 +29,7 @@ Store the rotation key file somewhere safe and offline (e.g. a password manager, ### Linked account -Link your AppView to an existing AT Protocol account you control. HappyView verifies ownership by redirecting you to sign in through that account's PDS, then uses the account's existing DID as the service identity. +Link your AppView to an existing atproto account you control. HappyView verifies ownership by redirecting you to sign in through that account's PDS, then uses the account's existing DID as the service identity. ## Choosing an identity mode @@ -38,14 +38,14 @@ Link your AppView to an existing AT Protocol account you control. HappyView veri | Setup complexity | Automatic | Requires key backup | Requires existing account | | Domain independence | No — tied to your domain | Yes — survives domain changes | Depends on the linked account | | Key management | Automatic | You must back up the rotation key | Managed by the linked account's PDS | -| Best for | Single-domain deployments | Long-lived production instances | Operators who already have an AT Protocol presence | +| Best for | Single-domain deployments | Long-lived production instances | Operators who already have an atproto presence | ## Skipping setup -You can skip service identity configuration during setup. Your AppView will work with HappyView's built-in authentication, but standard AT Protocol service-to-service routing won't be available. You can configure a service identity later from **Settings > Service Identity** in the dashboard. +You can skip service identity configuration during setup. Your AppView will work with HappyView's built-in authentication, but standard atproto service-to-service routing won't be available. You can configure a service identity later from **Settings > Service Identity** in the dashboard. ## Further reading -- [AT Protocol identity specification](https://atproto.com/guides/identity) -- [DID methods in AT Protocol](https://atproto.com/specs/did) -- [AT Protocol glossary](https://atproto.com/guides/glossary) +- [atproto identity specification](https://atproto.com/guides/identity) +- [DID methods in atproto](https://atproto.com/specs/did) +- [atproto glossary](https://atproto.com/guides/glossary) diff --git a/packages/docs/content/docs/guides/backfill.md b/packages/docs/content/docs/guides/backfill.md index 414ebc0..6430909 100644 --- a/packages/docs/content/docs/guides/backfill.md +++ b/packages/docs/content/docs/guides/backfill.md @@ -22,7 +22,7 @@ Progress counters (`total_repos`, `resolved_repos`, `processed_repos`, `total_re ### Rate limiting -All three phases handle HTTP 429 responses. HappyView reads the `RateLimit-Reset` header (a Unix timestamp, the AT Protocol convention) to determine how long to wait, falling back to the `retry-after` header, then defaulting to 5 seconds. +All three phases handle HTTP 429 responses. HappyView reads the `RateLimit-Reset` header (a Unix timestamp, the atproto convention) to determine how long to wait, falling back to the `retry-after` header, then defaulting to 5 seconds. ## Job lifecycle diff --git a/packages/docs/content/docs/guides/background-jobs.md b/packages/docs/content/docs/guides/background-jobs.md index b1483e7..00ff67b 100644 --- a/packages/docs/content/docs/guides/background-jobs.md +++ b/packages/docs/content/docs/guides/background-jobs.md @@ -154,7 +154,7 @@ When `auth = true`, the worker loads the creator's OAuth session at execution ti ### When to use auth -Use `{ auth = true }` when the job needs to create, update, or delete records on the AT Protocol network on behalf of the user. For example, batch record creation, cross-collection syncs, or migrations that write back to the user's PDS. +Use `{ auth = true }` when the job needs to create, update, or delete records on the atproto network on behalf of the user. For example, batch record creation, cross-collection syncs, or migrations that write back to the user's PDS. Leave auth off (the default) for jobs that only read data, compute aggregates, sync to external services, clean up local records, or perform any work that doesn't touch a user's PDS. diff --git a/packages/docs/content/docs/guides/permissions.md b/packages/docs/content/docs/guides/permissions.md index b9a3ca8..157a350 100644 --- a/packages/docs/content/docs/guides/permissions.md +++ b/packages/docs/content/docs/guides/permissions.md @@ -20,7 +20,7 @@ HappyView defines 49 permissions organized by category: | Permission | Description | | --------------------------- | --------------------------------------- | -| `records:read` | Browse indexed AT Protocol records | +| `records:read` | Browse indexed atproto records | | `records:delete` | Delete individual records from the index | | `records:delete-collection` | Bulk-delete all records in a collection | diff --git a/packages/docs/content/docs/guides/record-scripts.md b/packages/docs/content/docs/guides/record-scripts.md index ea96e58..23639a8 100644 --- a/packages/docs/content/docs/guides/record-scripts.md +++ b/packages/docs/content/docs/guides/record-scripts.md @@ -2,7 +2,7 @@ title: "Record & Label Scripts" --- -Record and label scripts are Lua scripts that run in response to events on the AT Protocol network. **Record scripts** fire when a record in a collection is created, updated, or deleted. **Label scripts** fire when a label is applied to a record or actor. Both run **before** the event is indexed, giving you the ability to filter, transform, or trigger side effects. +Record and label scripts are Lua scripts that run in response to events on the atproto network. **Record scripts** fire when a record in a collection is created, updated, or deleted. **Label scripts** fire when a label is applied to a record or actor. Both run **before** the event is indexed, giving you the ability to filter, transform, or trigger side effects. These scripts are event-driven -- they react to incoming Jetstream events (which include events caused by HappyView's own PDS writes), not to XRPC requests. For scripts that run in response to XRPC queries and procedures, see [Lua Scripting](./lua-scripting.md). diff --git a/packages/docs/content/docs/index.md b/packages/docs/content/docs/index.md index e28ab6e..360b9c3 100644 --- a/packages/docs/content/docs/index.md +++ b/packages/docs/content/docs/index.md @@ -2,7 +2,7 @@ title: "Introduction" --- -HappyView is the best way to build an [AppView](https://atproto.com/guides/glossary#app-view) for the [AT Protocol](https://atproto.com). Upload your [lexicon](reference/glossary.md#atproto-terms) schemas and get a fully functional AppView, complete with [XRPC](reference/glossary.md#atproto-terms) endpoints, OAuth, real-time network sync, and historical [backfill](guides/backfill.md), without writing a single line of server code. +HappyView is the best way to build an [AppView](https://atproto.com/guides/glossary#app-view) for the [atproto](https://atproto.com). Upload your [lexicon](reference/glossary.md#atproto-terms) schemas and get a fully functional AppView, complete with [XRPC](reference/glossary.md#atproto-terms) endpoints, OAuth, real-time network sync, and historical [backfill](guides/backfill.md), without writing a single line of server code. Building an AppView from scratch means wiring up real-time event streams, record storage, XRPC routing, OAuth flows, and PDS write proxying before you can even think about your application. HappyView handles all of that. Define your data model with lexicons, add custom logic with Lua scripts when you need it, and ship your app. @@ -16,7 +16,7 @@ Building an AppView from scratch means wiring up real-time event streams, record - **Protocol-native:** Works with any PDS, resolves DIDs through the directory, and fetches [network lexicons](guides/lexicons.md#network-lexicons) via DNS authority resolution. -- **Permissioned Spaces:** Experimental support for [AT Protocol Proposal 0016](experimental/spaces/index.md) — membership-gated data containers with per-user repo state, cross-service credentials, and write notifications. +- **Permissioned Spaces:** Experimental support for [atproto Proposal 0016](experimental/spaces/index.md) — membership-gated data containers with per-user repo state, cross-service credentials, and write notifications. - **Full admin surface:** Built-in [dashboard](getting-started/dashboard.md) and [admin API](api-reference/admin/admin-api.md) for managing lexicons, users, API keys, API clients, backfill jobs, and plugins. @@ -38,5 +38,5 @@ Building an AppView from scratch means wiring up real-time event streams, record - [Record & Label Scripts](guides/label-scripts): React to record changes and label events in real time - [Labelers](guides/labelers.md): Subscribe to external labelers and manage content labels - [Plugins](guides/plugins.md): Integrate with external platforms using WASM plugins -- [Permissioned Spaces](experimental/spaces/index.md): Create membership-gated data containers with the AT Protocol spaces API +- [Permissioned Spaces](experimental/spaces/index.md): Create membership-gated data containers with the atproto spaces API - [Event Logs](guides/event-logs.md): Monitor system activity, debug script errors, and audit admin actions diff --git a/packages/docs/content/docs/reference/glossary.md b/packages/docs/content/docs/reference/glossary.md index d1dbb0c..1011404 100644 --- a/packages/docs/content/docs/reference/glossary.md +++ b/packages/docs/content/docs/reference/glossary.md @@ -2,11 +2,11 @@ title: "Glossary" --- -Key terms used throughout the HappyView documentation. For a broader introduction to the atproto, see the [official ATProto glossary](https://atproto.com/guides/glossary). +Key terms used throughout the HappyView documentation. For a broader introduction to the atproto, see the [official atproto glossary](https://atproto.com/guides/glossary). ## atproto terms -**AppView** — A backend service that indexes atproto records and serves them through an API. HappyView is an AppView. See the [ATProto docs](https://atproto.com/guides/glossary#app-view) for more. +**AppView** — A backend service that indexes atproto records and serves them through an API. HappyView is an AppView. See the [atproto docs](https://atproto.com/guides/glossary#app-view) for more. **DID** (Decentralized Identifier) — A persistent, globally unique identifier for an account (e.g. `did:plc:abc123`). @@ -52,11 +52,11 @@ Key terms used throughout the HappyView documentation. For a broader introductio **Permission** — A granular access control right that authorizes a specific action in the admin API. HappyView defines 44 permissions organized by category (e.g. `lexicons:create`, `users:read`). See [Permissions](../guides/permissions.md). -**Permissioned Data** — AT Protocol data that is gated by membership in a space, as opposed to public repo data. Defined by AT Protocol Proposal 0016. +**Permissioned Data** — atproto data that is gated by membership in a space, as opposed to public repo data. Defined by atproto Proposal 0016. **Permission template** — A predefined set of permissions that can be applied when creating a user. Templates are: **Viewer** (read-only access), **Operator** (viewer + backfill and API key management), **Manager** (operator + lexicon, record, spaces, and plugin management), and **Full Access** (all 44 permissions). -**Space** — A container for permissioned data in AT Protocol. Identified by a space DID, type NSID, and space key (skey), forming an `at://` URI with a `space` path segment (e.g. `at://did:plc:abc/space/com.example.forum/main`). +**Space** — A container for permissioned data in atproto. Identified by a space DID, type NSID, and space key (skey), forming an `at://` URI with a `space` path segment (e.g. `at://did:plc:abc/space/com.example.forum/main`). **Space Credential** — A short-lived JWT (`typ: atproto-space-credential+jwt`, ES256, 2-hour TTL) for cross-service read access to space data. Signed by the space's P-256 keypair. Obtained by exchanging a delegation token via `com.atproto.space.getSpaceCredential`. diff --git a/packages/docs/content/docs/sdk/oauth-client-browser/overview.md b/packages/docs/content/docs/sdk/oauth-client-browser/overview.md index 9ac8056..d22f93c 100644 --- a/packages/docs/content/docs/sdk/oauth-client-browser/overview.md +++ b/packages/docs/content/docs/sdk/oauth-client-browser/overview.md @@ -345,7 +345,7 @@ The `redirect_uris` array must include the `redirectUri` your client is configur ## Local development -For local development with ATProto's loopback client ID convention, use `buildLoopbackClientId`: +For local development with atproto's loopback client ID convention, use `buildLoopbackClientId`: ```typescript import { buildLoopbackClientId } from "@happyview/oauth-client-browser"; diff --git a/packages/docs/content/docs/sdk/oauth-client-node/overview.md b/packages/docs/content/docs/sdk/oauth-client-node/overview.md index abd7415..8cbb38c 100644 --- a/packages/docs/content/docs/sdk/oauth-client-node/overview.md +++ b/packages/docs/content/docs/sdk/oauth-client-node/overview.md @@ -2,7 +2,7 @@ title: "Node Client" --- -Server-side OAuth client for authenticating with a HappyView instance using AT Protocol. Built on top of [`@happyview/oauth-client`](../oauth-client/overview.md), matching the API surface of [`@atproto/oauth-client-node`](https://www.npmjs.com/package/@atproto/oauth-client-node). +Server-side OAuth client for authenticating with a HappyView instance using atproto. Built on top of [`@happyview/oauth-client`](../oauth-client/overview.md), matching the API surface of [`@atproto/oauth-client-node`](https://www.npmjs.com/package/@atproto/oauth-client-node). ## Installation diff --git a/packages/docs/content/docs/tutorials/statusphere.md b/packages/docs/content/docs/tutorials/statusphere.md index 3316153..d10b4bd 100644 --- a/packages/docs/content/docs/tutorials/statusphere.md +++ b/packages/docs/content/docs/tutorials/statusphere.md @@ -19,7 +19,7 @@ Statusphere uses a single record type, `xyz.statusphere.status`. Each record has Users can set their status as many times as they want. Each status is a new record in their repository, keyed by a TID (timestamp-based identifier). The most recent record is their "current" status. -For more background on how the app works, see the [ATProto Statusphere guide](https://atproto.com/guides/applications). +For more background on how the app works, see the [atproto Statusphere guide](https://atproto.com/guides/applications). ## Step 1: Add the record lexicon @@ -492,4 +492,4 @@ Everything was done through the dashboard — no server restarts, no config file - [XRPC API](../api-reference/xrpc-api.md): Understand how the generated endpoints behave - [Admin API](../api-reference/admin/admin-api.md): Automate lexicon management via the API - [Statusphere example app](https://github.com/bluesky-social/statusphere-example-app): See the full Statusphere frontend -- [ATProto Statusphere guide](https://atproto.com/guides/applications): How the app works at the protocol level +- [atproto Statusphere guide](https://atproto.com/guides/applications): How the app works at the protocol level -- 2.51.2