Skip to content

Updated activitypub Bluesky sharing enablement flow#21

Open
tomerqodo wants to merge 6 commits intosentry_combined_20260121_augment_sentry_coderabbit_1_base_updated_activitypub_bluesky_sharing_enablement_flow_pr244from
sentry_combined_20260121_augment_sentry_coderabbit_1_head_updated_activitypub_bluesky_sharing_enablement_flow_pr244
Open

Updated activitypub Bluesky sharing enablement flow#21
tomerqodo wants to merge 6 commits intosentry_combined_20260121_augment_sentry_coderabbit_1_base_updated_activitypub_bluesky_sharing_enablement_flow_pr244from
sentry_combined_20260121_augment_sentry_coderabbit_1_head_updated_activitypub_bluesky_sharing_enablement_flow_pr244

Conversation

@tomerqodo
Copy link
Copy Markdown

Benchmark PR from qodo-benchmark#244

mike182uk and others added 6 commits January 21, 2026 15:51
ref TryGhost/ActivityPub#1377

We updated the backend implementation of the Bluesky sharing enablement process
to include a confirmation step in which the client would prompt the backend
to check what handle has been assigned to the Bluesky account generated by
Bridgy Fed - This circumvents the need to for us to compute the handle manually
and potentially getting it wrong if we compute it in a different way to Bridgy
Fed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants