docs: document Header Confidentiality Policy#8016
Conversation
09ec7a1 to
1eeeeb9
Compare
beed0f1 to
fb2f732
Compare
r10s
left a comment
There was a problem hiding this comment.
thanks for taking care!
lgtm, but i am wondering "if if val_in is an RFC 5322 date-time" is needed in this spec, regarding level of detail. it seems just to be a technical detail in case core sets date wrong elsewhere. similar for "from"
fb2f732 to
39e8dd8
Compare
I removed I also don't really understand the idea of registering HCP that RFC has, HCP is actually an implementation detail, so it does not need naming and registering. |
spec.md
Outdated
| return the UTC form of a random date within the last 7 days | ||
| else if lower(name) is 'subject': | ||
| return '[...]' | ||
| else if lower(name) is in ['message-id', 'chat-version', 'chat-is-post-message']: |
There was a problem hiding this comment.
We want to remove this chat-version from outer headers eventually. Maybe should do it now in the doc already. We don't need it and only send it for compatibility: #7932
39e8dd8 to
971f239
Compare
Requested at https://support.delta.chat/t/name-and-describe-the-header-confidentiality-policy-used-by-delta-chat-rfc-9788/4927