rfc-0001-jmap-ipfs #1

Merged
peersky merged 2 commits from rfc-0001-jmap-ipfs into main 2026-09-21 07:05:35 +00:00
Owner
No description provided.
- Improved Interface RFC 0001 rewritten in JMAP terms: capability object, using semantics, Email/get, Email/set and Email/query behaviour, a SetError type and three FilterConditions
- BREAKING CHANGE Interface every image is an Image object identified by a CIDv1; url fields are removed, and embedded media in the HTML body must be ipfs: URIs
- Added Function binding of each CID to an inline EmailBodyPart by Content-Location, so a JMAP client with no IPFS support still renders an entry
- Fixed Bug slug pattern whose character class admitted uppercase and punctuation, the contradictory slug ownership rule, and the wrong claim about receivedAt on Email/set
- Added Interface conventions, security, privacy and IANA considerations, references, a worked example, the Ghost mapping as Appendix A and an implementation status appendix
- Improved Interface schema follows the RFC, the README no longer carries a status column, and the template gains Requires, Conventions, Security and References
- Fixed Bug Email property table whose nullable types split into extra columns on the unescaped pipe; it now shows the type an entry requires, with from and to never null
- Added Interface noolog:blog is the parsed view of an application/vnd.noolog.blog+json body part, so an entry is complete within its RFC 5322 message
- Added Interface comments defined by message identifier through inReplyTo and references, and revisions that reference their predecessors so comments survive an edit
- Added Interface signatures section: S/MIME or OpenPGP/MIME over the message, RFC 9219 for reporting, what is and is not covered, and why CIDs extend coverage to media
- Improved Interface implementation status lists the message part, message identifiers and signatures as not yet implemented
peersky deleted branch rfc-0001-jmap-ipfs 2026-09-21 07:05:35 +00:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
peeramid-labs/rfc!1
No description provided.