This request might be a bit more tricky to implement, feel free to decline.
Is your feature request related to a problem? Please describe.
A persistent spammer can trivially generate a new key pair to route around any
per-sender block or rate limit once it's been identified, this is an ongoing,
deliberate spam campaign, not a one-off, so identity rotation is a realistic
adaptation to expect.
Describe the solution you'd like
When a message arrives from a senderKeyPrefix never seen before (no prior
message/contact history locally), apply stricter handling — e.g. a lower
rate-limit threshold or a short delay before it's shown normally rather than
treating it identically to an established contact from the first message.
Describe alternatives you've considered
Relying on manual blocking once a new identity starts spamming — doesn't help
against the gap between "first message from a new key" and "user notices and
blocks it."
This request might be a bit more tricky to implement, feel free to decline.
Is your feature request related to a problem? Please describe.
A persistent spammer can trivially generate a new key pair to route around any
per-sender block or rate limit once it's been identified, this is an ongoing,
deliberate spam campaign, not a one-off, so identity rotation is a realistic
adaptation to expect.
Describe the solution you'd like
When a message arrives from a
senderKeyPrefixnever seen before (no priormessage/contact history locally), apply stricter handling — e.g. a lower
rate-limit threshold or a short delay before it's shown normally rather than
treating it identically to an established contact from the first message.
Describe alternatives you've considered
Relying on manual blocking once a new identity starts spamming — doesn't help
against the gap between "first message from a new key" and "user notices and
blocks it."