search

textileio / papers

Textile Whitepapers
12 stars 3 forks source link

Decouple Log ID from Writer key #44

Closed sanderpick closed 4 years ago

sanderpick commented 5 years ago

From @Gozala

  • I would recommend against Public Key as Log ID which was one of the design goals for IPDF as that implies that log can have only one ID and it's key can not be rotated. I would suggest decoupling Log ID from Writer key as that enables:
    1. Multiple IDs for the same log, which is handy if you want to publish updates on different frequencies e.g. alpha, beta, release channel.
    2. Share snapshot of the log in time to which no updates will be published.
    3. Rotate writer keys if necessary.
sanderpick commented 5 years ago

@Gozala how would you imagine referring to the "branches"? Do they get their own name / priority?

Gozala commented 5 years ago

how would you imagine referring to the "branches"?

Is that question about name itself ? I have being using term “branch” that I don’t particularly favor but do find it helpful due to git analogy. Only other term I can think of are “channel” and “pointer”. I’m absolutely open to alternatives, it’s more important in my opinion to have n:1 relationship with logs.

Do they get their own name / priority?

Name as in cryptographic key yes. Priority I don’t think so. I don’t feel like it would make sense to prescribe what multiple identifiers should be used for. Maybe they won’t be, but if log key and identifier is the same key then it can’t be, which in my experience could be a pretty inconvenient

carsonfarmer commented 4 years ago

Working on this one tomorrow.

carsonfarmer commented 4 years ago

Proposal for discussion here #62

carsonfarmer commented 4 years ago

Closing this in favour of discussion on #62.