Document API #53
Labels
No labels
area:docs
area:identity
area:ops
area:plugin
area:server
channel:community
channel:direct
channel:owned
channel:press
channel:social
e2ee-constrained
gate:at-ga
gate:pre-ga
marketing
parity
relay:absent
relay:planned
relay:requested
relay:supported
risk:additive
risk:contract
risk:none
usability
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
Nectenda/nectenda#53
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Part of #37. Depends on the headless client.
What Relay does
"API access to your Relay Server — documented API for external applications,
enabling automation workflows, AI integration and custom applications" is
Active on their roadmap and a Premium line item. No public documentation
of it exists that I could find, so it is announced rather than shipped.
What ours must be
Same constraint as the Git mirror: the server cannot serve plaintext, so the API
is local — served by the headless client or the plugin, against decrypted
content, on the customer's machine.
That is a real difference from theirs and worth stating plainly: their document
API is a cloud endpoint, ours is a local one. Ours cannot be called by a SaaS
integration without the customer running something. In exchange, no third party
ever holds readable content.
Risk
risk:additive.Verification
The API is proven to serve only decrypted-locally content and to require keys the
server does not hold — assert it, since this is the claim the product is built on.
Moved to the Vikunja board as NEC-30: https://projectron.nerchure.com/tasks/30