Link images on the server instead of storing copies; credit their sources
- github
- github/openchronology/timeline-app
- commit
- main
- github/athanclark
Closes #109. Saving a timeline to the server stored copies of its linked images (assets, captured by the browser from hosts allowing cross-origin access), which the platform then served to readers. Hosting copies reproduces and distributes the images; linking to where their owners host them is the safer footing (the Ninth Circuit's server test, the EU's Svensson line), though contested elsewhere (the Fifth Circuit's 2026 Emmerich decision). - The server keeps links only: the editor no longer embeds copies when saving or proposing, and the server drops any it is sent (the API's document validation, pull requests, the store's whole-document writes). Exports (.ochx, .och, offline HTML, desktop files) still embed copies: they are the user's own files. - The migration removes copies earlier releases stored, from timelines, saved history (settings, revision patches, snapshots) and pull requests: saved history's one exception to immutability, made once, like a takedown. Timelines' storage shrinks by what the copies took. - Images are credited where they show: the hover card and details name the host and link to the original, and the image field asks owners to link only images they may share. - docs/images.md explains the choice and the law; the terms, privacy notice and plugin docs follow. Co-Authored-By: Claude Opus 5.5 Claude-Session: https://claude.ai/code/session_011fFY8eruEi1xAkkMBni13B https://github.com/openchronology/timeline-app/commit/1f521fbff6b3f0784332b37ee978c03ca65e2c13
Related
Open Link images on the server instead of storing copies; credit their sources in the timeline