Editing Feed generator (section)

== Architecture ==
The feed generator architecture follows a simple design pattern, aiming to create a clean division of responsibilities between content selection and content delivery.

Each feed algorithm is declared as a record in the repository of its creator, typically using the <code>app.bsky.feed.generator</code> [[collection]]. This declaration includes metadata about the feed (name, description, avatar) and points to the service that hosts. the algorithm. The feed generator service itself is identified by a [[Decentralized Identifier (DID)|decentralized identifier (DID)]] to allow for secure communication and authentication.

When a user requests a feed, their PDS resolves the feed's [[AT URI]] to find the feed generator's service endpoint. The PDS then sends a <code>getFeedSkeleton</code> request to this endpoint.

Requests to feed generators are authenticated with a [[wikipedia:JSON_Web_Token|JWT]] signed by the user's repository signing key, allowing the generator to verify the user's identity. The feed generator then returns a "skeleton" of the feed - a list of post URIs with optional ranking signals or metadata. The user's PDS hydrates this ekeleton with full post content, user information, and engagement metrics before returning it to the client application.

[[Category:Network architecture]]
[[Category:Content curation]]
[[Category:Opinionated services]]