[Feature Request]: Add `chat.bsky.convo` reply and group conversation support
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 43/100
Research direction
Start with Sources/ATProtoKit/Models/Lexicons/chat.bsky/Convo/ChatBskyConvoDefs.swift and the wrappers under Sources/ATProtoKit/APIReference/ChatBskyAPI/; compare their existing acceptConvo and muteConvo patterns with the referenced chat.bsky.convo lexicons. Add the listed reply and group types and fields, then expose the four requested endpoints with api.bsky.chat routing. Done when replies, group metadata, and all four operations are available through ATProtoBlueskyChat.
Written by the indexing model from the issue text.
Description
Summary
chat.bsky.convo upstream has been extended with two cross-cutting additions that are not yet reflected in the typed models or wrappers: message-level reply (replyTo on both input and view) and group conversations (convoView.kind union with #groupConvo, plus four new XRPC endpoints). Currently the SDK exposes neither, so the entire reply / group surface is unreachable through ATProtoBlueskyChat.
Pain points
The reply / group definitions are absent from the typed models and wrappers, so the whole surface is unreachable through ATProtoBlueskyChat: typed quote-reply on sendMessage is impossible, an incoming reply's parent is silently dropped on decode (no field-level .unknown fallback), a group is indistinguishable from a 1:1 DM with its metadata unreachable, and the group / lock endpoints require raw XRPC that re-implements the api.bsky.chat host routing / auth ATProtoBlueskyChat already provides. See Additional Context for the specific undefined types, fields, and wrappers.
Considered Alternatives
Raw XRPC for the entire chat surface (loses typed pipeline and the isRelatedToBskyChat host routing) — only viable per-client and brittle.
Is this a breaking change?
No
Library Examples
N/A
Additional Context
Missing types
| Lexicon | Suggested type |
|---|---|
chat.bsky.convo.defs#replyRef |
ReplyReferenceDefinition — messageID: String (messageId) |
chat.bsky.convo.defs#messageBeforeUserJoinedGroupView |
MessageBeforeUserJoinedGroupViewDefinition — per lexicon |
chat.bsky.convo.defs#groupConvo |
GroupConvoDefinition — name: String?, createdAt: Date, lockStatus: String, lockStatusModerationOverride: String?, memberCount: Int, memberLimit: Int, joinLink: String?, joinRequestCount: Int, unreadJoinRequestCount: Int |
Missing fields on existing types
| Lexicon | Suggested field |
|---|---|
chat.bsky.convo.defs#messageInput |
replyTo: ReplyReferenceDefinition? |
chat.bsky.convo.defs#messageView |
replyTo: ReplyToUnion? (messageView | deletedMessageView | messageBeforeUserJoinedGroupView) |
chat.bsky.convo.defs#convoView |
kind: KindUnion? (groupConvo) |
Missing wrappers
| Lexicon | Suggested method |
|---|---|
chat.bsky.convo.getConvoMembers |
getConversationMembers(from:limit:cursor:) |
chat.bsky.convo.listConvoRequests |
listConversationRequests(limit:cursor:) |
chat.bsky.convo.lockConvo |
lockConversation(by:) |
chat.bsky.convo.unlockConvo |
unlockConversation(by:) |
All four sit on api.bsky.chat, mirror the existing acceptConvo / muteConvo shape, and require isRelatedToBskyChat: true routing.
References
- Lexicon root: https://github.com/bluesky-social/atproto/tree/main/lexicons/chat/bsky/convo
defs.json: https://github.com/bluesky-social/atproto/blob/main/lexicons/chat/bsky/convo/defs.json- Affected file:
Sources/ATProtoKit/Models/Lexicons/chat.bsky/Convo/ChatBskyConvoDefs.swift - Affected wrapper namespace:
Sources/ATProtoKit/APIReference/ChatBskyAPI/
- Dominant language
- Swift
- Stars
- 226
- Forks
- 40
- Avg merge
- 2h 56m
- Merged PRs (30d)
- 3
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from MasterJ93/ATProtoKit
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
MasterJ93/ATProtoKit#354 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
MasterJ93/ATProtoKit#352 ·
-
[Feature Enhancement]: Add `sort` parameter to `getQuotes`Possibly taken A pull request linked to this issue is open or already merged. Openenhancement
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
MasterJ93/ATProtoKit#346 · 1 comment ·
-
[Feature Request]: Add `app.bsky.actor.contentVisibilityDeclaration` record supportPossibly taken A pull request linked to this issue is open or already merged. Opennew feature
Difficulty 3/5 1-2 days Newbie friendliness 68/100
MasterJ93/ATProtoKit#350 · 4 comments ·
-
[Feature Enhancement]: Support scoped mutes (`onlyReposts` / `onlyQuoteposts`) in `muteActor`Possibly taken A pull request linked to this issue is open or already merged. Openenhancement
Difficulty 3/5 1-2 days Newbie friendliness 72/100
MasterJ93/ATProtoKit#348 · 1 comment ·
All issues in MasterJ93/ATProtoKit
Similar issues
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
good first issue help wanted testing
Difficulty 1/5 Under an hour Newbie friendliness 78/100
-
area:cli documentation good first issue priority:low
Difficulty 1/5 Under an hour Newbie friendliness 94/100
isaaclins/freesnitch#430 ·
Maintainers usually reply within 1 day
-
enhancement help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
heysidhant/appvanish#4 ·
-
bug priority:low status:queued
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day