fix: inbound Block activity doesn't persist block record #15

New Issue

GKaszewski · 2026-05-29T09:25:37Z

GKaszewski commented

2026-05-29 09:25:37 +00:00

Problem

When a remote actor sends a Block activity targeting a local user, k-ap's handler removes follower/following relationships (correct), but does NOT call blocklist_repo.add_blocked_actor(). So we don't record that the remote actor blocked us.

Practical effect is correct (they can't receive our posts after follows are removed), but we can't show "this actor blocked you" in the UI.

Fix

Requires k-ap change — the Block activity handler (activities/block.rs) should call blocklist_repo.add_blocked_actor() on the local user's behalf. See companion issue in k-ap repo.

Blocked by: k-ap update.

## Problem When a remote actor sends a `Block` activity targeting a local user, k-ap's handler removes follower/following relationships (correct), but does NOT call `blocklist_repo.add_blocked_actor()`. So we don't record that the remote actor blocked us. Practical effect is correct (they can't receive our posts after follows are removed), but we can't show "this actor blocked you" in the UI. ## Fix Requires k-ap change — the `Block` activity handler (`activities/block.rs`) should call `blocklist_repo.add_blocked_actor()` on the local user's behalf. See companion issue in k-ap repo. Blocked by: k-ap update.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: GKaszewski/thoughts#15