capture.rs

`crates/veilvoice-cli/src/capture.rs`

veilvoice-cli · 339 lines · read the source here · or on GitHub

veilvoice capture -- which screen recorders are running, and which of them you have said you meant to run.

The command-line front end to veilvoice_watch::capture. That crate holds the table, the allowlist and the honest account of the three things it cannot do; this file decides where the allowlist lives and prints the result.

Where the allowlist lives

<config>/veilvoice/capture/allow.txt

Beside everything else this program keeps. Plain text, nothing secret in it: an allowlist is a note to yourself about which notifications you have already read.

The exit code

veilvoice capture check exits non-zero when something not allowed is running, so it can be a step in a script that refuses to start recording something sensitive while a recorder is open. Allowing a program is precisely how you tell that script you meant it.

It exits zero when the listing itself failed, and says so on the way past. A check that cannot see is not a check that passed, but neither is it a reason to fail a script. The difference is in the words, and the words are printed.

In plain words

Tells you which screen recorders are running, and lets you say you meant to start one so it stops being mentioned.

It cannot tell whether a program is actually recording, only that it is open, and it says so. A meeting application being open is not somebody watching your screen.

WHAT THIS FILE CONTAINS

339 lines defining 10 functions (7 public), 0 types and 0 constants. Everything below is read out of the source, so it cannot disagree with the code.

What happens when it runs. These are the ways in: public, and nothing else in this file calls them, so they are what an outside caller reaches first.

status line 78 · What is running, what is allowed, and what this cannot see.
reaches load, allow_path, capture_dir
calls line 130 · Every program in the table, whether it is running or not.
list line 213 · veilvoice capture list: the screen recorders this build knows how to name.
allow line 246 · Stop notifying about one program.
reaches load, save, allow_path, capture_dir
deny line 263 · Start notifying about one program again.
reaches load, save, allow_path, capture_dir
check line 279 · Look now, and let the exit code answer.
reaches load, allow_path, capture_dir

WHAT CALLS WHAT

The functions this file defines, and the calls between them. An edge means the callee's name appears, called, inside the caller's body. This is a syntactic reading, not a type-resolved one.

The same graph as Mermaid source

%%{init: {"theme":"base","themeVariables":{"background":"#1a1b26","primaryColor":"#1f2335","primaryTextColor":"#c0caf5","primaryBorderColor":"#7aa2f7","secondaryColor":"#16161e","tertiaryColor":"#16161e","lineColor":"#737aa2","textColor":"#c0caf5","mainBkg":"#1f2335","nodeBorder":"#7aa2f7","clusterBkg":"#16161e","clusterBorder":"#2f3549","fontFamily":"ui-monospace, SFMono-Regular, Consolas, monospace","fontSize":"14px"}}}%%
flowchart TD
    n_capture_dir["capture_dir<br/>line 48"]
    n_allow_path["allow_path<br/>line 53"]
    n_load["load<br/>line 64"]
    n_save["save<br/>line 70"]
    n_status(["status<br/>line 78"])
    n_calls(["calls<br/>line 130"])
    n_list(["list<br/>line 213"])
    n_allow(["allow<br/>line 246"])
    n_deny(["deny<br/>line 263"])
    n_check(["check<br/>line 279"])
    n_allow --> n_load
    n_allow --> n_save
    n_allow_path --> n_capture_dir
    n_check --> n_load
    n_deny --> n_load
    n_deny --> n_save
    n_load --> n_allow_path
    n_save --> n_allow_path
    n_status --> n_load
    click n_capture_dir href "https://github.com/tilas01/veilvoice/blob/main/crates/veilvoice-cli/src/capture.rs#L48" "open the source"
    click n_allow_path href "https://github.com/tilas01/veilvoice/blob/main/crates/veilvoice-cli/src/capture.rs#L53" "open the source"
    click n_load href "https://github.com/tilas01/veilvoice/blob/main/crates/veilvoice-cli/src/capture.rs#L64" "open the source"
    click n_save href "https://github.com/tilas01/veilvoice/blob/main/crates/veilvoice-cli/src/capture.rs#L70" "open the source"
    click n_status href "https://github.com/tilas01/veilvoice/blob/main/crates/veilvoice-cli/src/capture.rs#L78" "open the source"
    click n_calls href "https://github.com/tilas01/veilvoice/blob/main/crates/veilvoice-cli/src/capture.rs#L130" "open the source"
    click n_list href "https://github.com/tilas01/veilvoice/blob/main/crates/veilvoice-cli/src/capture.rs#L213" "open the source"
    click n_allow href "https://github.com/tilas01/veilvoice/blob/main/crates/veilvoice-cli/src/capture.rs#L246" "open the source"
    click n_deny href "https://github.com/tilas01/veilvoice/blob/main/crates/veilvoice-cli/src/capture.rs#L263" "open the source"
    click n_check href "https://github.com/tilas01/veilvoice/blob/main/crates/veilvoice-cli/src/capture.rs#L279" "open the source"
    classDef entry fill:#1f2335,stroke:#7aa2f7,color:#c0caf5
    class n_status,n_calls,n_list,n_allow,n_deny,n_check entry
    classDef api fill:#1f2335,stroke:#7dcfff,color:#c0caf5
    class n_capture_dir api
    classDef helper fill:#1f2335,stroke:#bb9af7,color:#c0caf5
    class n_allow_path,n_load,n_save helper

This site loads no third-party script, so it cannot run Mermaid; the diagram above is the same nodes and edges drawn by the generator instead. GitHub renders the source below directly.

ITEMS

Item	Line	Documentation
`capture_dir` _{pub fn}	48	Where the allowlist is kept.
`allow_path` _fn	53	Where the screen-recorder allowlist is kept for this user.
`load` _fn	64	The allowlist, or an empty one when none has been written yet.
`save` _fn	70	Write the allowlist back, readable by its owner and nobody else.
`status` _{pub fn}	78	What is running, what is allowed, and what this cannot see.
`calls` _{pub fn}	130	Every program in the table, whether it is running or not.
`list` _{pub fn}	213	veilvoice capture list: the screen recorders this build knows how to name.
`allow` _{pub fn}	246	Stop notifying about one program.
`deny` _{pub fn}	263	Start notifying about one program again.
`check` _{pub fn}	279	Look now, and let the exit code answer.