Improve or replace TorFlow

TorFlow is not so hard to game; we should make it harder to game, or replace it with something harder to game. Aaron, Rob, and Paul have some interesting preliminary designs for a Big Thing Indeed, but last I heard it still needed quite a bit of work. So is our best option improving the TorFlow we have today?

added SponsorZ in Legacy / Trac component::core tor/torflow in Legacy / Trac needs-proposal in Legacy / Trac parent::13630 in Legacy / Trac priority::medium in Legacy / Trac resolution::duplicate in Legacy / Trac security in Legacy / Trac severity::normal in Legacy / Trac status::closed in Legacy / Trac type::enhancement in Legacy / Trac labels

This ticket is tagged high priority and SponsorZ, but it looks like progress stalled over a year ago. Is this still a thing that needs funding?

Trac:
Reviewer: N/A to N/A
Severity: N/A to Normal
Sponsor: N/A to N/A
Cc: N/A to cass

Nowadays TorFlow is only used by the bandwidth authorities. As I understand it the bandwidth scanner is being reimplemented by Donncha...

https://github.com/TheTorProject/bwscanner

If the question was 'does bwauth work need funding?' then I suspect the answer is yes, but not TorFlow.

Let's put these all in the one place

Trac:
Parent: N/A to legacy/trac#13630 (moved)

Priorities and Severities in torflow are meaningless, setting them all to Medium/Normal.

Trac:
Priority: High to Medium

aagbsn was the default owner, unassigning

Trac:
Status: new to assigned
Owner: aagbsn to N/A

Mark all tickets that are assigned to nobody as "new".

Trac:
Status: assigned to new

This task will be done by sbws

Trac:
Status: new to closed
Resolution: N/A to duplicate

closed

moved from legacy/trac#15238 (moved)

added Feature label and removed 1 deleted label

removed 1 deleted label