Skip to content

Droppen v0.2.128

Choose a tag to compare

@github-actions github-actions released this 23 Oct 07:24
· 532 commits to main since this release
Immutable release. Only release title and notes can be modified.
e9c7853

Droppen v0.2.128: the server for macOS (Apple silicon and Intel) and Linux.

On a Mac, the Droppen desktop App (Droppen-<version>.dmg, when it is attached
to a release) is the recommended way for everyday use. The files below are the
server, for running Droppen in the background or on a device with no screen.
Install or upgrade it, and add the device to your account with a one-time code
(on droppen.app: my devices → add a device that runs AI → show a one-time code):

curl -fsSL https://droppen.app/install.sh | DROPPEN_CODE=<code> sh

Or download the tarball for your device, check it against SHA256SUMS
(shasum -a 256 -c --ignore-missing SHA256SUMS, or sha256sum -c --ignore-missing SHA256SUMS),
and follow INSTALL.txt. The server is droppen; remote-hand-server is the
same program under its old name, which the installed service keeps.

file for
droppen-v0.2.128-macos-aarch64.tar.gz Apple silicon
droppen-v0.2.128-macos-x86_64.tar.gz Intel Mac
droppen-v0.2.128-macos-universal.tar.gz either Mac
droppen-v0.2.128-linux-x86_64.tar.gz Linux x86_64, glibc 2.28+
droppen-v0.2.128-linux-aarch64.tar.gz Linux aarch64, glibc 2.28+
remote-hand-v0.2.128-macos-{aarch64,x86_64,universal}.tar.gz and remote-hand-v0.2.128-linux-{x86_64,aarch64}.tar.gz the same server under its old name only, for older copies of the installer (on every release until at least 2027-01-31)
install.sh the installer above (https://droppen.app/install.sh redirects to the latest release's)
INSTALL-macos.txt, INSTALL-linux.txt installing by hand (each tarball has its own INSTALL.txt)
LICENSE Droppen's licence: AGPL-3.0-only
THIRD_PARTY_NOTICES the third-party software in the server, with its licences
web-manifest.json the embedded web app's files and digest
droppen-v0.2.128.sigstore.json, web-manifest.sigstore.json the build provenance attestations: every file here was built by this repository's release workflow from the commit below. Check one with gh attestation verify <file> --repo getdroppen/droppen --signer-workflow getdroppen/droppen/.github/workflows/release.yml --source-ref refs/tags/v0.2.128

Droppen is licensed under AGPL-3.0-only. The source of this release is
https://github.com/getdroppen/droppen/tree/e9c785337ca6ef63eefa656b1b6e155db1bf5777.

Copyright (C) 2026 Kilerd

Built from commit e9c785337ca6ef63eefa656b1b6e155db1bf5777 (server 0.2.128+ge9c7853).

Droppen App for macOS

Droppen-0.2.128.dmg — the desktop app (Apple silicon and Intel), signed with Developer ID and notarised by Apple. It needs macOS 13 or later. Open the DMG, drag Droppen to Applications, open it.

Droppen 0.2.127 updates itself to this release: it downloads it in the background and installs it the next time you quit, or at once with Restart to Update. Droppen 0.2.125 and 0.2.126 update themselves in two steps: first to 0.2.127, which https://github.com/getdroppen/releases (where they look for updates, now archived) still offers, then from 0.2.127 to this release. Version 0.2.124 and older do not update themselves: download this DMG once and replace the app in Applications.

macOS 版 Droppen App

Droppen-0.2.128.dmg 是桌面 App(Apple 芯片和 Intel 芯片的 Mac 都能用),使用 Developer ID 签名并经过 Apple 公证,需要 macOS 13 或更高版本。打开 DMG,把 Droppen 拖到「应用程序」,然后打开它。

0.2.127 会自动更新到这个版本:在后台下载,并在你下次退出时安装;也可以用「重启以更新」立即安装。0.2.125 和 0.2.126 会分两步自动更新:先更新到 0.2.127(它们检查更新的 https://github.com/getdroppen/releases 已归档,但仍提供 0.2.127),再从 0.2.127 更新到这个版本。0.2.124 及更早的版本不会自动更新:请手动下载一次这个 DMG,替换「应用程序」里的 Droppen。

What's new in v0.2.128

Renewing a device's identity key, in testing

  • A renewal that cannot start says whose confirmation it waits for. A device that runs AI renews its identity key only once another of your full devices has confirmed the account's latest change; the confirmation of the page that asks counts only when it is the account's only full device. Choosing the renewal setting is such a change, so in an account with two full devices the first renewal failed, with "found no recent word on its chain head". It now says "it waits for another of your full devices to confirm the account's latest change: open Droppen on …, then try again", and names those devices.
  • The device's other reasons for refusing get messages of their own: it is still catching up with the account's latest changes (Droppen tries again by itself); it sees the account's devices differently from what your full devices confirmed, so nothing was changed (Droppen does not try again: look at Droppen on that device itself); or it takes no control from this device now (open Droppen on another of your full devices and try again, or renew it from there). Its row in My devices gives these reasons in the page's language (English, Chinese or Japanese), not in English only.
  • Reloading the page during a renewal no longer leaves it stuck. Only the page that asked for a renewal can check the device's answer, and that page kept what it needed in its memory only. If it was reloaded, closed or crashed in the renewal's window of about two minutes, nobody could finish the renewal: other pages showed it as "renewing its identity key…", and only ten minutes after the window did a page withdraw it and start again. The asking page now keeps the attempt in this browser, sealed with the browser's own key as its other keys are (the renewal's one-time key is never kept), and the next page of the same browser finishes it: it checks the device's answer again and writes it, or, if the answer had not been checked yet, withdraws the attempt at once and asks again. Another tab of the same browser that is still on it is left alone.
  • A renewal left by a page of another browser, or by a browser without Web Locks, is still withdrawn ten minutes after its window and started again, and now on time: an open page of any of your full devices wakes for it by itself instead of waiting for something else to happen on the page.
  • droppen.app/security says renewal is switched on, in testing. Its section on renewing identity keys said renewal was not live yet. It now says Droppen Hub at droppen.app has switched it on for early testing, and what a test there showed; the other places on the page that called it "not live" say "in testing".

How releases are made

  • Releases now need a single approval and are built faster, and pull requests from outside the project run CI only after an automated security review of the change.

v0.2.128 更新内容

更换设备身份密钥(测试中)

  • 无法开始的更换,会说明在等谁的确认。 可运行 AI 的设备只有在你的另一台完整设备确认过账户的最新变更后,才会更换身份密钥;发起更换的页面自己的确认,只在它是账户唯一的完整设备时才算数。选择更换设置本身就是这样一次变更,所以在有两台完整设备的账户里,第一次更换会失败,提示「found no recent word on its chain head」。现在它会说「它在等你的另一台完整设备确认账户的最新变更:请在 … 上打开 Droppen,然后重试」,并列出这些设备。
  • 设备拒绝更换的其它原因也各有说明:它还在同步账户的最新变更(Droppen 会自己重试);它看到的账户设备与你的完整设备确认的不一致,所以没有做任何更改(Droppen 不会重试:请在那台设备本身查看 Droppen);或者它现在不接受这台设备的控制(请在你的另一台完整设备上打开 Droppen 再试,或直接从那台设备更换)。「我的设备」里它的那一行会用页面的语言(英文、中文或日文)说明这些原因,而不是只用英文。
  • 更换期间刷新页面,不会再让更换卡住。 只有发起更换的页面能核对设备的回答,而它所需的东西只存在自己的内存里。如果这个页面在大约两分钟的更换窗口内被刷新、关闭或崩溃,就没有谁能完成这次更换:其它页面显示「正在更换身份密钥…」,要到窗口关上十分钟后,才会有页面撤回它并重新开始。现在发起的页面会把这次尝试保存在本浏览器里,像浏览器的其它钥匙一样用它自己的钥匙封存(这次更换的一次性钥匙从不保存),由同一浏览器的下一个页面完成:它再次核对设备的回答并写下;如果回答还没核对过,就立即撤回这次尝试并重新发起。同一浏览器里仍在处理它的另一个标签页不会被打扰。
  • 由另一个浏览器的页面、或不支持 Web Locks 的浏览器留下的更换,仍在窗口关上十分钟后撤回并重新开始,而且现在会准时:你任何一台完整设备上打开着的页面会自己醒来处理,而不是等页面上发生别的事情。
  • droppen.app/security 写明更换功能已打开,处于测试中。 页面上讲身份密钥更换的一节以前写的是尚未启用。现在写明 Droppen Hub 已在 droppen.app 上把它打开,供早期测试使用,以及在那里测试的结果;页面上其它说它「尚未启用」的地方都改成了「测试中」。

发布方式

  • 现在发布一个版本只需批准一次,构建也更快;来自项目外部的拉取请求,要先通过一次自动安全审查,才会运行 CI。