Tech dobz

preparing a tiny bit of magic...

    Overview

    Zero 2.0 — What’s New and What Changed from V1

    Zero 2.0 — What’s New and What Changed from v1

    Zero 2.0 is a substantial update focused on reliability, safety, and day-to-day usability. This page summarizes what changed from v1 so you know what to expect when you upgrade.

    Highlights

    • Automatic backups with rotation and a safe global lock (no overlapping runs).
    • Recovery kit flow (optional): create, rotate, test, restore — so you can regain access without re-encrypting data if you forget the password.
    • Template Manager (UI) to create/edit database templates without editing files by hand.
    • Safer APIs: a guarded /api/get-credentials and a streaming /api/file/download endpoint for file fields.
    • Backups UI refresh: one place to create, schedule, restore, and manage retention.
    • Quality-of-life settings: timezone selection, default page size, dark mode (theme), and “include media” default for backups.
    • Faster search and smoother rendering: improved filtering and clearer result grouping across tables and vaults.

    Security & Reliability Changes

    Area v1 Zero 2.0
    Master password handling Basic unlock; no recovery flow. Structured unlock with optional recovery kit to regain access without re-encrypting existing data.
    Recovery Not available. Create, rotate, test, restore, and disable a recovery kit from the UI. Recovery is optional.
    Backups Manual backups. Manual and automatic backups with rotation. Single global lock prevents concurrent runs. “Include media” is respected across UI and scheduler.
    Auto-backup interval Not applicable. Enforced minimum interval (default 6 hours). UI shows the active minimum and clamps inputs.
    Restore safety Restore only. Optional “Create a safety backup first” before restoring; overwrite toggle with clear behavior notes.
    APIs Limited. /api/get-credentials (with only_creds) and /api/file/download. Identifiers validated; access requires a saved, authenticated local session.
    Files in APIs Not stream-oriented. File fields return URLs (and an alt streaming URL). DB-stored files and encrypted files are handled server-side and streamed on demand.
    Templates Edit JSON by hand. Template Manager in the UI to add/edit templates and generate databases faster.
    UI & rendering Basic lists and filters. Improved table filtering and rendering, clearer grouping in search results, better responsiveness on large datasets.
    Appearance & time Fixed theme; basic timestamps. Dark mode theme toggle and timezone setting so dates/times display in your local time.

    Backups: what’s different

    • Automatic scheduling: choose Daily at time (pick days/time) or Every N minutes (with a server-enforced minimum). The next run and last run are shown in the panel.
    • Retention for auto-backups: keep the newest N automatic backups; older auto backups are rotated. Manual backups are never rotated.
    • Global backup lock: prevents overlap if a job is already running.
    • “Include media”: one setting used consistently by manual and scheduled backups.
    • Restore UX: optional safety backup first; clear explanation of overwrite vs. add-only behavior.

    Recovery kit (optional)

    2.0 adds an optional recovery mechanism so you can regain access if you forget the master password.

    • Create a one-time kit and store it offline (file or code).
    • Rotate to invalidate an old kit and issue a new one.
    • Test a kit to confirm it still works.
    • Restore access using the kit if you can’t remember the password.
    • Disable recovery at any time (with your password).

    If you never create a recovery kit and you forget the master password, your encrypted data will be unrecoverable.

    APIs in 2.0

    • GET /api/get-credentials — fetch a decrypted row by table and row_id. Use only_creds=true for username/password-only output with helpful messages when columns are missing or empty.
    • GET /api/file/download — stream a single file field (handles DB-stored and filesystem files; decrypts when needed). Requires a saved, authenticated local session.

    Both endpoints validate identifiers and require that the app is running locally with an active session.

    Templates

    • Create databases from built-in or custom templates.
    • Template Manager in the UI lets you add new templates and adjust existing ones without editing JSON files directly.

    Settings & UX

    • General settings: timezone, default page size, dark mode (theme), and backup media preference.
    • Backups Manager: centralized page to create, schedule, restore, rotate, and download backups.

    Compatibility & upgrade notes

    • Existing vaults from v1 continue to work in 2.0.
    • After upgrading, consider creating a recovery kit (optional but recommended).
    • Review the Backups Manager and configure automatic backups if you want scheduled protection.
    Behavior differences you might notice
    • Backups now respect a server-enforced minimum interval; very short intervals are clamped for safety.
    • Automatic backups are tagged and rotated separately from manual backups.
    • API responses for file fields return URLs (and an alternate streaming URL) instead of embedding bytes.
    • Search and list rendering are more responsive on large tables.

    Where to find updates

    • Zero Orbi: release notes, new templates, and announcements.
    • Support: use the in-app Support link if you run into issues or have questions.

    If you need a deeper dive, see these guides:

    • Backups & Restore (Manual + Auto)
    • Account Recovery & Password Changes
    • Using Templates in Zero
    • Using the Zero API