Repository navigation
A bookmark you keep on one computer is on the others.
0.4.7 shipped the plumbing that carries browser settings and bookmarks between
your computers and the bars that draw them, but nothing a person did reached it:
the console kept bookmarks in its own storage. This release closes that, so the
sentence the last two release notes had to take back is true now.
Changed
- Bookmarks follow the account. The star writes to the rows the daemon keeps
on disk, which is the store the sync note reads, so a page kept on this
computer appears on the account's other computers and comes back if you keep it
again. Removing a bookmark removes it everywhere: the deletion travels as its
own row, so a computer that was switched off cannot bring it back. - A computer that was reset catches up. A device whose browser store started
again used to have every note it sent ignored, silently, because its sequence
began at one again. A note now says which run it came from, and the receiver
reads it rather than skipping it. - The bar tells you when it is a memory. If the daemon refuses a bookmark
write or does not answer in time, the row goes back and the bar says the list
is what this window last saw, instead of showing a save that never happened.
Known
- Your reading history, cookies and the tabs to restore stay on the computer that
made them. They are not part of the account. - Browser settings have the same plumbing and nothing in the console writes
them yet, so in practice they do not travel: only bookmarks do. - An installed app still does not look for a newer version. Moving to a newer
release means running a newer installer over it, oropenremote --updateif
you installed through npm.