[Feature Request]: Add `chat.bsky.group` namespace and group join-link embed
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 52/100
Research direction
Start by reading the existing chat lexicon models under Sources/ATProtoKit/Models/Lexicons/chat.bsky/ and API methods under Sources/ATProtoKit/APIReference/ChatBskyAPI/ to follow their conventions. Then compare the listed missing lexicons with the upstream lexicon references and add the typed group wrappers and join-link embed. Done when the listed group operations and embed are represented in the typed pipeline with api.bsky.chat routing.
Written by the indexing model from the issue text.
Description
Summary
The upstream lexicon now ships a full chat.bsky.group.* namespace (group lifecycle, membership, join links, join requests) plus a chat.bsky.embed.joinLink embed object. None of these are reflected in ATProtoKit, so group conversation management is unreachable through the typed pipeline.
Pain points
The entire group surface (lifecycle, membership, join links, join requests, and the messageInput.embed join-link) has to be hand-built on raw XRPC, re-implementing the api.bsky.chat routing and auth plumbing that ATProtoBlueskyChat already handles for every other chat call.
Considered Alternatives
Raw XRPC for the entire group surface — loses typed pipeline, isRelatedToBskyChat host routing, and forces every consumer to repeat the same auth plumbing.
Is this a breaking change?
No
Library Examples
N/A
Additional Context
Missing lexicons
| Lexicon | Suggested wrapper |
|---|---|
chat.bsky.embed.joinLink |
ChatBskyLexicon.Embed.JoinLink embed object, selectable in the sendMessage messageInput.embed union |
chat.bsky.group.addMembers |
addMembers(to:memberDIDs:) |
chat.bsky.group.approveJoinRequest |
approveJoinRequest(for:requesterDID:) |
chat.bsky.group.createGroup |
createGroup(name:memberDIDs:memberLimit:) |
chat.bsky.group.createJoinLink |
createJoinLink(for:) |
chat.bsky.group.defs |
types only |
chat.bsky.group.disableJoinLink |
disableJoinLink(for:) |
chat.bsky.group.editGroup |
editGroup(by:name:) |
chat.bsky.group.editJoinLink |
editJoinLink(for:expiresAt:) |
chat.bsky.group.enableJoinLink |
enableJoinLink(for:) |
chat.bsky.group.getJoinLinkPreviews |
getJoinLinkPreviews(for:) |
chat.bsky.group.listJoinRequests |
listJoinRequests(for:limit:cursor:) |
chat.bsky.group.listMutualGroups |
listMutualGroups(with:limit:cursor:) |
chat.bsky.group.rejectJoinRequest |
rejectJoinRequest(for:requesterDID:) |
chat.bsky.group.removeMembers |
removeMembers(from:memberDIDs:) |
chat.bsky.group.requestJoin |
requestJoin(by:) |
chat.bsky.group.updateJoinRequestsRead |
updateJoinRequestsRead(for:) |
chat.bsky.group.withdrawJoinRequest |
withdrawJoinRequest(by:) |
Wrappers follow the existing ATProtoBlueskyChat convention (method name mirrors the lexicon's final segment, no artificial Group prefix — matching getConversation, listConversations). All sit on api.bsky.chat and require isRelatedToBskyChat: true routing, and the group namespace maps to ChatBskyLexicon.Group.
Cross-reference
- The convo-side discriminator (
convoView.kind→#groupConvo) and the 4 convo-level endpoints (getConvoMembers,listConvoRequests,lockConvo,unlockConvo) are tracked in a separate feature request #320.
References
- Lexicon root: https://github.com/bluesky-social/atproto/tree/main/lexicons/chat/bsky/group
chat.bsky.embed.joinLink: https://github.com/bluesky-social/atproto/blob/main/lexicons/chat/bsky/embed/joinLink.json- Affected directories:
Sources/ATProtoKit/Models/Lexicons/chat.bsky/Group/(new),Sources/ATProtoKit/APIReference/ChatBskyAPI/(new method files)
- 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