Skip to content

backend: mitigate spamming events #101

Description

@r0liveir

Context

Some websocket events (such as inserting/adding to GSL queue) can be spammed by users, broadcasting state a lot.

What to do

Some ideas:

  • We can return an error to the offender when the event cannot be processed
  • Follow idempotency principle, make event be "successful", but dont broadcast state
  • Use a rate limiter perhaps?

Expected Behaviour

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    BackendBack of the end

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions