Media Gateway focuses on convention-driven publication of private provider-managed images and videos. The product model defines its scope; optional directions below are not promises or scheduled releases.
See configuration, the consumer guide and media behavior for the supported contracts. Immich 3.2.0 is the deployed validation baseline; provider upgrades require renewed representative checks.
Source-metadata exposure is off by default. Capture/local timestamps,
coordinates and original paths remain present as null; originals return fixed 404
without provider fetches. Qualified previews/posters remain available. Set
privacy.expose_source_metadata=true deliberately to enable sensitive public catalog
fields and exact originals, whose bytes may contain embedded metadata. Filenames
and collection names remain visible in both modes.
The settled surface is catalog, preview/poster and privacy-permitted exact original. Consumers own browsing, selection, presentation and their derivative or caching strategy. Additional gateway representations are not standing future work; a measured new need requires a fresh bounded issue.
Provider asset IDs are not secrets because delivery reauthorizes every request. Signed or opaque public identifiers require a demonstrated abuse, privacy or integration need.
Another concrete integration may justify extending the small provider boundary. A generic provider framework is not needed for the current Immich integration.
Gateway caching, arbitrary resize/crop/quality APIs and transcoding are outside the current product. Any proposal needs measured requirements and must preserve fresh publication authorization; cached bytes cannot become independent authority.
Immutable versioned binaries are distributed through GitHub Releases. The bundle verification and operations guide describes download, checksum verification and installation. Host-specific public routing remains an operator deployment decision after validation.