Repository navigation
FAQ
No. Normal operation is local and offline. Python and package dependencies may need network access during installation. See Privacy and the security model.
No. Source photos are read-only inputs. Countscape does not rename, rewrite, copy, or delete them, and it scans only supported files directly inside the selected directory.
GNOME may keep referencing the active file after ordinary cache cleanup. Final wallpapers therefore live in persistent XDG data; the photo-only base is rebuildable cache.
No. It changes the current user's GNOME settings and creates systemd user units. Installing missing Ubuntu host packages is outside Countscape itself.
The v0.1 support target is Ubuntu 26.04 GNOME/Wayland. Other environments are not supported claims until fixtures and live evidence exist. Check Tested GNOME Configurations for published evidence.
Not in v0.1. One private config represents one countdown and photo pool.
The offset identifies the exact instant; the IANA zone verifies the intended wall time and daylight-saving rules. Countscape refuses a mismatch instead of guessing.
Unchanged work is intentionally idempotent. If the visible countdown, selected photo, layout, event, and style are unchanged, Countscape reuses the complete output and avoids rewriting GNOME settings.
Do not hand-edit them. Countscape records content digests and refuses to replace
or remove foreign or edited units silently. Change supported schedules through
the config, then rerun countscape install.
It always preserves private config and source photos. It removes only validated Countscape-managed integration, state, cache, and generated files when GNOME no longer references them. See the lifecycle guide.
Published wiki editing is collaborator-only. Open a public issue, name the page, and use synthetic details. Do not post private data.