[Feature Request]: Add `chat.bsky.convo` reply and group conversation support

Open
#320 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
43/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Quiet
Tech stack
swift
Domain
api

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

new feature
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
Dominant language
Swift
Stars
226
Forks
40
Avg merge
2h 56m
Merged PRs (30d)
3

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from MasterJ93/ATProtoKit

All issues in MasterJ93/ATProtoKit

Similar issues

More Swift issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.