Blind Dev

AI consulting, workflows, and accessibility from real practice

I help diagnose the workflow, estimate ROI and risks, implement an AI agent or automation, and verify that the system is safe, accessible, and useful in real scenarios.

Where Blind Dev helps

Site overview

What you can find on Blind Dev

Services, projects, articles, and contacts are organized so visitors can quickly understand how I can help and where to read more.

What would you like to do?

Start with a task, then choose a concrete tool, skill, article or Hermes contribution.

All tasks · What is new

What is new

    No saved interests — latest updates across all topics.

    • Proposed Secure ENV catalog update to 0.8.7 — Open — proposal

      This open PR proposes changing only the Secure ENV catalog entry in Hermes: pin the published 0.8.7 SHA, revise the description and add install-visible warnings. Linux scope, the Hermes ≥0.22.2 floor and community tier remain. The plugin version aligns password, saved TOTP and card destination selection with native Browser Vault; it does not move plugin code into core or automatically update installations. A maintainer decision under rule 11 is still required: approved-key ingress reads and writes the selected .env, and setup directly reads owner IDs from it; no exemption is claimed. The plugin runs in-process, depends on internal APIs and retains a CAUTION scanner warning. One-use links authorize their holder; CVC is stored in the encrypted Vault, and sites may authorize or submit operations in response to input. Allowlisted operation consumers run unsandboxed with gateway privileges. Filling does not confirm sign-in or payment. The PR is not merged, and inclusion in a Hermes release is unverified.

      · Source

    • hermes-secure-env-plugin — Release published

      Enter secrets over HTTPS outside the chat and language-model context. Explicit human-entered code layouts support groups of up to 100 fields and the Unicode 14.0.0 policy. Version 0.8.7 aligns password, saved TOTP and card destination selection with native Browser Vault: field stamps replace the previous CSS-history and document-census checks; origin, profile, original-transport checks and separate payment-fill consent remain. Requires Hermes ≥0.22.2 with the public captured-CDP dispatch API, Python 3.11+ and Linux/POSIX. Use a reviewed tag or wheel; catalog installations use a separate SHA pin and do not update automatically. Requires your own TLS and owner authorization. The plugin runs in-process with internal APIs and a CAUTION warning, not in a sandbox. Filling does not confirm sign-in or payment; sites may act on input. Successful GigaID sign-in after the 0.8.5 fixes remains unconfirmed; the broader legacy suite then did not complete because of file timeouts. That does not validate 0.8.7 or guarantee compatibility with every site or screen reader.

      · Source

    • hermes-secure-env-plugin — Update

      Secure ENV 0.8.7 aligns password, saved TOTP and card destination selection with native Browser Vault: field stamps replace the previous CSS-history and document-census checks. Binding to the selected parent page, origin, profile and original-transport checks and separate payment-fill consent remain. HTTPS-field discovery can traverse an intermediate about:blank document, and explicit card discovery stops once all declared destinations are found. Filling does not confirm sign-in or payment; sites may react to input. Successful GigaID sign-in remains unconfirmed; the earlier incomplete run with timeouts does not validate 0.8.7. This is not an all-sites guarantee.

      · Source

    What is new · My interests