Send actor updates with keyed Fedify actor object #42
No reviewers
Labels
No labels
activitypub
actor
admin
ai-safety
article
articles
atproto
bug
cli
configuration
content
dev-environment
docker
enhancement
feature
federation
fediverse
forgejo
garage
health
how-to
logging
markdown
mastodon
media
navigation
opengraph
passkeys
preview
priority:medium
production
release
rendering
s3
settings
setup
status:active
status:done
status:inprogress
technical
webauthn
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
erik/slugkit.com!42
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "task-d213c262-revert-and-fix-actor-update"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
publicKey/#main-keyand Fedify multikeyassertionMethod/#multikey-1key material#multikey-1pathVerification
Task: task-d213c262
After merge/release/deploy, publish a test note first to verify normal fanout recovers, then test actor avatar update delivery.
Review summary
Approved. This fixes the PR #39 problem by removing the separate partial actor object construction path and routing actor Update payload construction through the same helper used by the Fedify actor dispatcher. The actor Update payload now includes both legacy
publicKey/#main-keyand FedifyassertionMethod/#multikey-1key material.Acceptance criteria coverage
publicKeyPem/#main-key.publicKeyMultibase/#multikey-1.#multikey-1path.Verification
npm run typechecknpm test -- --run src/routes/__tests__/admin-activitypub.test.ts src/federation/__tests__/routes.test.ts src/federation/__tests__/delivery.test.tsnpm testnpm run buildRisk / deploy note
Production Mastodon may have a bad cached copy of the actor/key state from the previous broken update attempts. After deploying this fix, first verify normal note fanout. If Mastodon still rejects with
Public key not found, force a remote actor refetch/re-follow flow before concluding the new payload is still bad.Blocking issues
None.
Verdict
Approved.