Skip to content

Milestones

List view

  • Bug fixes and cosmetic issues of v0.1

    No due date
  • * Lots more documentation about how Tapestry works and how to deploy it. * Even more detail behind the NCI number, such as how many distinct communities have been detected. * More rigorous testing and benchmarking. * Various server side “knobs” on the input sources. * should Google.com be counted as one endpoint or many (e.g., based on the number of Google servers that Tapestry sees)? * data aging knobs to control data stored on server - NCI historical data - NCI calculation "window" * calculation frequency knobs to control server load

    No due date
    0/1 issues closed