Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • T torflow
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Network Health
  • torflow
  • Issues
  • #2127
Closed
Open
Created Oct 28, 2010 by Roger Dingledine@armaOwner

Stop the false positives to flynn

Our original idea for the flynn list was to only send mail when we're convinced it's a bad exit.

Then we changed it so we send mail several times a day, for exits that seem to fail to connect a few times to some arbitrary site we found via google.

Either these are all badexits, in which case we should nuke them all, or they're false positives, in which case we should stop sending the mail.

Perhaps the compromise is to only send mail once they've been clearly broken for a week?

We should make it so we send the mail when we think we should badexit it, and don't send the mail otherwise.

(Or we should make a separate mailing list for it to send its output, if you want to look at it, but Linus / I / Chris Walker probably don't.)

Assignee
Assign to
Time tracking