Hazumi News

SQLite has six layers: SQL parser → query planner → VDBE → B-tree → pager → OS. (https://sqlite.org/arch.html) For key-value workloads you only need the bottom three.

SNKV cuts the top three layers and talks directly to SQLite's B-tree engine. No SQL strings. No query planner. No VM. Just put/get/delete on the same storage core that powers SQLite.

Python:

    pip install snkv

    from snkv import KVStore

    with KVStore("mydb.db") as db:
        db["hello"] = "world"
        print(db["hello"])   # b"world"

C/C++ (single-header, drop-in):

    #define SNKV_IMPLEMENTATION
    #include "snkv.h"

    KVStore *db;
    kvstore_open("mydb.db", &db, KVSTORE_JOURNAL_WAL);
    kvstore_put(db, "key", 3, "value", 5);

Benchmarks vs SQLite WITHOUT ROWID (1M records, identical settings):

  Sequential writes  +57%
  Random reads       +68%
  Sequential scan    +90%
  Random updates     +72%
  Random deletes    +104%
  Exists checks      +75%
  Mixed workload     +84%
  Bulk insert        +10%

Honest tradeoffs: - LMDB beats it on raw reads (memory-mapped) - RocksDB beats it on write-heavy workloads (LSM-tree) - sqlite3 CLI won't open the database (schema layer is bypassed by design)

What you get: ACID, WAL concurrency, column families, crash safety — with less overhead for read-heavy KV workloads.

We've all done it — "hey can you DM me the staging .env?" Secrets end up in Slack history, email threads, shared notes — all searchable, all persistent. The secure path (1Password, GPG, etc.) always had more friction than the insecure one, so people took the shortcut. enseal makes the secure path faster than the insecure one: # sender $ enseal share .env Share code: 7-guitarist-revenge Expires: 5 minutes or first receive

# recipient $ enseal receive 7-guitarist-revenge ok: 14 secrets written to .env Zero setup, no accounts, no keys needed for basic use. Channels are single-use and time-limited. The relay never sees plaintext (age encryption + SPAKE2 key exchange). For teams that want more: identity mode with public key encryption, process injection (secrets never touch disk), schema validation, at-rest encryption for git, and a self-hostable relay. Written in Rust. MIT licensed. Available via cargo install, prebuilt binaries, or Docker. Looking for feedback on the UX and security model especially. What would make you actually reach for this instead of the Slack DM?

Detailed documentation here: https://enseal.docsyard.com/

Home

Show HN: enveil – hide your .env secrets from prAIng eyes

The Engine Behind the Hype

IDF Killed Gaza Aid Workers at Point Blank Range in 2025 Massacre: Report

Atlantic: Sam Altman Is Losing His Grip on Humanity

Show HN: SNKV – SQLite's B-tree as a key-value store (C/C++ and Python bindings)

Panasonic, the former plasma king, will no longer make its own TVs

Decimal-Java is a library to convert java.math.BigDecimal to and from IEEE-754r

Google, Apple start testing encrypted RCS on Android and iOS 26.4

Show HN: Autonomous AI Agent Fleets

IBM shares plummet 13% after Anthropic COBOL announcement

Claude for Government

Show HN: Self-modifying AI agent with full computer use. Mac-app, MIT

Diesel Vortex: Inside the Russian cybercrime group targeting US and EU freight

Lamborghini cancels their multi-year EV project

Everyone in AI is building the wrong thing for the same reason

Show HN: acorn – LLM framework for long running agents

Why I Hate Anthropic and You Should Too

Human Existence Is Just as Wasteful as AI Data Centers, Sam Altman Suggests

Say Goodbye to the Undersea Cable That Made the Global Internet Possible

Show HN: Enseal – Stop pasting secrets into Slack .env sharing from the terminal