• v0.3.0 ce666c768e

    Import, keywords, and the detail stage
    Build and test / Desktop (Linux) (push) Failing after 28s
    Build and test / Layer separation (push) Successful in 27s
    Traceability / Requirement traces (push) Successful in 25s
    🐳 Android image / Build and push (push) Successful in 1s
    Build and test / android-image (push) Successful in 1s
    Build and test / Android (aarch64) (push) Failing after 9m49s

    dtourolle released this 2026-08-22 18:55:04 +00:00

    Photographs now get into the library without a file manager. A card is read,
    its photographs are recognised against what the library already holds so a
    second insertion is not a second copy, and what is new goes up into dated
    folders on the server — with the import page saying plainly where they will
    land. Their thumbnails are made from the bytes still in hand rather than
    fetched back out of the server a minute later.

    Keywords arrive as a whole: put one on a photograph, type one in the library,
    and keep both devices' keywords when two catalogs meet.

    The develop pipeline gains its detail stage — capture sharpening through a
    separable unsharp mask, clarity, texture, and noise reduction — ordered so the
    repair runs before the enhancements rather than sharpening noise into place.
    Neighbourhood operations are kept out of a mask layer's chain, where they have
    no defined neighbourhood to read. The tone curve now takes a curve per colour
    channel, and an export carries the copyright while dropping the GPS.

    A library can also be thumbnailed in one pass on request, from the settings
    page, with the shards sent to the server afterwards so a second device inherits
    the result instead of spending an hour deriving it again.

    Known, and not fixed here: collections do not cross between devices. Their
    membership merges on a content hash that a scan never computes, so the join
    matches nothing on exactly the scanned remote libraries this application is
    built for. The catalog schema also moves 5 to 6 in this release, and a client
    on an older build refuses a newer catalog with only a log line to show for it.
    Both are the next thing to be fixed.

    Verified: 1,727 tests across 44 suites.

    Downloads