Local first
chrome.storage.local with unlimitedStorage holds every page
and note — that's the source of truth, and it has no practical ceiling.
chrome.storage.sync sits downstream as a replication channel, not a store.
That inversion is the reason a note is never turned away.
One key per note
The browser merges sync data key by key, so two devices editing different notes both keep
their edits. A single array under one key would make every save a whole-list overwrite,
and the last device to sync would quietly erase the other's work.
Reconciled, not queued
On every change EasyNotes computes what sync should hold and pushes the
difference. A failed write needs no retry bookkeeping — the next change simply
computes the same difference again.
What fits in sync
Browsers allow an extension 102,400 bytes. Page structure always travels; notes then
fill what's left, newest first across every page. Measured against the real quota:
| Average note | Reaches sync |
|---|
| 40 characters | 479 notes |
| 100 characters | 479 notes |
| 280 characters | 280 notes |
| 500 characters | 173 notes |
| 2,000 characters (max) | 48 notes |
Anything past that stays on the machine that wrote it, marked with a circle in the
margin. Nothing is dropped, and deleting newer notes promotes older ones back up.
EasyNotes
