Repository navigation
Mialuna 0.17.0 — Reliable story receipts, a Home that refreshes
Mialuna 0.17.0 — Reliable story receipts, a Home that refreshes
A fix-and-polish release. Story views no longer get lost, Home refreshes after your phone has slept and scrolls more smoothly, and you can switch off new-follower notifications if people spam you with follows.
Highlights
- Pull-to-refresh works after the phone has slept. Connections to relays often die silently in the background, and the refresh used to be sent into them and bring nothing back. Mialuna now checks a quiet relay before refreshing (and when the app returns to the foreground) and replaces a dead connection at once.
- Smoother scrolling in Home. Single-picture posts no longer sit in a carousel that competed with vertical scrolling, cards keep their real shape instead of jumping when they scroll back into view, and cards that did not change are no longer rebuilt every time a page of posts arrives.
- Show new followers (Settings). Off, new followers no longer appear in Notifications, the bell's count or on the phone. Likes, comments and zaps still do. On by default.
- Home follows who you follow. Replacing one followed account with another used to leave Home (and the story rail) showing the old people.
Story views and Stories
- No more lost views. A story view receipt is delivered only once the author's inbox relay accepted it. Otherwise it waits in a small on-device outbox (a story id and the author's key, for at most 24 hours) and is retried with growing pauses. Amber and bunker signers are never prompted in the background.
- Turning receipts off really stops them. Receipts still waiting are discarded immediately, and a restart does not bring them back. A receipt a relay already accepted cannot be taken back.
- More than 30 stories to one author are now sent in further messages instead of being cut at 30.
- A story counts as watched only once it was really shown: not when a picture failed to load, not when you swipe past it, not while it is held, in the background or buffering.
- Watched stories are remembered per account (they used to be shared by every account on the phone).
- Stories disappear after 24 hours even when their expiration tag is missing, malformed or far in the future, and while the app stays open.
- Only receipts for your own live stories are counted, within bounded memory; anybody could previously name any story id.
- A new story starts clean: no caption or sensitive-content flag from the last one, and a story's caption no longer overwrites your post draft.
Privacy and robustness
- Receipts and queues are bound to the account that watched; an account switch or sign-out cannot have them signed, sent or written for someone else, and it can no longer carry a signer refusal or a "follow list loaded" signal over to the next account.
- The private inbox now remembers every wrap it has opened, so a session that only received story receipts or close-friends content does not decrypt them again at the next start (a signer prompt each with Amber).
- PRIVACY.md, the Nostr compatibility notes and the in-app setting text describe the new behaviour (English and Italian).
The full audit — every finding, the tests that reproduce it and the risks left open — is in docs/BUGFIX_AUDIT.md.
Install on Android
- Download
mialuna-0.17.0.apkfrom the release assets. - Open the APK on a device running Android 7.0 or later and allow installation from your browser or file manager if Android asks you to.
- It is signed with the same key as 0.16.0, so it installs over it and keeps your data. Do not uninstall the old version first.
The APK includes arm64-v8a, armeabi-v7a and x86_64 native libraries. It is signed with Mialuna's release key.
Verification
Built with Flutter 3.44.3 and Dart 3.12.2 (the repository pins 3.47.9, which was not available on the build machine). The source passed static analysis and all 805 automated tests. The APK's signature was verified with apksigner; it has not yet been launched on a device or emulator, and the Amber/bunker prompts, video playback counting and background/foreground behaviour still need a check on real hardware (see the audit, section F).
- APK SHA-256:
833263a73c5cb1b16d85845a033422b8ff4e9c11206694ab1e62f0a8b0932f18 - Signing certificate SHA-256:
5F:E4:44:55:43:21:44:8B:FA:7B:EB:FD:EF:F8:0E:84:1C:08:6D:80:91:59:A5:9A:82:B2:AA:EE:EE:D0:37:50(the same as 0.16.0)
Full changelog: CHANGELOG.md