Skip to content

_estimate_time_received should use time_server #314

@danielrichman

Description

@danielrichman

Some points are out of order. My current favourite is the unnamed listener whose clock is set to exactly the right time and day… in May rather than April.

currently:

  • uses time_created provided by the listener, excludes points outside std dev, takes mean

ideas:

  • correct time_created by using (time_server - time_uploaded)
  • if time_server provided, trust it and ignore others
  • weight listeners with time_server provided in the previous algo (4x ?)

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