fix: inbound Block should persist to BlocklistRepository #1

New Issue

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

GKaszewski commented

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

Problem

activities/block.rs receive() removes follower/following relationships but doesn't call blocklist_repo.add_blocked_actor(). Consumers can't tell that a remote actor blocked a local user — only that the follow was removed.

Suggested fix

In BlockActivity::receive(), after removing follows, call:

data.blocklist_repo.add_blocked_actor(local_user_id, self.actor.inner().as_str()).await?;

This lets consumers show "blocked by this actor" in UI and prevent re-follow attempts.

## Problem `activities/block.rs` `receive()` removes follower/following relationships but doesn't call `blocklist_repo.add_blocked_actor()`. Consumers can't tell that a remote actor blocked a local user — only that the follow was removed. ## Suggested fix In `BlockActivity::receive()`, after removing follows, call: ```rust data.blocklist_repo.add_blocked_actor(local_user_id, self.actor.inner().as_str()).await?; ``` This lets consumers show "blocked by this actor" in UI and prevent re-follow attempts.

GKaszewski referenced this issue from a commit

2026-05-30 00:48:45 +00:00

fix: persist inbound Block to blocklist, clear on Undo(Block)

GKaszewski closed this issue

2026-05-30 00:48:45 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: GKaszewski/k-ap#1