feat: inbound/outbound rate limiting #7

New Issue

GKaszewski · 2026-05-30T01:22:31Z

GKaszewski commented

2026-05-30 01:22:31 +00:00

Currently ApObjectHandler callbacks receive raw serde_json::Value — consumers parse activity-specific fields themselves. There's no structured way to handle content types beyond Note (polls, questions, emoji reactions, events, etc.).

Consider a registry or trait-based extension system where consumers can register handlers for specific AP object types without modifying k-ap itself.

Closed: Rate limiting is an infrastructure concern, not a protocol adapter responsibility. Consumers own the HTTP layer (axum router) and can add tower middleware or reverse proxy rate limiting without k-ap needing to own counters, algorithms, or per-domain state.

Currently `ApObjectHandler` callbacks receive raw `serde_json::Value` — consumers parse activity-specific fields themselves. There's no structured way to handle content types beyond Note (polls, questions, emoji reactions, events, etc.). Consider a registry or trait-based extension system where consumers can register handlers for specific AP object types without modifying k-ap itself. **Closed:** Rate limiting is an infrastructure concern, not a protocol adapter responsibility. Consumers own the HTTP layer (axum router) and can add tower middleware or reverse proxy rate limiting without k-ap needing to own counters, algorithms, or per-domain state.

GKaszewski closed this issue

2026-07-11 08:28:07 +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#7