Skip to content

Comments

✨ Add Bluesky reply restriction support#812

Merged
0x46616c6b merged 3 commits intomainfrom
feature/bluesky-reply-restriction
Feb 15, 2026
Merged

✨ Add Bluesky reply restriction support#812
0x46616c6b merged 3 commits intomainfrom
feature/bluesky-reply-restriction

Conversation

@0x46616c6b
Copy link
Member

Summary

  • Adds a Reply Restriction dropdown to the Bluesky configuration form, allowing users to control who can reply to their Bluesky posts (Anyone, Followers only, People you follow, Mentioned users only, Nobody)
  • Displays the current reply restriction setting on the Bluesky integration card when connected
  • Makes Handle and Application Password fields optional when the integration is already connected, so users can update settings (e.g. reply restriction) without re-entering credentials

This aligns the admin UI with the backend changes that introduced Thread Gate support for Bluesky posts.


The changes and the PR were generated by OpenCode.

0x46616c6b and others added 3 commits February 15, 2026 19:35
Add a reply restriction dropdown to the Bluesky configuration form,
allowing users to control who can reply to their Bluesky posts
(Anyone, Followers only, People you follow, Mentioned users only, Nobody).

Also makes Handle and Application Password optional when already
connected, so users can update settings without re-entering credentials.

Co-Authored-By: OpenCode <noreply@opencode.ai>
Add tests for all reply restriction labels (following, mentioned, nobody),
Enable button when connected but inactive, and delete error/failure paths.

Co-Authored-By: OpenCode <noreply@opencode.ai>
Refactor AuthContext, FeatureContext, and MessageFormCounter to comply
with react-hooks/set-state-in-effect, react-hooks/refs, and
react-hooks/preserve-manual-memoization rules from eslint-plugin-react-hooks v7.

- AuthContext: Replace useEffect/useRef-based error reset with derived
  state pattern; consolidate state into single useState with lazy
  initializer
- FeatureContext: Move setState calls from effect body into async
  callbacks; consolidate into single state object
- MessageFormCounter: Replace useState+useEffect with useMemo for
  derived color value

Co-Authored-By: OpenCode <noreply@opencode.ai>
@sonarqubecloud
Copy link

@0x46616c6b 0x46616c6b marked this pull request as ready for review February 15, 2026 18:53
@0x46616c6b 0x46616c6b merged commit 0be0b16 into main Feb 15, 2026
9 checks passed
@0x46616c6b 0x46616c6b deleted the feature/bluesky-reply-restriction branch February 15, 2026 18:54
@0x46616c6b 0x46616c6b added the enhancement New feature or request label Feb 18, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant