Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Define zero-telemetry and strict-offline contract for dictation and future local translation

Chiusa
  • Qualcosa non va?
#65 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
35/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
linux, shell
Ambito
backend, security

Direzione di ricerca

Start by tracing the bootstrap release and dependency downloads, faster-whisper model acquisition, and dictation runtime paths; the issue does not name specific files or tests. Verify which endpoints are contacted and what data upstream libraries may send, then define and implement strict offline behavior and audit telemetry and update defaults. Done means documenting the verified data flow, requiring explicit model acquisition, and demonstrating with egress blocked that cached dictation and future local translation run without steady-state requests.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

enhancement privacy

Privacy contract / future translation design

HermesKey is local-first. A static sweep of current code found no HermesKey analytics or transcript-upload endpoint, but bootstrap downloads a release/dependencies and faster-whisper may fetch a model on first use. Customers should be able to distinguish explicit setup/model downloads from any runtime network access and choose a verified offline mode. Planned local-LLM translation must not silently introduce remote inference, telemetry, prompt logging or content upload.

Acceptance

  • Document a precise network/data-flow inventory: endpoints required for install/model download, when they are contacted, and what data could be sent by upstream libraries (verify rather than promising third-party behavior). State clearly that neither dictation nor future translation is uploaded by HermesKey.
  • Provide an opt-in strict offline configuration after a model is cached or supplied locally; fail clearly if a missing model requires download rather than silently going online. Audit upstream telemetry/update-check defaults and disable what can be disabled without breaking explicit downloads.
  • For any future translation engine: local model/process only by default, no remote translation API or transcript/prompt telemetry, no persistent content logs or implicit retention, explicit consent for model acquisition. Test with network egress blocked that preloaded dictation/translation still work and that no requests are made during steady-state operation.

This is a privacy requirement and verification task; this audit did not discover an existing HermesKey telemetry endpoint or claim that transcription currently uploads audio.

Lingua principale
Shell
Stelle
0
Fork
0
Merge medio
16m
PR unite (30g)
40

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di graygarbage/HermesKey

Tutte le issue di graygarbage/HermesKey

Issue simili

Altre issue su Shell/Bash

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.