Fix incorrect usage of "aggregator" when we mean "calendar" #60
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Member
Author
|
See also mailing list discussion: https://lists.opentimestamps.org/pipermail/ots-dev/2017-July/000018.html |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Building on #59, this pull-req changes the stamp subcommand and git wrapper to use the terminology "aggregator" rather than "calendar" to refer to the servers that aggregate digests into per-second merkle tree commitments.
That said, I'm not totally convinced this distinction is useful... Possibly it'd be better to drop the idea of an "aggregator" and stick with "calendar"