binwiederhier ac9c6b2bac Keep the UnifiedPush rate visitors in the topic service, derive the limiter key at push time ...

The server uses the topic package instead of the limit service for the rate
visitors: a subscribe sets the rate visitor (user ID and masked IP), a poll,
a stream close and the manager's keepalive record subscriber activity, a
refused push notes an unknown topic (insert-only). The limiter key is derived
on every push from the rate visitor's current tier (refreshed in the
background every minute, never on the publish path), so a downgrade or a
deleted account charges the IP. Before a 404 for an abandoned topic the row
is read from the database. The Matrix gateway rejects the pushkey under the
same 7-day rule; its 12 h per-node rule is gone.

2026-10-31 14:05:37 +00:00

..

key_test.go

Keep the UnifiedPush rate visitors in the topic service, derive the limiter key at push time

2026-10-31 14:05:37 +00:00

key.go

Keep the UnifiedPush rate visitors in the topic service, derive the limiter key at push time

2026-10-31 14:05:37 +00:00

limits_test.go

One field per line in multi-field struct literals

2026-10-28 21:35:06 +00:00

limits.go

One limiter model in package limit, replacing the three limiter types in the visitor

2026-10-25 15:50:03 +00:00

types.go

One limiter model in package limit, replacing the three limiter types in the visitor

2026-10-25 15:50:03 +00:00