Tim on Nostr: Building Omostrich-DB, a companion to Omostrich (my local Nostr signer/composer for ...

Building Omostrich-DB, a companion to Omostrich (my local Nostr signer/composer for Omarchy).

What it is: a small headless service that keeps a fast local cache (via nostrdb) of your own notes plus their replies, reactions, and zaps, so questions like "how many times did I post this week" or "which note got the most traction" answer instantly instead of waiting on relays. For real-time trends across the network it queries relays or an indexer live, since your own archive was never going to tell you what's moving right now.

No timeline, no DM inbox, no client UI. Just a read/analytics layer with its own MCP server, so any AI agent (Hermes, Claude, Codex, whatever you use) can ask it questions about your Nostr activity on request. It never touches your key.

Built for Omarchy first since that's where Omostrich lives, but it doesn't need Omarchy specifically. It should run on any OS.

Come soon.