kami
78f5feea11
A locked screen drops the radio, changes network or dozes, and one request fails. Both halves of an advance treated that as the session's fault. The outbox kept the failed event at its head with the comment that a later retry would pick it up, but nothing ever triggered one, so it sat there while the caller was rejected. advanceVibe then cleared the prefetched future and paused, destroying a plan that was still valid. Transient failures now hold the outbox entry unsettled and resend the same event id on a backoff, so no duplicate feedback reaches the director. The retry around the serve sits on the serve alone: serving a version is idempotent, while replaying the whole advance would report a second outcome for a track heard once. Each wait ends early when the browser says the network is back, which is the moment that matters when a screen unlocks. A drop that outlives every retry leaves the future intact to carry on from. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
muzick
A high-performance, distributed music orchestration and recommendation platform.
Overview
muzick is designed to manage a local music library while providing an "infinite vibe" listening experience. It bridges the gap between a local filesystem and advanced discovery engines through a tiered recommendation architecture.
Tech Stack
Frontend
- Framework: React
- Routing: TanStack Router
- Data Fetching: TanStack Query (with Look-ahead Buffering)
- State Management: Zustand (for Session/Vibe state)
- Styling: CSS Variables (Customizable Themes)
Backend
- Runtime: Node.js / TypeScript
- Framework: Fastify
- Task Queue: BullMQ (via Redis)
- Search: Typesense
Infrastructure & Data
- Database: PostgreSQL (Source of truth for metadata, relationships, and session state)
- Cache/Queue: Redis
- Audio Analysis: Essentia (via Worker processes)
- External Metadata: MusicBrainz, Discogs, LRCLib, Cover Art Archive
Core Concepts
- The Rolling Vibe: A continuous, evolving stream of music that uses a "Rolling Window" of tracks. It interleaves owned library tracks with high-probability "probation" tracks (external discoveries).
- The Dislike Lifecycle: A multi-stage state machine that protects users from accidental deletions while ensuring the library stays clean.
- Tiered Similarity: Instant metadata-based matches, followed by deep audio-feature similarity.
Getting Started
Prerequisites
- Docker & Docker Compose
Running Locally
Vibe uses the same per-user identity convention as the rest of the API:
x-user-id when supplied, otherwise the local default user. Each user's Vibe
session and listening history are isolated from other users.
docker-compose up -d