Add actor social media account settings #182

Closed
opened 2026-06-21 18:12:37 -05:00 by erik · 4 comments
Owner

Goal

Add a settings section for configuring social media accounts associated with the website actor.

Requirements

  • Add a settings section for actor social media accounts.
  • Allow the website actor’s social media account details to be configured.
  • Follow existing settings patterns in the project.
  • Wait until the actor settings data model bug is resolved so actor social accounts are built on the corrected actor/settings model.

Acceptance criteria

  • A settings section exists for actor social media accounts.
  • Social media account configuration is saved and available for the website actor.
  • The implementation follows existing project conventions.

Dependencies

  • task-bf6945b5
## Goal Add a settings section for configuring social media accounts associated with the website actor. ## Requirements - Add a settings section for actor social media accounts. - Allow the website actor’s social media account details to be configured. - Follow existing settings patterns in the project. - Wait until the actor settings data model bug is resolved so actor social accounts are built on the corrected actor/settings model. ## Acceptance criteria - [ ] A settings section exists for actor social media accounts. - [ ] Social media account configuration is saved and available for the website actor. - [ ] The implementation follows existing project conventions. ## Dependencies - task-bf6945b5
Author
Owner

Synced from todu comment by @todu on 2026-06-21T23:26:18.302Z

Moved to waiting because actor social account settings should not be built on the current actor settings data model. Blocking dependency: task-bf6945b5 (Fix actor settings data model).

_Synced from todu comment by @todu on 2026-06-21T23:26:18.302Z_ Moved to waiting because actor social account settings should not be built on the current actor settings data model. Blocking dependency: `task-bf6945b5` (`Fix actor settings data model`).
Author
Owner

Synced from todu comment by @todu on 2026-06-22T03:50:24.401Z

Review update

  • PR: #185 is open and CI passed.
  • Result: approved with no blocking issues or warnings.
  • Verified: local ./scripts/pre-pr.sh passed and Forgejo Actions task #255 passed for commit 8d96a27.
  • Follow-up: waiting for explicit human merge approval.
_Synced from todu comment by @todu on 2026-06-22T03:50:24.401Z_ ### Review update - PR: #185 is open and CI passed. - Result: approved with no blocking issues or warnings. - Verified: local `./scripts/pre-pr.sh` passed and Forgejo Actions task #255 passed for commit `8d96a27`. - Follow-up: waiting for explicit human merge approval.
erik 2026-06-21 23:36:47 -05:00
Author
Owner

Synced from todu comment by @todu on 2026-06-22T04:35:20.248Z

Closing summary

Task is ready to close based on PR #185 merged to main (cda2b41, implementation commit eddee62).

Acceptance criteria evidence:

  • Settings UI includes a Social accounts section on /settings/actor with account label, URL, kind, protocol fields, plus add/remove row controls in template/site/src/templates/settings-activitypub.ts.
  • Social account configuration is persisted through POST /settings/actor: template/site/src/routes/settings.ts validates form rows and calls replaceActivityPubActorAccounts; migration 024_activitypub_actor_accounts.sql adds normalized storage; template/site/src/federation/actor-accounts.ts provides list/replace/validation behavior.
  • Saved accounts are available for the website actor in the ActivityPub actor document as profile attachments via template/site/src/federation/routes.ts, and on public pages through readLocalPostAuthor/ActorAccountSummary in home.ts and public.tsx.
  • Tests cover UI rendering, saving, validation, storage replacement, ActivityPub actor document attachment output, and public homepage account links.
  • PR #185 landed after dependency PR #184/task-bf6945b5, and review comments recorded local ./scripts/pre-pr.sh plus Forgejo Actions task #256 passing before merge.

Result: READY; task closed.

_Synced from todu comment by @todu on 2026-06-22T04:35:20.248Z_ ### Closing summary Task is ready to close based on PR #185 merged to `main` (`cda2b41`, implementation commit `eddee62`). Acceptance criteria evidence: - Settings UI includes a `Social accounts` section on `/settings/actor` with account label, URL, kind, protocol fields, plus add/remove row controls in `template/site/src/templates/settings-activitypub.ts`. - Social account configuration is persisted through `POST /settings/actor`: `template/site/src/routes/settings.ts` validates form rows and calls `replaceActivityPubActorAccounts`; migration `024_activitypub_actor_accounts.sql` adds normalized storage; `template/site/src/federation/actor-accounts.ts` provides list/replace/validation behavior. - Saved accounts are available for the website actor in the ActivityPub actor document as profile attachments via `template/site/src/federation/routes.ts`, and on public pages through `readLocalPostAuthor`/`ActorAccountSummary` in `home.ts` and `public.tsx`. - Tests cover UI rendering, saving, validation, storage replacement, ActivityPub actor document attachment output, and public homepage account links. - PR #185 landed after dependency PR #184/task-bf6945b5, and review comments recorded local `./scripts/pre-pr.sh` plus Forgejo Actions task #256 passing before merge. Result: READY; task closed.
Author
Owner

Synced from todu comment by @todu on 2026-06-22T04:32:43.561Z

Review update

  • PR: #185 was amended after requested changes.
  • Result: approved with no blocking issues or warnings.
  • Verified: local ./scripts/pre-pr.sh passed and Forgejo Actions task #256 passed for commit eddee62.
  • Follow-up: waiting for explicit human merge approval.
_Synced from todu comment by @todu on 2026-06-22T04:32:43.561Z_ ### Review update - PR: #185 was amended after requested changes. - Result: approved with no blocking issues or warnings. - Verified: local `./scripts/pre-pr.sh` passed and Forgejo Actions task #256 passed for commit `eddee62`. - Follow-up: waiting for explicit human merge approval.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
erik/slugkit#182
No description provided.