Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rate-limit chiron #35

Open
dehnert opened this issue Jul 10, 2014 · 1 comment
Open

Rate-limit chiron #35

dehnert opened this issue Jul 10, 2014 · 1 comment

Comments

@dehnert
Copy link
Member

dehnert commented Jul 10, 2014

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.

@dehnert
Copy link
Member Author

dehnert commented Jul 10, 2014

jhawk suggests when the rate-limit triggers, chiron could move to the .d. I'm dubious that talking on sipb.d would really make people much happier than sipb (and jhawk is also unsure), but it's a possible experiment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant