One reader. Every device.
翻译准备中
取自仓库 README
正在加载完整 README。
查看完整 README ↗One reader. Every device.
A local-first, cross-platform RSS reader
🌐 Website: https://keryx.merc.works
| Platform | Requirements | Get it |
|---|---|---|
| Windows | x86_64 | .msi / portable ZIP from the Releases page |
| macOS (native app) | macOS 14 (Sonoma) or later on Apple Silicon | .dmg from the Releases page |
| Linux | x86_64 / arm64 | Snap Store, or .deb / .rpm / portable ZIP from the Releases page |
| Android | Android 8.0 or later | F-Droid, or .apk from the Releases page |
iOS/iPadOS support is planned. The F-Droid build has no Google Drive sync (Dropbox and OneDrive work as usual).
[!IMPORTANT] Windows: Until a code-signing certificate is in place, the
.msiis unsigned, so Windows SmartScreen shows a "Windows protected your PC" warning on first run. Click "More info", then "Run anyway" to continue.Android: if you install from F-Droid, no extra steps are needed. The
.apkfrom the Releases page is distributed directly (sideloaded), so Android will ask you to allow installing from this source the first time you install it from the app you used to open it (e.g. your file manager or browser).
Once Keryx is running, it can check for, download, and install newer releases on its own — from the notification bell, the task tray, or Settings → Updates (on macOS, from Keryx → Check for Updates… in the menu bar, or automatically, as set in Settings → General). The Windows and Android steps above are therefore only needed for the first install: an update Keryx downloads itself is not a browser download, so it never triggers Windows SmartScreen's "unsigned file" prompt, and on Android the "allow installing from this source" permission is granted only once, not on every update.
In-app updates work for the macOS app, a Windows .msi/portable install, a Linux portable install,
and an Android .apk from the Releases page. A Linux .deb/.rpm or Snap install instead opens the
release page — Keryx still tells you a new version exists, just not by installing it itself there.
Update a .deb/.rpm install through your package manager; a Snap install is updated automatically
by the Snap Store, so there is nothing to download from that page. The F-Droid build leaves updates
entirely to the F-Droid client, so it has no in-app update at all.