A room made for attention
Good reading tools do not compete with the page…
Local-first personal reader
Read quietly.
Keep what matters.
Rinwa turns RSS, web articles, and public video into a calm reading stream. The original appears first, translation settles underneath, and every highlight or note remains yours.
No account required · macOS is the primary quality target · Android is a development preview
TodayBy time
Notes on a small, open web
The links we keep become a map of what mattered…
SQLite, indexes, and the long view
Why a database on your own device still matters.
A room made for attention
The best reading tools disappear. They hold the text still and let understanding arrive at its own pace.
A good reading room does not compete with the page. It softens the edges of the world until only the words remain.
好的阅读空间不与页面争夺注意力。它让世界的边缘渐渐柔和，直到眼前只剩文字。
Images keep their place. Lists keep their rhythm. Code remains exactly what the author wrote.
图片留在应有的位置，列表保有原来的节奏；代码则完整保留作者写下的样子。
JUST KEPTObsidian ↗
“Let the tools disappear. Keep the understanding.”
Original firstTranslation followsKnowledge stays
RSS · Atom · JSON Feed✦
Public YouTube channels✦
Original-first translation✦
Local hybrid search✦
Two-way Obsidian knowledge✦
Encrypted backups✦
One reading surface
Many sources.
One quiet rhythm.
Feeds, web pages, videos, and future connectors do not become separate silos. They enter one local content layer and share the same extraction, translation, search, highlighting, and note tools.
Sources enter Rinwa
Independent publishing, on your time.
Follow blogs, newsrooms, and changelogs while preserving authors, dates, source links, and feed content.Read
The original arrives first.
Translation appears block by block without replacing or delaying the source. Code, dates, numbers, links, and already-Chinese text stay untouched.
Organize
A search can become a living feed.
Search articles, notes, and highlights locally. Save the conditions and the result stays in the sidebar, collecting what you care about over time.
Remember
Reading should leave more than a status.
Bookmarks, highlights, personal notes, tags, and references become one durable knowledge record. Markdown edited in Obsidian returns to Rinwa.
Search your understanding
Find more than words.
Find what you understood.
Rinwa combines local full-text indexing with optional multilingual vector retrieval. Models, indexes, and articles stay on-device. If a model is unavailable, search falls back quietly instead of breaking your library.
- ✓ Articles, notes, tags, and highlights together
- ✓ FTS + dense retrieval + RRF ranking
- ✓ Visible download, indexing, pause, and rebuild states
Searching on this device · nothing sent to the cloud
Article92%
SQLite WAL Mode Can Lock Short-Lived Readers
…a local database does not mean giving up sync. It means every device first owns a library that can work by itself.
Lobsters · 3 hours agoYour note86%
Sync operations, not the entire database file. Each device keeps its own media and indexes.
#sqlite · #sync · ObsidianFTS+Local embeddings→RRF
Keep what matters
Your knowledge should not belong to a subscription.
Articles expire and services change. Your notes should not. Rinwa treats highlights, tags, references, and edited summaries as user data, never as disposable AI cache.
“A good reading room does not compete with the page.”
好的阅读空间，不与页面争夺注意力。
MY NOTE
Calm is not the absence of features. It is making them appear only when needed.
Local first, honestly
The cloud may help. It should never be a prerequisite for reading.
SQLite on every device
Subscriptions, articles, media, and indexes live locally first. Saved reading continues offline.
Sync operations, not database files
Optional Rinwa Sync exchanges selected states and operations while every device keeps an independent library.
App updates do not clear content
Extraction, translation, and summary caches have separate versions. A failed refresh preserves the last successful result.
An exit route stays open
OPML, Obsidian, and encrypted full backups keep subscriptions and knowledge portable.
Under the reading surface
Technical when it matters.
Invisible when it does not.
Rinwa keeps the reading surface calm, but the boundaries underneath are explicit: local ONNX search, provider-aware AI, and operation-log synchronization.
LOCAL SEARCH01
FTS + ONNX embeddings
A pinned EmbeddingGemma model runs locally. Sparse and dense ranks meet through RRF; failure returns to full-text search.
SQLite FTS＋256d→RRF
Explore search architecture ↗
AI RUNTIME02
Evidence before provider
Local context selection, token budgets, citation IDs, streaming, retries, and usage records wrap the provider you choose.
[P][H][S]→Provider
Explore the AI boundary ↗
SYNC PROTOCOL03
Operations, not SQLite files
Devices exchange immutable operations through CouchDB, then merge fields deterministically with HLC clocks and tombstones.
Device A⇄Op log⇄Device B
Explore synchronization ↗
Architecture, cache rules, privacy, knowledge surfaces, and honest platform status now live in one place.
Open DocumentationOne interface, many screens
One reading surface across your devices.
React and Tauri 2 let platforms share the interface and reading logic. When a native capability is not ready, Rinwa says “in development” instead of showing a false green checkmark.
macOSPrimary target
Designed for keyboards, trackpads, and long reading.
Native windows, hierarchy swipes, directory picking, secure storage, and in-app web windows are in the desktop shell.
Signed and notarized package in preparationAndroidPreview available
Moving through real-device verification.
The shared UI and preview package work today. Local SQLite, Keystore, and background refresh still need device validation.
Download ARM64 APK ↓iPhone · iPadIn development
The same reading logic, not another app.
The Tauri project and interface boundary are ready; database, background work, signing, and store validation remain.
Requires real devices and Apple Developer workflowWindowsIn development
No second UI implementation.
Windows reuses the React surface and local data model. A release awaits validation on the native toolchain.
Requires Windows build and signing validationA few honest answers
Clear boundaries before release.
How are Rinwa and Luma related?＋
Rinwa is the next-stage brand. The current application and preview package still say Luma. The migration will preserve bundle identity, backup formats, and secure-storage compatibility.
Do I need Rinwa Sync?＋
No. A single-device library works locally with SQLite. Sync starts only after you attach a server, and only covered data classes exchange operations.
Where do translation and chat send article text?＋
Only to the provider you configure, and only after explicit data-sharing consent. A self-hosted OpenAI-compatible proxy is supported.
Is it ready to replace my daily reader?＋
macOS is the primary quality target, but the product is still a development preview. Start with a subset of feeds and keep your current reader nearby; OPML export and backups are available.
Rinwa · 页间