Timelines from files
The desktop app can make a timeline from the files on your computer: a moment for each photo, video, recording or any other file, at the time you choose (#433). A folder of photos becomes an album you browse by when each was taken. Each moment's source is the file itself, so opening a moment's source opens the file in its own app, such as your photo viewer or video player. Nothing is copied: the timeline links to the files where they are.
This is only in the desktop app. A web browser can't read your folders, and a server never stores where your files are (see Your file paths stay on your computer).
Making one
Choose From files… (on a phone-sized window it's in File). The dialog asks:
| Choice | What it does |
|---|---|
| Folders and files | Add folders… and Add files… pick them in your system's own dialog; only what you pick there is read. Clear empties the list. |
| Search subfolders too | Includes the files in every folder inside the ones picked (on by default). Hidden files and folders, whose names start with a dot, are passed over, and links to other folders are never followed. |
| Which files | Photos, videos and sound (by their file extension, listed below) or Any file. |
| Date each moment by | For any file, when the file was created or when the file was last modified. For photos, videos and sound, also when it was taken or recorded, from the file's own metadata. |
| Times recorded without a time zone are in | Most cameras record the time a photo was taken without its time zone. This says how to read it: as this computer's time zone at that date (the default) or as UTC. A time with its zone is exact. |
| Metadata: Add where each was taken (GPS) | Off by default. When on, a photo or video that records its location gets a location in its metadata: { "latitude": 51.5, "longitude": -0.125 }. Where a photo was taken is often where someone lives. |
| Title | The new timeline's title; the first folder's name to begin with. |
Make timeline reads the files, showing how many it has looked at, and opens the new timeline. Stop ends it early with what it has found so far. The new timeline isn't saved yet: Save As… writes it to an .och file. A message says how many moments were made and which files were left out, and why.
What each moment holds
- Time: the date chosen, exact to the nanosecond the file system or the file records. The timeline shows dates in this computer's time zone.
- Title: the file's name, such as
IMG_0042.JPG. - Source: the file, as a
file:///link (its path, with spaces and other characters written as%20and so on). The timeline has the Sources plugin, which lists it. - Tags: the kind of file:
file:photo,file:video,file:audio, orfile:other. - Location: only when chosen, as above.
- Thumbnail: a photo or video shows a small picture of itself as its marker (see Thumbnails).
Each moment's ID comes from its file's path, so the same file gives the same ID each time.
Which dates a file has
- Taken or recorded is read from EXIF for photos (when the photo was taken, or else when it was digitized) and from the creation date in a video's or recording's header. A file without one, such as a screenshot, a downloaded image or most MP3s, is left out and counted. A date of zero, which some cameras write when their clock isn't set, counts as none.
- Created is when the file was made on this disk, which for a copied photo is when it was copied, not when it was taken. Some Linux file systems don't keep it; then those files are left out and counted.
- Modified is when the file's contents last changed.
Limits
One population makes at most 100,000 moments and looks at most at a million files and folders; past either it stops and says so. A timeline holds at most 200,000 moments.
Photos: jpg, jpeg, heic, heif, avif, png, webp, tif, tiff, dng, cr2, cr3, nef, arw, raf, orf, rw2, iiq. Videos: mp4, m4v, mov, 3gp, mkv, webm, avi. Sound: mp3, m4a, aac, flac, wav, ogg, opus, mka. Recorded dates are read from JPEG, HEIC/HEIF, AVIF, PNG, WebP, TIFF and the raw formats listed, and from MP4, MOV, 3GP, MKV, WebM and MKA.
Thumbnails
In the desktop app, a moment whose source is a photo or video on this computer shows a small picture of it as its marker, which grows on hover like any marker picture (#440, #442). The File thumbnails plugin (file-thumbnails) does this, and a timeline made from files has it; add it in Plugins to any timeline whose moments have photos or videos among their sources. A moment uses its first source that is one.
- Where they come from:
- Photos: their own small preview, which most cameras and phones store in the photo's EXIF and many raw files carry too, or else the photo itself scaled down. Each is turned the way the photo was taken.
- Videos: the cover picture an MP4 or MOV file carries, where it has one.
- Otherwise (most videos, and HEIC, AVIF and raw photos without their own preview), the system's own thumbnail, as its file manager shows it. On Linux, that is the one the file manager has already made (in
~/.cache/thumbnails), or else one made by an installed thumbnailer, such asffmpegthumbnailerfor videos orheif-thumbnailerfor HEIC. On macOS it is Quick Look's, and on Windows Explorer's. The app bundles no video decoder, so a video the system can't picture shows no thumbnail.
- Whose files the system pictures: the system's thumbnailers are separate programs that decode every kind of file with your rights, outside any sandbox, and a timeline from someone else can name any file on your computer. So the app asks them only about files you chose: those in the folders (or the files) you populated a timeline from, which it remembers, and those of any timeline you trust. Any other file gets only what the app reads itself (a photo's preview or the photo, a video's cover) and the thumbnail your file manager already keeps.
- Where they are kept: in the app's cache folder, which only you can read (as are its thumbnails, on Linux and macOS), at most 160 pixels a side, named by the file's path, size and modification time, so a changed file gets a new one. Deleting the folder only means they're made again. The page holds them while it shows them; they are never saved into the timeline or sent anywhere.
- Which files: JPEG, PNG, WebP, TIFF, GIF and BMP are scaled down when they carry no preview of their own. Photos over 256 MB without one aren't read by the app itself. Sound shows no picture. Only files the timeline may show get one: those in folders you chose, or any once you trust the timeline.
- Elsewhere: on the website and in the offline file, which can't read your files, these moments keep their usual markers.
Opening a moment's file
A moment's source that is a file shows its name. In the desktop app:
- Clicking the name opens the file in your system's app for it, if it is a photo, video, sound or document (below), or else shows it in its folder. The first time you open a file from a timeline, the app asks first, in a dialog of its own naming the file: open files from a timeline only when you trust where the timeline came from. Saying yes trusts the timeline (below), so it isn't asked again. A timeline you made with the populator is yours, and isn't asked about.
- Show in folder opens the folder holding it in your file manager (on macOS and Windows with the file selected). For a file outside the folders you chose, it asks the same first.
Only files whose apps show them, rather than run them, are opened from a timeline: the photos, videos and sounds the populator knows, and documents: PDF, plain text, Markdown, CSV, RTF, EPUB, OpenDocument (.odt, .ods, .odp, .odg), Word, Excel and PowerPoint without macros (.docx, .xlsx, .pptx), GIF and BMP. Anything else (programs, scripts, installers, shortcuts, help files, macro documents, web pages, and every type not listed) is shown in its folder instead, where you can open it yourself; so is anything that is a link to one, and, on Linux and macOS, any executable file that isn't a photo, video or sound (photos on a memory card are often marked executable). A file that has been moved or deleted, or is on another computer, can't be opened.
A source can also be typed as a file:/// path in the Sources field, one per line, alongside HTTPS links.
Which files a timeline may show
A timeline can come from anyone, and its sources can name any file on your computer, so the app doesn't take a timeline's word for which files to read. It pictures, shows in their folder or opens only:
- files in folders you chose: the folders (and files) you populated a timeline from, remembered for every timeline; and the folder of the timeline file open, which you picked when opening it, for that timeline;
- any file, once you trust the timeline: by saying yes when the app asks before opening one of its files, or showing one outside those folders. The app asks in its own dialog, which the timeline's page can't answer or imitate, and remembers the answer for that timeline's file (by its path), so a trusted timeline isn't asked about again. A timeline saved from a trusted one is trusted too. A new timeline, or one from a server, has no file, so it is trusted only until you open a file.
Any other file gets no thumbnail and isn't opened, and the app doesn't look at it at all: whether a link may be followed is decided from the path it writes, before anything on the disk is touched. So a timeline from someone else learns nothing of which files you have, and a link into a network folder doesn't make your computer contact another (on macOS, merely looking at /net/<server>/… mounts that server's shares). Network automount folders (/net, /Network) are never followed from a timeline, trusted or not, unless you populated from them. A file a link reaches through a shortcut (a symbolic link) must itself be in a folder you chose.
Trusting a timeline also shows its images from other sites. What you trusted, the folders you populated from and the timelines whose images you showed are kept in access.json in the app's settings folder, readable only by you: the latest 64 folders and 256 timelines. Delete it to be asked again.
Your file paths stay on your computer
A file's path says who you are and how your folders are arranged (/home/someone/Pictures/…, C:\Users\someone\…), so it never goes to a server:
- The app leaves them out. Saving to a server, sending a pull request or anything else sent to a server goes without
file://links, and a message says how many stayed on this computer. The.ochfile on your computer keeps them. - The server refuses them. A request holding a
file://link anywhere is refused, so no other program can store one there either.
Only the desktop app uses file sources. On the website and in the offline file, which can't open a file on your computer, they aren't listed and can't be added.