[Feature Request]: Add `chat.bsky.group` namespace and group join-link embed

Open
#321 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
52/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Quiet
Tech stack
swift
Domain
api

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

new feature
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
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.