Dropbox Camera Uploads Review — 2026-05-14

This is the first human-readable review page for the photo organization project. It is meant to be viewed through the site rather than buried in local terminal output.

Privacy note: this page intentionally contains aggregate counts and workflow recommendations only. It does not publish file names, paths, thumbnails, or private photo contents.

Source

• Source: dropbox:Camera Uploads
• Access method: rclone Dropbox OAuth remote
• Local stack: /home/reasoncode/photo-stack/piwigo-b2
• Raw inventory artifact: import/agent-review/dropbox-camera-uploads-lsjson-20260514T195134Z.json
• Local summary artifact: import/agent-review/dropbox-camera-uploads-summary-20260514.md

Summary

• Files: 15,301
• Total size: 173.59 GiB
• Date range by Dropbox modified time: 2006-08-24 to 2024-04-22
• Zero-byte files: 0
• Files under 50 KB: 75
• Media-like files: 15,300

File type breakdown

Interpretation

The Dropbox Camera Uploads library is manageable by file count, but videos dominate storage.

The key number is:

.mov: 2,085 files, 149.45 GiB

So the next workflow should not blindly sync everything into every app. Photos are relatively cheap to sample and index; videos should be handled deliberately.

Recommended architecture

Dropbox Camera Uploads / Google Photos / iOS uploads
  -> cloud inventory via rclone / immich-go
  -> lightweight sample + metadata index
  -> Immich as the responsive intelligent photo library
  -> Hermes/agents generate review manifests
  -> user-approved quarantine/deletion only
  -> Piwigo for curated shareables and document packets
  -> Backblaze B2 before irreversible cleanup

Recommended next actions

1. Do not delete or move Dropbox originals yet. This pass was inventory only.
2. Configure Cloudflare Access protection for /agent-reviews/* before treating this as a private review area.
3. Install Immich as the main intelligent photo library if the goal is automatic organization rather than manual album curation.
4. Pull a bounded photo-first sample for visual review and caption/tag experiments.
5. Add B2 before any large-scale cleanup, quarantine, or deletion workflow.

Proposed deletion safety policy

Agents should never directly delete from Dropbox, Google Photos, Immich, or Piwigo on a first pass.

Use this policy instead:

candidate -> review manifest -> user approval -> quarantine -> retention window -> final deletion

For Dropbox, quarantine would mean moving approved files to a folder such as:

Camera Uploads/_agent_quarantine/YYYY-MM-DD/

Only after a retention period should final deletion be considered.

Status

• Dropbox OAuth remote: configured.
• Dropbox Camera Uploads cloud inventory: complete.
• Piwigo local stack: running.
• Cloudflare tunnel container: running.
• Public DNS for photos.freereason.org: still needs Cloudflare public hostname/DNS configuration.
• Immich: not installed yet.
• B2: not configured yet.