docs/developers/examples/api/47-remove.json at main · pipobscure.com/ordner · Tangled

replace big-tech and host basic infrastructure yourself! ordner.fyi

ordner docs developers examples api 47-remove.json

612 B · 36 lines

JSON

Blame

· webdav, settings, seams, docs: a delegate and a connected application act as the drive's owner, so what they write into a drive is the owner's own — every annotation source in a drive is keyed by its owner and marked only by the application it came from (a delegate's web session writes as the owner's web source, their app or app password as <owner>.app.<client_id> / <owner>.pw.<id>; the mutation audit still names the actor). drive:annotate now writes every photo detail through FileNode/set (title, description, keywords, rating, taken and its offset, location, orientation, edits, faces) into the picture's sidecar, as the owner would, and still never content, a name, a folder or a share. A delegate reads the owner's whole source list and its changes; a web session in the drive, the owner's or a delegate's, removes any source's data, an application only its own. Settings › Connected apps reads each drive's owner source per app and removes it there. accountReadOnly says what it needs. A seams test runs Emma's case end to end (her all app password through the delegation, direct, through the router, and with the delegation hidden). Developer guide examples re-recorded (Emma's application is Shelf); docs/design/annotations.md §2, docs/areas/files.md and the guide say so (Pip 2026-10-26) · 2w ago