keeper 0.5.0

keeper 0.5.0

nothing about your archives changes. an existing .keeper folder is read and
written exactly as 0.4.3 left it, tags, placements and trays included, and
0.4.3 can open a folder 0.5.0 has touched. an installed keeper can update
itself to this one from inside its own window.

on a mac, two lines and no warning:

curl -L -o ~/Downloads/keeper.tar.gz https://github.com/gntrs/keeper/releases/latest/download/keeper-macos-arm64.tar.gz
tar -xzf ~/Downloads/keeper.tar.gz -C /Applications

on windows, run keeper-0.5.0-windows-x64-setup.exe and open keeper from
the start menu.

against 0.4.3

	0.4.3	0.5.0
what a new machine gets	one sentence along the bottom	eight cards over your own archive
what an existing keeper gets on update	nothing	one card, two buttons, no thanks or show me
where the answer is remembered	the browser, and a browser remembers it per port	keeper's own file, once per machine
settings you can change later	the click sound	the click sound, auto advance, whether keeper may look at github, and the walkthrough again
where the settings live	one button in the shortcuts sheet	a second pane behind the same ?
ways onto a mac	the disk image	the disk image, or a tarball and two lines
what the mac warns you	the developer cannot be verified	nothing, if you used the two lines
mac download	51 mb disk image	52 mb disk image, 47 mb tarball
windows installer	31 mb	31 mb
the page itself	433 kb of js, css and html	456 kb
shortcuts	30 rows on one sheet	30 rows on one sheet
what leaves your machine	nothing you did not ask for	nothing you did not ask for

what we did not have, and now do

a first run that shows the keyboard instead of mentioning it. 0.4.3 put one
sentence along the bottom of the screen saying that letters tag and ? has the
rest. that sentence was true and it was not enough. keeper's whole argument is
that a thousand frames is twenty minutes with one hand, and somebody who has
not read the readme sits down, sees tiles, and clicks, because clicking is what
an unlabelled page teaches. eight cards now walk the room in the order the day
happens in: look, keep, tag, set aside, pile up, cut to shape. the app stays
live underneath them and nothing is blocked, so every key a card names can be
pressed the moment it is named, and pressing it moves the card on.

and it asks first if you already use keeper. a machine that has never run
keeper gets the cards, because a first run has nothing to interrupt and a wall
of unlabelled tiles is the whole problem. a machine that has run keeper before
gets one card with two buttons instead. updating and being immediately taught
your own tool is a bad way to be thanked for updating, and no is an answer that
is written down. keeper works out which one you are from what its own file said
before this launch touched it, so a first run and a hundredth cannot be
confused five seconds in.

the answer records which walkthrough you saw and not merely that you saw one, so
a later keeper with something genuinely new to show can ask once more. it will
not fire on a fix or on a version number moving: the number only goes up when
the cards do.

a settings pane, on the key people already press. the sound switch used to
be the only preference keeper had a home for. auto advance lived in the bar,
and whether keeper may check github could be answered exactly once, on a card
that never came back, so anybody who changed their mind had nowhere to go. all
four are one pane now, behind the same ? as the shortcuts, each written as
what it does to your machine rather than as its own name.

the walkthrough is remembered per machine and not per browser tab. the old
one wrote its bit into the browser's storage, and a browser keys storage to an
origin, and keeper's origin carries a port. keeper app takes the first free
port from 7777 upwards, so opening keeper on a day when something else held
7777 handed you a different origin with an empty store and started the first
run again. it is one line in the same file keeper already uses to remember
which archive you had open.

a mac install that never meets gatekeeper. this is the one worth reading if
you gave up on keeper before. a disk image a browser downloaded is quarantined,
macos carries that mark into the app inside it, and the first open of an app
carrying it that nobody has paid apple to notarise is refused. there is a way
through and it is four clicks deep in system settings, past a sentence saying
the developer cannot be verified, which is where most people stop. curl
writes no such mark, because a file you fetched with a command you typed is
treated as something you chose. so the same app, the same ad hoc signature, the
same bytes, also ships as a plain tarball, and the two lines at the top of this
note are the install that works today. the disk image is still there and still
works, and it still argues with you once.

a written list of what keeper is being pointed at. film cropped and trimmed
the way the photographs already are, more inside the crop than one per shape, a
size for youtube, and an export that goes where it is going instead of into a
folder you then open somewhere else. it is in the readme under "what is
coming", with no dates on it, so you can tell whether the thing you need is on
the list or not on it at all.

what got more expensive

the page carries 23 kb more javascript and css, 433 to 456. it is served off
a socket on your own machine, so this is a number rather than a wait, but it is
23 kb that did not exist.

return is taken off the shelf while the walkthrough is up. a card with a
primary button answers to return, and it has to win against the shelf, which
answers a bare return by opening the quick look. it costs nothing, because
return on the shelf is the second way to do what space does and space is the
key the card in front of you is naming, but for those eight cards it is a key
the app no longer answers.

each mac release is about 100 mb bigger, because the tarball is a second
copy of the same app per architecture. that is the price of the two lines.

what we still do not have

no signature and no notarisation. the two lines above walk around a warning.
they are not a substitute for the money that would remove it, and they do not
make anything about this build more trustworthy than it was. the reasons to
trust it are unchanged: every line is in this repository, the downloads are
built by a workflow you can read, and every file has a checksum beside it.

nothing in this release has been run on real windows. the walkthrough and
the settings are the same code on both machines and the keys are named in the
words a pc keyboard uses, which was checked by making the page believe it was
on one. that is not the same as a windows laptop having opened it.

the walkthrough does not know what you already know. it is eight cards in
one order for everybody, and somebody who has used a culling tool before sits
through the same cards as somebody who has not. skip is one press and it is
remembered.

there is still nothing for film past the poster frame. keeper reads mov,
mp4, mkv and the rest and shows you a frame from each, and the bench crops
stills only.