Additional Notes and Considerations

Oct 13, 2025 by recoveryshake.com 122 views

What is the Objective?

The objective of this working group is to create a feed lexicon that expands on existing app.bsky.feed.* types and methods to be used by applications, tools, and libraries as a replacement. This working group is expected to produce documentation that supports feed definition, subscription, and management, reference code to consume feeds, and reference code to produce feeds.

Who is the Responsible Individual for the Working Group?

The responsible individual for this working group is @ngerakines.

Additional Notes and Considerations

Feeds are an essential part of AT Protocol, both from a technical point of view and as a critical feature of user autonomy and empowerment. In their current form, there are several significant limitations that make it difficult to use feeds beyond posts and outside of the bsky.app AppView.

Limitations of Current Feeds

Feeds are limited to app.bsky.feed.post record types: This limitation restricts the types of feeds that can be created and used.
Feeds do not have parameters or configuration: This limitation prevents features like alternative views (i.e., sort by popular vs new) or control mechanisms.

Existing Notes

These are some notes that were used to work through the idea.

Updated Feed System Diagram

In the above diagram, the updated feed system could be updated to include the same existing discovery pattern, but with several key additions.

Feed discovery: The AppView would retrieve a feed definition record that includes additional configuration options. This definition would include parameters (args) that can be set at query time or in a user configuration record. It would also include the types that are returned by the feed, giving the AppView time to perform any resolution needed or filter/reject the feed as not supported.

{
  "did": "did:web:feeds.smokesignal.events",
  "$type": "app.bsky.feed.generator",
  "createdAt": "2025-03-13T13:10:30.000001+00:00",
  "description": "Upcoming music festivals and events in Ohio.",
  "displayName": "Ohio Music Festivals",
  "recordTypes": ["community.lexicon.calendar.event"]
  "args": {
    "sort": {
      "description": "The sort order for the feed",
      "allowedValues": ["popular", "upcoming"],
      "defaultValue": "upcoming",
      "usage": ["query", "record"]
    },
    "location": {
      "description": "The city or region you want prioritized in the feed.",
      "usage": ["record"]
    }
  }
}

Identities subscribing to the feed: Identities could create a record that contains their default configuration and arguments.

{
  "$type": "community.lexicon.feed.subscription",
  "createdAt": "2025-03-13T13:10:30.000001+00:00",
  "feed": "at://smokesignal.events/app.bsky.feed.generator/ohio-festivals",
  "args": {
    "sort": "upcoming",
    "location": "Dayton, Ohio"
  }
}

AppViews querying feeds on behalf of users: Arguments can be provided as described in the feed definition.

GET /xrpc/community.lexicon.feed.getSkeleton?sort=upcoming&feed=at://smokesignal.events/app.bsky.feed.generator/ohio-festivals

Feed skeleton returned: A list of strongRef records where the subject is of one of the types listed in the feed definition. Any applicable args are also returned.

{
  "args": {"sort": "upcoming"},
  "records": [
      {
          "$type": "com.atproto.repo.strongRef",
          "cid": "bafy...3n4i",
          "uri": "at://did:plc:un..um/community.lexicon.calendar.event/3jzfcijpj2z2a"
      },
      {
          "$type": "com.atproto.repo.strongRef",
          "cid": "bafy...3n4i",
          "uri": "at://did:plc:un..um/community.lexicon.calendar.event/3jzfcijpj2z2b"
      }
  ],
  "cursor": "cGFnZT0xCg=="
}

Working Group Requirements

This working group would use a public-facing read-only repository for this work: lexicon-community/wg-exemplary-murrelet.

Repository Requirements

Public-facing: The repository should be publicly accessible to ensure transparency and collaboration.
Read-only: The repository should be read-only to prevent accidental changes or modifications.
Version control: The repository should use a version control system (e.g., Git) to track changes and maintain a history of updates.

Working Group Deliverables

The working group is expected to produce the following deliverables:

Documentation: Documentation that supports feed definition, subscription, and management.
Reference code: Reference code to consume feeds and produce feeds.
Feed lexicon: A feed lexicon that expands on existing app.bsky.feed.* types and methods.

