0.11.8 — the tally in the bar

Since 0.11.4 a reader gets a mark for finishing an entry: it floats above the text, lasts two seconds and fades. Until today that was all of it. The record went into the database and stayed there — there was no way to look at it afterwards.

**A reward you cannot look at is a reward for one moment only.** This version adds three things: a mark with a number in the header bar, a dot beside it when something new has arrived, and a list behind a click — what for and when, with a link to the entry.

**The dot carries no digit, and the number carries no dot.** These are two different pieces of information, and merging them into one element ends with a circle holding a two-digit number that pushes the bar apart on a phone. The number beside the mark says how much there is altogether. The dot only says “take a look”, and goes out once you have.

**The seen marker lives in the database, not in browser storage.** Browser storage can be edited from the console in fifteen seconds, and a state that can be changed from outside is not a state but a suggestion. The same rule already governs the marks themselves: the server grants them, from its own timestamps.

**The entry title is not stored alongside the mark.** The database holds the key — the same one across every language version. Title and address are worked out by the instance, at home, when it answers. Had the title gone into the database, changing it would have broken the list, and the English version would be showing Polish sentences.

An entry the author later hid stays on the list with its date and without a link. The mark was granted honestly and does not disappear because someone rearranged the content.

The list hands out fifty items at a time, more on request. Paging follows the timestamp of the last item rather than a page number — between one request and the next a new mark may arrive and shift the whole numbering.