The inbox and your phone

Everything that waits for you, across all videos, is in one list: the inbox. Answer an agent's question, check a fix, approve a new version or wave a note from a review link through, right where it is. Lampo also installs as an app on a phone, tablet or computer, and notifications bring the inbox to the lock screen.

Getting it onto your phone

A hosted server is the way to review from anywhere (see server-mode.md and docker.md): open its address on the phone and sign in with the same account as on your computer.

Your own machine, on the same Wi-Fi. npm run lan (or LAMPO_LAN=1) also serves the app on your network and prints a link with an access token. Open it on the phone once; the phone stays signed in. This is meant for your desk, not for on the go, and notifications don't work over it (see where they work).

Installing it as an app

The installed app opens on the inbox, full screen, with its own icon. It starts instantly and shows an "Out of reach" screen when it can't reach the server. After an update, "A new version of the app is ready" offers a reload.

What stays on the device: the app's code, and a copy of the screens you saw last (the library, the inbox, the notes), so the next start shows them at once while it catches up with the server. That copy is kept per account and deleted when you sign out. Videos and pictures are never kept; they always come from the server.

The inbox

Inbox is first in the library's sidebar (and in the phone's menu, and in ⌘K), with the number of things waiting. The bell in every top bar shows the same number and opens the same list over the page you are on: a popover on a computer or tablet, a sheet from the bottom on a phone. The page underneath keeps its place.

On a screen 1100 px wide or more, the inbox reads like a mail client: the list on the left, the picked item's preview on the right with its action. Narrower, every item is a card with its action right on it; tap one to open it in the player.

What lands there

Work leaves when it is done. Questions, an agent's work that needs you, fixes, versions to review, failed posts and playbook suggestions have no Got it: they leave when they are answered, checked or decided. Only what informs can be waved through, and it also leaves by itself once you have read it in the preview (it stayed open for a moment, and you moved on).

Got it changes nothing in the review; it only takes the item off your own list. Each person sees what their role allows: questions need the right to write notes, fixes the right to check them, versions to review and stalled videos the right to approve, playbook suggestions the right to edit playbooks, failed posts the right to publish, and an agent's work (waiting for your OK, stopped, gone quiet) the right to work with agents — never a reviewer. Stalled videos come last and aren't counted in the bell's number. Notes someone saved but hasn't sent never show up in anyone's inbox.

By video or by kind. By video (the default) groups everything per video, the most urgent video first: its name, what it holds ("3 questions · 2 fixes · V4 to review") and a ⋯ for the whole video. By kind groups the list as in the table. The switch sits across from the title and is remembered per device; the bell's list follows it, showing a video with three or more items as its most urgent item and "n more".

Clearing it where it is

Every row has its own actions, in the place of its time while the pointer or the keys are on it (on a touch screen, behind a ⋯ on the row):

Done, Got it and Looks right leave the list at once, with Undo in the message that follows.

Later puts an item aside for you alone, until tomorrow at 9:00 (your device's time) or until its video moves (a new version, a note, a reply, a decision), whichever comes first. It changes nothing on the note or the video and isn't counted while it is aside; "n later" at the bottom of the list shows what is aside, with Bring back.

Several at once: tick the circle on a row's picture, ⇧-click for a run, ⌘-click for one more, ⌘A for all. The bar under the list offers Done (questions close, updates are waved through; fixes and versions stay), Later, and Looks right when every picked item is a fix. A video's ⋯ does the same for the whole video: Got it on all updates, Done for this video, Later for this video.

Keys (never while you type): ↑/↓ or J/K move, ↵ opens the preview (again: the full player), E done or got it, ⇧E done for the whole video, H later, X select, Esc clears the selection, ? lists them all.

With nothing waiting, the inbox says All caught up, and when something put aside comes back.

The preview

Pick an item and its preview opens: beside the list on a wide screen, in its place on a narrow one (the back arrow returns to the list).

• A small frame-exact player, parked on the note's frame (a note about the whole video: the first timecode its words name, else the poster's frame). A fix is shown in the version it was fixed in. The note's marks are drawn on the version they were drawn on, with a toggle.
• A timeline with the note's moment on it (a range as a band) to tap or drag to any frame; play and pause, a frame back or on, sound, and Play around it: from 1.5 s before the frame to 1.5 s after, then back on the frame. Timecodes in the note's text are links that move the picture there.
• Who did what and what was said: the note, what the agent changed, the last replies. A version to review says what it brings instead: who put it up, what changed since the version before (fixes in it, notes carried over), the file, and what Auto-check found.
• The item's action, at the bottom: for a question the answers the agent offers (one tap sends one), a field for your own answer and whether the agent gets it now ("Running · gets it now" or "Not running · gets it when it starts"); for a fix Looks right, Still wrong or Compare (check mode in the player); for a version Approve V4 or Request changes; Seen for a note from a review link, Got it for the rest; Later on every item. A playbook suggestion shows its diff with Accept and Reject.

Open in player (also O, or a double-click on the picture) takes the frame on screen to the full player: the note open, a fix in check mode. In the preview, Space plays and pauses and ←/→ step a frame (⇧ a second).

Notifications

Turning them on

While a device hasn't decided, the inbox asks once: Turn on asks the device for permission, Not now puts the question away on that device. If notifications are blocked or need a step first (the Home Screen on iOS, https), the inbox says what to do. Once they are on, Settings → Notifications shows this device's state, lets you pick what is worth a ping on it, Send a test checks the way through, and Turn off here stops them. Each device is turned on and set up on its own.

What pings you

A bundle waits until its video has been quiet for that long (two minutes at most), so an agent's batch of fixes arrives as one notification, and a newer notification about the same video replaces the older one. An agent starting, rendering or getting on never pings you: the app shows it. Nobody is told about their own actions. Tapping a notification opens the exact note, or check mode at the fix; when the app is already open, it goes there instead of opening a second window. On a server with several workspaces it opens in the workspace the note is from (the app switches there first). Where the platform supports it (installed apps on iOS, macOS, Windows and many Android launchers), the app icon shows how much waits for you.

Where they work

Browsers allow notifications only on secure pages: https, or localhost on the computer the app runs on.

• iPhone and iPad (iOS 16.4 or later): only in the app added to the Home Screen, never in a Safari tab. The app says so when you open it in Safari.
• A hosted server over https: every browser, on every device.
• Your own machine: on that computer itself. A phone on the Wi-Fi reaches it over plain http, where browsers don't allow notifications; use a hosted server for notifications on the phone.

What goes through the push service

A notification travels through the push service of the browser's maker (Apple, Google, Mozilla or Microsoft). Its content (the title, a line of the note, the link inside the app) is encrypted for the device (RFC 8291), so the push service sees only its size and timing. The server signs its requests with its own key (VAPID) and sends to those four services only, and only to a public address their name resolves to (it connects to the address it checked). Devices that uninstalled the app or revoked the permission are dropped when the push service says so. Sign out everywhere and a password reset drop every device of the account, so a lost phone stops showing notes on its lock screen.

Details

Files.

The contact push services see is push_subject (LAMPO_PUSH_SUBJECT): mailto:you@example.com or an https URL. The default is the server's public_url when it is https, else a placeholder.

API.

Server-sent events carry for-you when a list changes. Full shapes are in api.md and undefined.

Older addresses. #/for-you and #/verify (fixes to check) open the inbox; #/open (open notes) opens All videos on the Being fixed lane.