Working Group Timeline

The working group is expected to complete its work within a specified timeline. The timeline should include milestones and deadlines for each deliverable.

Working Group Communication

The working group should maintain open communication channels to ensure that all members are informed and engaged throughout the process. This can include regular meetings, email updates, and issue tracking.

Working Group Governance

The working group should establish a governance structure to ensure that decisions are made in a fair and transparent manner. This can include a leader or chairperson, a decision-making process, and a conflict resolution mechanism.

Working Group Membership

The working group should be open to all interested parties, including developers, designers, and stakeholders. Membership should be based on a clear set of criteria, such as expertise, experience, and commitment to the project.

Working Group Roles and Responsibilities

Each member of the working group should have a clear understanding of their roles and responsibilities. This can include tasks such as:

Documentation: Writing and maintaining documentation.
Code review: Reviewing and testing code.
Testing: Testing and validating deliverables.
Communication: Maintaining open communication channels.
Governance: Participating in decision-making and conflict resolution.

By following these guidelines, the working group can ensure that its work is completed efficiently, effectively, and in a manner that meets the needs of all stakeholders.

What is the objective of the Exemplary Murrelet working group?

The objective of the Exemplary Murrelet working group is to create a feed lexicon that expands on existing app.bsky.feed.* types and methods to be used by applications, tools, and libraries as a replacement. This working group is expected to produce documentation that supports feed definition, subscription, and management, reference code to consume feeds, and reference code to produce feeds.

Who is responsible for the Exemplary Murrelet working group?

The responsible individual for the Exemplary Murrelet working group is @ngerakines.

What are the limitations of current feeds?

Current feeds are limited to app.bsky.feed.post record types and do not have parameters or configuration, which restricts features like alternative views (i.e., sort by popular vs new) or control mechanisms.

What is the proposed updated feed system?

The proposed updated feed system includes the same existing discovery pattern, but with several key additions:

Feed discovery: The AppView would retrieve a feed definition record that includes additional configuration options.
Identities subscribing to the feed: Identities could create a record that contains their default configuration and arguments.
AppViews querying feeds on behalf of users: Arguments can be provided as described in the feed definition.
Feed skeleton returned: A list of strongRef records where the subject is of one of the types listed in the feed definition. Any applicable args are also returned.

What is the expected timeline for the working group?

The working group is expected to complete its work within a specified timeline, which includes milestones and deadlines for each deliverable.

How will the working group communicate?

The working group will maintain open communication channels to ensure that all members are informed and engaged throughout the process. This can include regular meetings, email updates, and issue tracking.

What is the governance structure of the working group?

The working group will establish a governance structure to ensure that decisions are made in a fair and transparent manner. This can include a leader or chairperson, a decision-making process, and a conflict resolution mechanism.

Who can join the working group?

The working group is open to all interested parties, including developers, designers, and stakeholders. Membership is based on a clear set of criteria, such as expertise, experience, and commitment to the project.

What are the roles and responsibilities of working group members?

Each member of the working group has a clear understanding of their roles and responsibilities, which can include tasks such as:

Documentation: Writing and maintaining documentation.
Code review: Reviewing and testing code.
Testing: Testing and validating deliverables.
Communication: Maintaining open communication channels.
Governance: Participating in decision-making and conflict resolution.

What is the expected outcome of the working group?

The working group is expected to produce the following deliverables:

Documentation: Documentation that supports feed definition, subscription, and management.
Reference code: Reference code to consume feeds and produce feeds.
Feed lexicon: A feed lexicon that expands on existing app.bsky.feed.* types and methods.

How will the working group ensure that its work is completed efficiently and effectively?

The working group will use a public-facing read-only repository for this work, which will track changes and maintain a history of updates. The working group will also establish a clear set of criteria for membership and roles and responsibilities to ensure that all members are engaged and committed to the project.

What is the expected impact of the working group's work?

The working group's work is expected to have a significant impact on the development of feeds in AT Protocol, enabling the creation of more complex and dynamic feeds that can be used by applications, tools, and libraries.