Skip to content

Rate-limit chiron #35

@dehnert

Description

@dehnert

Some kind of rate-limit to reduce people's tendency to play with chiron seems desirable. It's not clear how exactly this should work, since I think pasting a bunch of tickets on -c debathena is pretty common. Some possibilities:

  • limit only certain fetchers/matchers (Debathena #xxx is probably pretty safe, but XXX Airport is more likely to get played with)
  • limit only certain classes (I think people tend to behave better on -c debathena than -c sipb)
  • limit messages, not tickets -- bulk lookups tend to be one zephyr, and playing (at least when annoying) tends to be spread out (though I'm less sure this is a good enough distinguisher)

To some degree, Chiron-#18 is a substitute for this.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions