Building Synapse offline-first with Loro
July 24, 2026 Building Synapse offline-first with Loro Synapse is a study app: courses, annotated PDFs, generated exercises, a lexicon of notions. I wanted it to work on a train with no signal (a thing that I’ve been doing a lot lately), to be able to edit and make changes on a phone as well as on a laptop, and to keep those in sync without anyone having to run a server for it. This is mostly the reason the whole data layer looks the way it does.
- ▪July 24, 2026 Building Synapse offline-first with Loro Synapse is a study app: courses, annotated PDFs, generated exercises, a lexicon of notions.
- ▪I wanted it to work on a train with no signal (a thing that I’ve been doing a lot lately), to be able to edit and make changes on a phone as well as on a laptop, and to keep those in sync without anyone having to run a server for it.
- ▪This is mostly the reason the whole data layer looks the way it does.
Hacker News (Newest) files mainly under programming. We currently carry 5,306 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Tngl |
| Canonical URL | https://dhovart.tngl.sh/synapse-blog/loro-offline-first/ |
| Publication time | Sun, 26 Jul 2026 10:07:39 +0000 |
| Retrieval time | 2026-07-26T10:34:30.581Z |
| Last seen | 2026-07-26T10:34:30.581Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | GO3dA3xVOo9u |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
July 24, 2026 Building Synapse offline-first with Loro Synapse is a study app: courses, annotated PDFs, generated exercises, a lexicon of notions. I wanted it to work on a train with no signal (a thing that I’ve been doing a lot lately), to be able to edit and make changes on a phone as well as on a laptop, and to keep those in sync without anyone having to run a server for it. This is mostly the reason the whole data layer looks the way it does. An application is usually built using a database on a server and a client that talks to it over HTTP. There is nothing wrong with that, but it makes “offline” something you have to retrofit in later, usually the hard way, the same way multiple device sync is not a problem you can simply solve after the fact.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Tngl.
Discussion
0 commentsMore from Tngl
