Clients
Each card is one creator: the folder we watch for their new clips, and the account folders their edited copies land in.
Content
What every client uploaded to their master folders — clips and pictures — in the last 24 hours, 7 days and 30 days.
Uploads by client
stamped with the time the file was created in Drive| Client | Clips 24 h | 7 days | 30 days | All time | Pictures 24 h | 7 days | 30 days | All time | Last upload |
|---|
A clip counts from the moment the watcher sees it in a watched folder; a picture counts from the moment a pictures folder is scanned. Both use Drive's own upload time, so a file that arrived before the folder was watched is still counted on the right day.
Activity
What employees have downloaded, and what clients have uploaded, over the last day, week and month.
Employees
clips downloaded from the Post queue| Employee | 24 h | 7 days | 30 days | All time | of which pictures | Last |
|---|
Clients
clips uploaded to their master folder| Client | 24 h | 7 days | 30 days | All time | Last |
|---|
Errors on employees' phones
what the app could not do, and for whom| When | Employee | What | Message | Doing | Phone · app |
|---|
Re-downloads
pictures downloaded more than once| Client | Account | Picture | Downloads | Employees | Who | Last |
|---|
Downloads
most recent first| When | Account | File | Status |
|---|
Click an employee for the list of what they downloaded. Uploads are stamped with the time the file was created in Drive, so clips that arrived before this page existed are counted on the right day. Downloads count from the moment an employee pressed Download in the app.
Overview
What the worker is doing right now.
Recent activity
last 8 jobs| # | Source | Job | Status | Output |
|---|
Run once
Edit everything in a folder one time, without watching it afterwards. For a one-off batch or a test.
- 1
A label, so the dashboard groups work by creator.Link, folder id, or its exact name. Only clips sitting loose in the folder count; anything inside a sub-folder (Posted, Scripts…) is left alone.
- 2
One username per account, comma separated — each gets its own uniquely edited copy in its own folder. Leave empty to put everything in one folder.the folder's own “v1”Your source files are never touched.
- 3
How many variants of each clip land in the one output folder.
Advanced — recipe, mirroring, hooks
Add a client folder
Point the software at a client's master folder once. Every clip dropped in it afterwards is edited and delivered to their account folders on its own.
Monitor a folder
checked every few minutes- 1
Whatever is already in there is left alone — only clips added after you add the watch get processed.
- 2
One username per account, comma separated — each gets its own uniquely edited copy in its own folder. Leave empty to put everything in one folder.
- 3
Per account, once accounts are listed.
Advanced — recipe, mirroring, back catalogue
Watched folders
checked every 20s when idle, every 5 min during a job| Watching | Delivers to | Makes | State | Latest |
|---|
Jobs
Every batch of edits: waiting, running, finished or failed. Failed jobs can be resumed; running ones cancelled.
All jobs
| # | Source | Job | Status | Output | Details |
|---|
Live
The worker PC, right now: what it is encoding, how far along, and its last log lines. Refreshes every 2 seconds.
Current job
Worker log
last lines from the PC · newest at the bottom—
Similarity
How alike each edit is to its source, through the matcher Meta has published, not a human eye.
By recipe
median bits apart out of 256 · lower is more alike · 31 = same picture, 70 = probably related| Recipe | Files | Bits apart | Frames matched | Verdicts |
|---|
Every file
| Job | File | Account | Recipe | Bits apart | Frames matched | Verdict |
|---|
How this is measured
Meta's published near-duplicate matcher is PDQ: the frame is reduced to luminance, downsampled to 64×64, transformed into its 16×16 lowest frequencies, and turned into 256 bits against the median. Two hashes within 31 bits are treated as the same picture; Meta documents 70 as the loose end of “probably related”. Their video matcher, TMK+PDQF, is built on the same per-frame feature.
The worker runs that on 8 evenly spaced frames of the source and of every file it makes, compares them by position (one neighbour either side, so a trim or speed change does not misalign them), and also tries the mirrored hash, because Meta's matcher checks every flip and rotation. A mirror is not a different picture to it.
Measured on two real 4K clips: a plain re-encode sits 2 bits away; soft 16–32; inset 30–46; zoom 44–56; flip 50–54. Nothing invisible gets past 70. What separates copies beyond the frame is time, audio and the file itself, which this does not measure, and Meta does not publish its full matcher.
Settings
Logins, the phone app, alerts, and what runs on the worker PC. Click a card's title to fold it.
Connection
fma_jobs → fma_variants → fma_watchesPhone app
the Post queue installs on any iPhone or Android and downloads straight from Google at full qualityAgencies
platform owner only — each agency is its own island| # | Agency | Slug | Plan | Created |
|---|
Logins
employees use the Post queue app; admins use this dashboard| Login | Name | Role | Accounts |
|---|
Alerts
so a failure overnight does not wait for someone to open this pageProcessing defaults
baked into the tool — change per job above, or in the reposmall, skipped below 0.5 language confidence@account folder per Instagram account, beside the source, reused on every runWorker PC
set on the machine, not from hereFMA_WATCH_SECS — 20 s while idle, 5 min during a jobFMA_HEARTBEAT_SECS — default 30 min into worker.logFMA_WORKER_PORT — default 47615fmaspoof worker — runs at boot and logon, idle priority, session 0