Registro de cambios

2026-10-26 · Linux, Windows, Android

• Unsent attachments stay with their own conversation. Ending that conversation clears its selection without clearing other conversations. After this update, select previously unsent attachments again.

Changed

• Clear previously stored unsent attachment selections once when upgrading. Sent messages and the original files remain unchanged.

Fixed

• Keep unsent attachment selections tied to their conversation when groups are removed or reordered.
• Preserve selections in other conversations after deletion and restart.

For administrators

Compatibility

The server and message format are unchanged.

Network

No new network requests are introduced by this repair.

Data and privacy

Desktop clears attachment selection records without deleting original files. Android also removes obsolete copies created inside the app.

Security

Packages use the existing update signing key and Android installation certificate. The Windows installer has no paid operating-system code-signing certificate.

Installation

Install the package for your platform or use the existing in-app update flow. After upgrading, select previously unsent attachments again; sent messages are preserved.

Known issues

Desktop cleanup can remain incomplete if local storage rejects deletion. This exceptional case remains open.

Files

File	Bytes	SHA-256	Update signature
EMAPKA_0.3.36.apk	68,985,166	e82151d1ee7c2b15ebe4a861beb8121035f94c65b6c8119cea5db3f04732fc10	yes
EMAPKA_0.3.36_amd64.deb	12,728,884	fc6c6c15b2af4f5235bbbe45496987ad398a147b2c2441b0e05890589ce6da9a	yes
EMAPKA_0.3.36_x64-setup.exe	7,945,206	bae6b924e928c0e3fef69665bc322728c6f5f262adb9708f0dd9fa1f4efe580c	yes

2026-10-23 · Android, Linux, Windows

• On the phone, the update notice no longer appears over the locked screen. It appears after you enter the app.

Fixed

• On Android, the update card is not shown over the dead (re-entry) screen; it appears after a correct entry.

For administrators

Compatibility

The server is unchanged. Desktop code is unchanged; Linux and Windows are rebuilt only to keep one release version across platforms.

Network

No change.

Data and privacy

No change.

Security

Use the existing Android installation certificate and the existing update signing key. Windows retains its update signature and has no paid operating-system code-signing certificate.

Installation

Install through the existing signed update route. Retain the mandatory Linux transition from version 0.3.26 through 0.3.27.

Known issues

Only the Android update card display condition changed; update checks, timing, storage, dismiss and install are untouched.

Files

File	Bytes	SHA-256	Update signature
EMAPKA_0.3.35.apk	68,968,782	ffb857b4ec78e643f8c93cc34232155e8d2584526f6239ed0128c247afe219a0	yes
EMAPKA_0.3.35_amd64.deb	12,711,254	80dacd48533a83d78dd7dce54a4f86a281eaeefaade2b91626238aaef6157ac6	yes
EMAPKA_0.3.35_x64-setup.exe	7,915,778	eea7b2ea735c4eec4cdb56deba5e74f0caf35a5aacd5620493600feeda43047d	yes

2026-10-23 · Android, Linux, Windows

• Opening the app now checks for a new version after about thirty seconds, on the phone and on the computer, including when the window is opened from the tray. The update card appears without restarting the app.

Fixed

• Check for a new version about thirty seconds after every opening of the app on Android, not only once per app process.
• Check for a new version about thirty seconds after the desktop window is opened from the tray icon, by a second launch or from minimized.

For administrators

Compatibility

The server is unchanged.

Network

One small update request about thirty seconds after each opening of the app window, in addition to the ten-minute check while the app is open.

Data and privacy

No change. The update request carries only the language and the installed version.

Security

Use the existing Android installation certificate and the existing update signing key. Windows retains its update signature and has no paid operating-system code-signing certificate.

Installation

Install through the existing signed update route. Retain the mandatory Linux transition from version 0.3.26 through 0.3.27.

Known issues

Checked live: on an Android emulator and on Linux, opening the app again asked the site about thirty seconds later. The Windows installer was not run live; physical phones are not certified by these checks.

Files

File	Bytes	SHA-256	Update signature
EMAPKA_0.3.34.apk	68,968,782	8e7dbce70ff88341867537638d28c03715267877e4ae714ad1fd67d14f12b254	yes
EMAPKA_0.3.34_amd64.deb	12,704,200	429e1f0caea6f28b5d95b2b75345aec47d1483cdafd77008ad85991d8363614f	yes
EMAPKA_0.3.34_x64-setup.exe	7,908,811	fb1fe68acc0c6a9d17f5e3c19a728d3e81ba3af9047bd8a8c4c1372db87936a1	yes

2026-10-22 · Android, Linux, Windows

• The open app checks for updates every ten minutes, and the phone shows the update card on the re-entry screen. Unsent text and files stay after you leave or close the app. Files keep sending after you leave the chat, with progress from the start. A message counts as read only when it is on your screen. The menu shows the version.

Fixed

• An app left open learns about a new version within the hour: it checks every ten minutes plus a random pause of up to an hour, instead of once a day.
• A failed check no longer postpones the next one by a full period; the app retries after a minute and schedules the next check only after the site answers.
• On Android the update card is shown on the app's re-entry screen too; an incoming call still hides it.
• Show the installed version at the bottom of the menu and in About instead of the fixed v0.1.0.
• Keep files that were attached but not sent after leaving the conversation, closing the app or restarting the phone; the app keeps its own copy from the moment the file is chosen.
• Keep sending a file after leaving the conversation while it is still being prepared; the copy is removed only when the app no longer needs it.
• Move the file progress ring from the first encrypted part instead of standing at 0% and jumping at the end.
• Mark a message as read, show two checkmarks to the sender and start its disappearing timer only when the message is visible on screen, not when it arrives while the reader is looking at older messages.
• Translate the delete and disappearing-message options into Russian, Polish, Japanese, Belarusian and Spanish.

For administrators

Compatibility

The server is unchanged. A new local record type keeps partial read marks; older versions are not installed over newer ones.

Network

Each open copy requests a small update file every 10 minutes plus a random 0-60 minute delay, so copies do not arrive at the site in the same minute; a failed request is retried after 60 seconds.

Data and privacy

No change. The update request carries only the language and the installed version.

Security

Use the existing Android installation certificate and the existing update signing key. Windows retains its update signature and has no paid operating-system code-signing certificate.

Installation

Install through the existing signed update route. Retain the mandatory Linux transition from version 0.3.26 through 0.3.27.

Known issues

Checked live on two Android emulators and a desktop build against a test server: drafts and attached files survive leaving and closing the app, sending survives leaving the conversation, progress moves from the start, read marks and disappearing timers start only when a message is on screen. Physical phones, battery use and cellular networks are not certified by these checks. The Windows installer of this build was not run live.

Files

File	Bytes	SHA-256	Update signature
EMAPKA_0.3.33.apk	68,952,398	ce0c284fcc762fef44c7c98ee701003243f42c48a817a0e38a1c537044f87fe2	yes
EMAPKA_0.3.33_amd64.deb	12,715,848	b372ca13563d2640ede6437cf5af12531e5c1f34b6148a328b13337bc0dc9187	yes
EMAPKA_0.3.33_x64-setup.exe	7,925,701	c0fcb3adfbea909fc8284a80fdb34843acfe361709694da0913f4991a4204b21	yes

2026-10-22 · Android, Linux, Windows

• Delete messages for yourself or for both of you, and turn on disappearing messages: 10, 15 or 30 minutes after the other person opens them. Conversations open at the latest messages and load older ones as you scroll up. An open conversation no longer redraws the screen while nothing happens. Files keep the phone awake while they are sent, and the progress shows real encryption and upload. Calls in the conversation can be selected and deleted.

Added

• Delete selected regular messages and call lines for yourself or for both people; priority messages are never deleted this way.
• Disappearing messages per conversation from the menu: off, 10, 15 or 30 minutes after the recipient opens them, shown as a line in the conversation on both sides.

Changed

• Selection header: back arrow, Delete N and a checkbox to delete for the other person; Back, Escape and tapping outside cancel the selection.
• Files chosen for sending, including in the priority message window, stay inside the input frame and scroll there; the text field stays visible; file names can be renamed before sending.
• A file that is already being sent has no cancel cross or rename pencil; deleting the message stops the send.
• Call lines show a green or red handset and can be selected and deleted like messages.

Fixed

• Show the latest messages of a conversation instead of the first fifty, and load older messages when scrolling up.
• Stop redrawing an open, idle conversation several times a second on Android; the screen now updates only when something changes.
• Keep the phone awake while a file is encrypted and each part is uploaded, so a sleeping phone no longer turns a send into a long retry wait.
• Show file progress across encryption and upload instead of 0% until the upload starts.
• Apply an edit that arrives before its message, and apply an edit to the message that was chosen even if new messages arrive meanwhile.
• Keep files chosen for sending when leaving and reopening a conversation.
• Refuse a desktop file selection that the system file picker returned only partly, with a visible message.

For administrators

Compatibility

The server is unchanged. Delete-for-both and disappearing-message settings travel as new messages inside the existing encrypted conversation channel; version 0.3.31 and older ignore them, so their copies stay until they update.

Network

No new polling. Idle open conversations make no extra requests; pending deletions and settings wait in the existing send queue while offline.

Data and privacy

Deleted messages leave no text on the device: removal marks hold only author and message number, survive log compaction for 16 days, and compaction after a deletion rewrites the conversation log under a new random key and removes the old files. The server never stored readable messages.

Security

Use the existing Android installation certificate and the existing update signing key. Windows retains its update signature and has no paid operating-system code-signing certificate.

Installation

Install through the existing signed update route. Retain the mandatory Linux transition from version 0.3.26 through 0.3.27.

Known issues

Checked live on two Android emulators against a test server: an idle open conversation rendered 0 frames in 30 seconds, delete-for-both and a 10-minute disappearing message worked on both sides. Desktop screens were checked by the existing render tests; Linux and Windows were not run live. Physical phones, battery use and cellular networks are not certified by these checks. The full bridge test suite and Android instrumentation suites were not run.

Files

File	Bytes	SHA-256	Update signature
EMAPKA_0.3.32.apk	68,919,630	17bdbceb0c33fae7496ab95758799141e12c4ac767628a035bd396313184d444	yes
EMAPKA_0.3.32_amd64.deb	12,708,428	acec0d347462441aaf8986b1881d4b1dc108abe210948bc0412e8b9c61c5ca33	yes
EMAPKA_0.3.32_x64-setup.exe	7,899,947	5a4068b3b27c450bfcd3c449e4097af4b420627f7b2fe216a41686b07dba3bb4	yes

2026-10-21 · Android, Linux, Windows

• Conversations open at the latest message. Select, copy and share text, and edit your own messages and the names of files you sent. Every message shows its time; priority messages also show when they were read, on both sides. Calls appear in the conversation. Send up to ten files at once. In the priority message window, files wait for Send, and the window is kept after leaving the app or restarting the device.

Added

• Select, copy and share message text on Android; copy and select on desktop.
• Edit your own regular messages and the names of files you sent; the change appears in place for both people.
• Show the time on every message, day separators, and two ticks when a regular message was opened.
• Show when a priority message was read, on both sides.
• Show calls in the conversation: talked from–to, missed, declined and cancelled; each device records its own line.

Changed

• Report that a conversation was opened inside the encrypted message channel as a single value instead of a list of message numbers.
• Keep files added in the priority message window until Send or Cancel, and keep that window, its text and files after leaving the app or restarting the device.

Fixed

• Open conversations at the latest message and keep it visible above the keyboard.
• Show the update prompt centred and complete on desktop.
• Refuse a selection of more than ten files with a visible message instead of silently keeping the first ten.
• Show file sizes in the units of the selected language.

For administrators

Compatibility

The server is unchanged. Older clients ignore the new edit, opened and read-time messages: they keep the original text, and priority messages still turn green through the existing acknowledgement. Android, Linux and Windows packages use the same source revision.

Network

No polling or wake-ups are added. Edits and opened reports wait in the existing send queue while offline. Call lines are local and are not sent.

Data and privacy

Edits, opened reports and read times travel inside the existing encrypted message channel; the server does not see message numbers or text. Priority window files on Android are kept as private app copies and removed after Send or Cancel; on desktop the user's own file is referenced and never deleted.

Security

Use the existing Android installation certificate and the existing update signing key. Windows retains its update signature and has no paid operating-system code-signing certificate.

Installation

Install through the existing signed update route. Retain the mandatory Linux transition from version 0.3.26 through 0.3.27.

Known issues

Changes were verified live on two Android emulators and the Linux desktop app in a test container; Windows was not run. Physical devices, battery use and cellular networks are not certified by these checks. The full bridge test suite and Android instrumentation suites were not run for this release. A call answered on a device without a microphone is recorded as cancelled on that device and as declined on the caller's. These packages have not been approved for publication.

Files

File	Bytes	SHA-256	Update signature
EMAPKA_0.3.31.apk	68,624,718	f1173e1aa79f851d19518264b010cd32bde83b607fb48495e6c4e79b36985365	yes
EMAPKA_0.3.31_amd64.deb	12,646,664	c72817c6be2dafb0a300cfbfbe27e0120335508a8e7febca5c16949f8d413772	yes
EMAPKA_0.3.31_x64-setup.exe	7,870,218	0ff9a333474708d4814e48c3ee7cade7c86a3fa2fd1d01f11578b55ca8c3dc13	yes

2026-10-20 · Android, Linux, Windows

• On Android, tapping anywhere in the message field opens the keyboard — in conversations, in Channel +1 and in the priority message window.
• The screen turns off at your ear during a call. The caller hears ringback and a short busy tone.
• The phone wakes less often without a network, and a received message is not lost if the system closed the app.

Added

• Turn the screen off at the ear during outgoing dialing and conversation through the earpiece, using the Android proximity wake lock where supported.
• Play Android ringback after the recipient confirms ringing and stop it on answer or call termination; limit the busy tone to five seconds.

Changed

• Do not arm reconnect wake alarms while Android reports no network.
• Do not interrupt the one-minute message wait to retry a single group's mailbox proof.
• Back off persistent file errors exponentially up to 15 minutes.
• Keep one-minute message waiting and support mailbox subscriptions in batches of up to 64.

Fixed

• Start text input from any point of the visible message field frame in Android conversations, Channel +1 and the priority message window.
• Remove the durable incoming record only together with the relay acknowledgement, after the conversation is proven on disk, so a process killed in between does not lose the message; discard a redelivered message whose key was already used instead of blocking the mailbox.
• Ask for microphone access when the first call is answered from the notification while the app is open, as in 0.3.29.
• Check for an app update on each launch, as in 0.3.29, while keeping the rare background check.
• Recover Android background delivery using deadlines that include device sleep and bounded reconnection attempts.
• Keep background messages unread until the conversation is opened.
• Stop file transfers and retries of a participant who left the group.
• Handle already detached Android audio-choice windows safely when ending a call.

For administrators

Compatibility

Retain the existing server protocol, data formats and desktop interface. Android, Linux and Windows packages use the same source revision.

Network

Client message waiting remains one minute. The proxy TCP keepalive change (Caddy 2.11.7, keepalive_idle 2m) is a separate server operation and is not installed by these packages.

Data and privacy

Keep existing message encryption and local state ownership. No Google push service is introduced.

Security

Use the existing Android installation certificate and the existing update signing key. Windows retains its update signature and has no paid operating-system code-signing certificate.

Installation

Install through the existing signed update route. Retain the mandatory Linux transition from version 0.3.26 through 0.3.27.

Known issues

Checked on two emulators with a local relay. Screen-off at the ear, Samsung sleep and battery use, and cellular network changes require a physical phone. A server-requested file retry delay is not kept across an app restart. These packages have not been published.

Files

File	Bytes	SHA-256	Update signature
EMAPKA_0.3.30.apk	68,411,726	0ffb61ad0405f2dc20de7ed9d3cb97f59b63ac85410cf4edb65c9c5f8852c8ac	yes
EMAPKA_0.3.30_amd64.deb	12,569,110	65b6941d1e22ecc5b67d7edfc1a8dec6192f46fa099cb0a04b4a59a847f8f07b	yes
EMAPKA_0.3.30_x64-setup.exe	7,826,902	34287d00520271e5a8e46fda2dc0259e18e5d4a6d39f2dfd3390cbe3845c2224	yes

2026-10-17 · Android, Linux, Windows

• Scenario entry comes to Android, as on the computer: the app opens on an empty page, and the only way in is to repeat your scenario.
• Switch it on in Settings. Messages and calls keep arriving.

Added

• Add the reentry scenario screen on Android: when enabled in Settings, the app starts on a blank screen of 100 numbered slots and opens only after the saved sequence of taps and slot numbers.
• Lock the app interface on process start and when the app is swiped away from recent apps; pressing Home does not lock it.

For administrators

Compatibility

Built on the accepted 0.3.28 release for Android, Linux and Windows. Android adds the optional reentry scenario through the existing shared state owners. Desktop calling, tray, message shade and Linux installation through APT retain their accepted behavior.

Network

No server program, server configuration or database changes are required. No new network requests are added.

Data and privacy

The scenario is stored only on the device, inside the existing encrypted app state. No new diagnostic data is collected.

Security

While locked, message reception, notifications and calls keep working; only the screen is locked. Use the existing Android installation certificate and the existing update signing key.

Installation

Install using the existing signed update packages. The mandatory Desktop 0.3.26 to 0.3.27 transition remains unchanged before newer releases.

Known issues

Checked on the local test bench with two emulators and a local relay; this does not certify every physical device. Access recovery for a forgotten scenario is still under development.

Files

File	Bytes	SHA-256	Update signature
EMAPKA_0.3.29.apk	68,247,770	5db1c52e374b2291af90f5a6ab2bb0e0deb689ea2f79d2b881b99a0f2b2d3ed2	yes
EMAPKA_0.3.29_amd64.deb	12,558,868	e9573ea9a43a985456c10eaf1927becefe1d540e3142b376f717408d7795a568	yes
EMAPKA_0.3.29_x64-setup.exe	7,822,725	a37dfaee11467266d88f549d993dc73bab3add6402717e9b6b573cb2ec910e56	yes

2026-10-17 · Android, Linux, Windows

• The server signals new group mail over one connection instead of regularly polling every group.
• Linux and Windows gain voice calls, a system tray icon and message notifications.

Added

• Voice calling controls on Linux and Windows, including incoming calls while the app screen is locked after startup.
• A system tray icon on Linux and Windows. Closing the window keeps the app running; the tray menu can reopen it or quit.
• System message notifications on Linux and Windows when the window is not focused.

Changed

• Group mail now uses one server notification connection. The existing receiver continues to decrypt, save and acknowledge messages.

For administrators

Compatibility

The updated relay retains the existing delivery and acknowledgement paths for older clients. Application data formats and invitation rules are unchanged.

Network

The relay must be updated before these clients. Group mail notifications use authenticated HTTPS long polling; message delivery still uses the existing inbox.

Data and privacy

The new mail notification connection carries mailbox proofs and cell numbers, not message content. Existing encryption and acknowledgement processing remain in place.

Security

Packages retain the existing update signing key and Android installation certificate.

Installation

Linux version 0.3.26 first receives transitional version 0.3.27 through the normal update button, then 0.3.28. APT installs the required sound and tray libraries from configured repositories. Existing application data is retained.

Known issues

Repeating the same mailbox proof after a restart within the same second can return HTTP 401. Battery use, operating-system alert sound, microphone conversations and delivery to sleeping physical devices are not certified by the server checks. Windows has an update signature but no paid operating-system code-signing certificate.

Files

File	Bytes	SHA-256	Update signature
EMAPKA_0.3.28.apk	68,133,082	d6e1d11234321762e91429f9443069b8548f45282dd86dbac82040bf8e2570e3	yes
EMAPKA_0.3.28_amd64.deb	12,562,066	1484e739e5a88cb2789ae1ba2290bc7288dddaa88e8bb9647b84c7839d583d87	yes
EMAPKA_0.3.28_x64-setup.exe	7,819,208	46be9f796b3198a349e0365bcb1a15d71884b96408c21b8b21a6c7db0a4a4336	yes

2026-10-17 · Android, Linux, Windows

• A transitional release for Linux updates. The app uses APT to install updates together with their required system libraries and shows the reason if installation fails.

Changed

• Linux update installation uses APT to resolve system dependencies. The signed download and existing administrator authentication remain in place.
• Desktop installation errors show the system installer reason and leave the update button available.

For administrators

Compatibility

The Linux package has the same system dependencies as version 0.3.26. Android and Windows retain the 0.3.26 feature set.

Network

Desktop version 0.3.26 is directed to this transitional release before later full releases, including when users update later. Android continues to receive the latest release.

Data and privacy

Application data, installation identity and operating-system key storage are retained. No application data migration is introduced.

Security

Existing update signatures and the Android installation certificate are retained. APT uses configured system repositories; package scripts do not invoke APT.

Installation

Use the normal update button. Version 0.3.27 enables Linux dependency installation for the following full release. Administrative authentication uses the existing system mechanism.

Known issues

This transitional release does not include the new desktop calls, tray, message notifications or mail notification connection; these are in version 0.3.28.

Files

File	Bytes	SHA-256	Update signature
EMAPKA_0.3.27.apk	66,642,138	bf0782d21f456265faff6dc16bee522df4be27baf13d9e8de909fb9132766820	yes
EMAPKA_0.3.27_amd64.deb	8,614,104	28acee512ce67bd5f3927303940ddb4adfc2df72f3609dcacce0b11081cfae06	yes
EMAPKA_0.3.27_x64-setup.exe	5,522,206	3fde2aab63fe8a1ac2620392979ba9f04f9ad759791f4ca7b333f7dbc9f5991f	yes

2026-10-15 · Android, Linux, Windows

• Fix joining a group by invitation when the clock on the phone or computer is fast or slow.
• The app now takes the time from the server.

Fixed

• Take the time for invitation key validity from the relay server's responses instead of the device clock, so joining a group no longer fails when device clocks differ.

For administrators

Compatibility

Retain existing system requirements, network contracts and stored-data formats for Android, Linux and Windows. Invitation codes, group rules and Channel +1 rules remain unchanged.

Network

No server program, server configuration or database changes are required. No new network requests are added.

Data and privacy

No new diagnostic sensors, collected data or monitoring tools are added. The server time is kept in memory only.

Security

Use the existing Android installation certificate and the existing signing key for all update packages.

Installation

Install 0.3.26 through the existing update card or the official download page; existing user data is preserved.

Known issues

Joining with mismatched clocks was checked on the local test bench with two app instances and a local relay; this does not certify every physical device. Windows retains its existing update signature without introducing a new operating-system code-signing certificate.

Files

File	Bytes	SHA-256	Update signature
EMAPKA_0.3.26.apk	66,642,138	4a7af0332ccf53f54411db99b2c602325d076fea9038abcba25b3a6608b4b526	yes
EMAPKA_0.3.26_amd64.deb	8,604,080	3b6c463ea86979743b844d47377129f5d58ba56b3095cbcd198007a62531bbf0	yes
EMAPKA_0.3.26_x64-setup.exe	5,512,487	202ddcbe17e1d7d932855b0bae40b91f7e0c5be8f819d0cdfd7b4220196cbf43	yes

2026-10-13 · Android, Linux, Windows

• Fix Android freezes after repeated unsuccessful group and Channel +1 invitations.
• Show the invitation's actual remaining lifetime, including time away from the app.

Fixed

• Keep Android invitation waiting separate from user actions so repeated unsuccessful attempts do not block the controls.
• Read the Android invitation countdown for the displayed code without restarting its lifetime when the interface is recreated or the app resumes.

For administrators

Compatibility

Retain existing system requirements, network contracts and stored-data formats for Android, Linux and Windows. Invitation generation, saved codes and Channel +1 creation rules remain unchanged.

Network

No server program, server configuration or database changes are required.

Data and privacy

No new diagnostic sensors, collected data or monitoring tools are added.

Security

Use the existing Android installation certificate and the existing signing key for all update packages.

Installation

Install 0.3.25 through the existing update card or the official download page; existing user data is preserved.

Known issues

The invitation fixes were checked on the existing Android emulator bench; this does not certify every physical device. Windows retains its existing update signature without introducing a new operating-system code-signing certificate.

Files

File	Bytes	SHA-256	Update signature
EMAPKA_0.3.25.apk	66,609,370	67db6cef2d700c939d484eaddc287e574e521c399d28a6150b9f1c49efd8958e	yes
EMAPKA_0.3.25_amd64.deb	8,596,960	11f68ef9cf9b337fbcab97ddc9d61e634b98c95c366f292c30a31d9be721055a	yes
EMAPKA_0.3.25_x64-setup.exe	5,510,837	d3f8955039711e41ed87352dc024131f2e2394f814a57a038097475f506dcd9a	yes

2026-10-12 · Android, Linux, Windows

• Wake the Android screen for an incoming call and show Answer and Decline.
• Show the update card above any screen and menu on Android, Linux and Windows.

Fixed

• Wake the Android screen for an incoming call and present the caller with Answer and Decline actions.
• Explain missing incoming-call presentation access and open the relevant phone settings; allow closing the notice with Later, the close button, or an outside tap.
• Show the update card above application screens and open menus on Android, Linux and Windows, including desktop loading and locked-entry screens.

For administrators

Compatibility

Retain existing Android, Linux and Windows system requirements, network contracts and stored-data formats.

Network

Leave the server program, server configuration and database schema unchanged.

Data and privacy

Retain existing diagnostic consent without adding collected data or diagnostic sensors.

Security

Sign Android with the existing installation certificate and all update packages with the existing update signing key.

Installation

Install 0.3.24 through the existing update card or the official download page; existing user data is preserved.

Known issues

The Android presentation behavior was checked on the existing Android 14 emulator bench; this does not certify behavior on every physical device. Windows retains its existing update signature without a paid operating-system code-signing certificate.

Files

File	Bytes	SHA-256	Update signature
EMAPKA_0.3.24.apk	66,609,366	b96127038e7d5071e0ef1824a3302a24df7696d2e4f1d42b12fc31326b3afef6	yes
EMAPKA_0.3.24_amd64.deb	8,596,674	8c46554f88b1ff3d4879f9845f1e5197b050fa5c24f802f84f535cd649a751a3	yes
EMAPKA_0.3.24_x64-setup.exe	5,511,693	fe3716da8ac55d0ce9fa64c26bb6be6fe963ff965f2ba8686d8a82997e9a4d65	yes

2026-10-11 · Android, Linux, Windows

• Improved incoming-call presentation on Android with the screen off
• Update notices appear above application screens and menus

Fixed

• Coordinate Android Telecom permission and foreground-service readiness before presenting an incoming call.
• Avoid redundant reposting of the incoming call notification.
• Show the existing update card above application screens and menus on Android, Linux and Windows.
• Explain incoming-call channel and full-screen access settings when required.
• Label the published-call state as waiting for an answer instead of claiming the other phone is audibly ringing.

For administrators

Compatibility

Windows 10 21H2 or later (x86-64). Ubuntu 22.04 or later (x86-64). Android 8.0 or later (arm64-v8a, x86-64). Existing network contracts and stored data remain compatible.

Network

The server program, configuration, and database schema are unchanged.

Data and privacy

No new collected data or diagnostic sensors are introduced. Existing diagnostic consent remains in effect.

Security

Use the existing release signing keys. Android retains its existing installation signing certificate.

Installation

Install 0.3.23 through the existing update card or the official download page.

Known issues

The incoming-call presentation change passed the existing Android 14 emulator scenarios; the reported Samsung behavior still requires physical-device confirmation. Windows installers do not have a paid code-signing certificate.

Files

File	Bytes	SHA-256	Update signature
EMAPKA_0.3.23.apk	66,592,958	f3171263312fd92e9c3f2f28be82c552ac562cec5d324903bbfd8edd5a407bdd	yes
EMAPKA_0.3.23_amd64.deb	8,591,420	14652c6aabc4c43fa1f5798b31c1ec128af5299da09eb32cb73b86baa5219519	yes
EMAPKA_0.3.23_x64-setup.exe	5,508,133	0cb862b447c4b156b08ee18af95951fa4b0493a0eb037e1ef16031ca13864270	yes

2026-10-11 · Android, Linux, Windows

• Improved Android call startup after the phone sleeps
• Close a finished call message with its button, the cross, or a tap outside

Fixed

• Improve Android call startup after device sleep.
• Limit repeated call-signal delivery and stop obsolete attempts.
• Allow the finished-call message to close immediately using its button, cross, outside tap, or Back.

For administrators

Compatibility

Windows 10 21H2 or later (x86-64). Ubuntu 22.04 or later (x86-64). Android 8.0 or later (arm64-v8a, x86-64). Existing network contracts and stored data remain compatible.

Network

The server program, configuration, and database schema are unchanged.

Data and privacy

No new collected data or diagnostic sensors are introduced. Existing diagnostic consent remains in effect.

Security

Use the existing release signing keys. Android retains its existing installation signing certificate.

Installation

Install the common 0.3.22 release through the normal update card. Desktop packages retain existing functionality.

Known issues

Call behavior after prolonged sleep awaits confirmation on physical Android phones. Force-stopped apps do not have a push wake mechanism. Windows installers do not have a paid code-signing certificate.

Files

File	Bytes	SHA-256	Update signature
EMAPKA_0.3.22.apk	66,592,958	dba16c26d5c9a24625176d2ab32eb4b8948f8a12eb71fa4af0883c2d75ff4aea	yes
EMAPKA_0.3.22_amd64.deb	8,592,994	24fe0251fd642a5d1c32426cfb7e09cce0cf8d151c4fdbfbb43ca5e28046ac52	yes
EMAPKA_0.3.22_x64-setup.exe	5,505,822	a00ed526e09274177dd8b4fb237ee7020282478c5c5d2db389d9f1f28131bf21	yes

2026-10-08 · Android, Linux, Windows

• Improved Android calls: starting a call, showing incoming calls on the locked screen, stopping the ringtone after answering, and calling again
• Call windows now share the same appearance; both chats have a green handset button

Fixed

• Improve Android call startup and incoming call presentation on the locked screen.
• Stop the incoming ringtone when answering and improve repeated calls and call cleanup.
• Use a consistent appearance for call windows and a green handset button in both chats.
• Connect privacy-safe diagnostic call tracing to the existing diagnostic service.
• Update server call code and the diagnostic observer without a database schema migration.

For administrators

Compatibility

Windows 10 21H2 or later (x86-64). Ubuntu 22.04 or later (x86-64); package dependencies unchanged. Android 8.0 or later (arm64-v8a, x86-64).

Network

Server call code and the diagnostic observer are updated. No database schema migration is required. The server package is separate from Android, Linux, and Windows user installers.

Data and privacy

Privacy-safe diagnostic call tracing uses ephemeral call correlations and fixed event categories. It does not include conversation audio, message content, contact names, or original call identifiers. Android message notification content remains obfuscated.

Security

Use the existing release signing keys and verify installer signatures and checksums before deployment. Android updates must retain the existing installation signing key.

Installation

This package prepares the common 0.3.21 update for Android, Linux, and Windows. Existing installations receive published updates through the normal update card.

Known issues

Locked-screen presentation and repeated calls were checked on the existing Android emulator pair. Behavior on Samsung user phones and during Android Doze has not been confirmed. Force-stopped apps do not have a push wake mechanism. Windows installers do not have a paid code-signing certificate.

Files

File	Bytes	SHA-256	Update signature
EMAPKA_0.3.21.apk	66,478,266	48188ee3e92513e3f58c9c607ae02a58defb2bdbe9fd921b573738827922bff6	yes
EMAPKA_0.3.21_amd64.deb	8,588,832	c5a2fde868e00038df16945065fdfe8e7178787c5a57c440675b1ae394b00797	yes
EMAPKA_0.3.21_x64-setup.exe	5,505,148	e4c4fc09c758b1684954e4e0db401a0095cffdef82de824e6930c0ee11923353	yes

2026-10-08 · Windows, Linux, Android

• On the phone, call another person in the same group: the other phone rings with the usual ringtone, including on the lock screen
• On Android, new messages now reliably appear in the notification shade and clear after reading

Fixed

• Restore Android shade notices for ordinary and priority mail on phones that already have 0.3.19: the existing background receiver, start after boot, and separate channels.
• Issue the short-lived voice-path permission so a call in the group can connect.
• Store a mail packet that carries a delivery key.

For administrators

Compatibility

Windows 10 21H2 or later (x86-64). Ubuntu 22.04 or later (x86-64); package dependencies unchanged. Android 8.0 or later (arm64-v8a, x86-64).

Network

The mail server issues short-lived permissions for a voice path through the project's own TURN service. A mail packet that carries a delivery key is stored. Existing 0.3.18 and 0.3.19 clients keep sending and receiving mail. Voice envelopes are acknowledged and never appear as chat.

Data and privacy

Call signalling is sealed between the two phones. The mail server stores only short-lived delivery tickets, not audio, names, or group roster. Android notification title and body remain obfuscated.

Security

Updates are signed with the same Ed25519 (minisign) key D5ABFA97CEDEBABF; a version older than the installed one is never installed. The Android package is signed with the same installation key as 0.3.15–0.3.19.

Installation

Existing 0.3.19 installations receive this version through the card on the main screen. Fresh install — Windows, silent: EMAPKA_0.3.20_x64-setup.exe /S. Linux: sudo apt install ./EMAPKA_0.3.20_amd64.deb. Android: install EMAPKA_0.3.20.apk over 0.3.19.

Known issues

An incoming call reaches the phone only while the app process is alive; there is no push wake from a killed process. Two-phone live calls on user devices were not measured in this release. Installers are not signed with a paid Windows code-signing certificate.

Files

File	Bytes	SHA-256	Update signature
EMAPKA_0.3.20.apk	66,429,118	1276892819d33509336f099ddd0e8dc2f35014acafe4d63f52f189add68c80bf	yes
EMAPKA_0.3.20_amd64.deb	8,578,294	23b4226a5fac14b1dcd175605cf798b3b645a6d5ade3da3cf9f04f3fd02b5677	yes
EMAPKA_0.3.20_x64-setup.exe	5,491,867	2efe4eb46d940cb340334177d3d6bb3400e2a8f497eb19cd5d7f3c5b60845501	yes

2026-10-08 · Windows, Linux, Android

• On the phone, call another person in the same group: the other phone rings with the usual ringtone, including on the lock screen
• On the computer this version is the same as 0.3.18

Added

• Place a one-to-one voice call on Android from an existing conversation; the other phone uses the system ringtone and can answer or decline from the lock screen.
• Opening the incoming notification shows the call without answering; Answer and Decline stay separate actions.
• Show why a call ended: busy, declined, no answer, could not connect, or call ended.

For administrators

Compatibility

Windows 10 21H2 or later (x86-64). Ubuntu 22.04 or later (x86-64); package dependencies unchanged. Android 8.0 or later (arm64-v8a, x86-64).

Network

The mail server now also issues short-lived permissions for a voice path through the project's own TURN service. Existing 0.3.18 clients keep sending and receiving mail. Voice envelopes are acknowledged and never appear as chat.

Data and privacy

Call signalling is sealed between the two phones. The mail server stores only short-lived delivery tickets, not audio, names, or group roster. Android notification title and body remain obfuscated.

Security

Updates are signed with the same Ed25519 (minisign) key D5ABFA97CEDEBABF; a version older than the installed one is never installed. The Android package is signed with the same installation key as 0.3.15–0.3.18.

Installation

Existing 0.3.18 installations receive this version through the card on the main screen. Fresh install — Windows, silent: EMAPKA_0.3.19_x64-setup.exe /S. Linux: sudo apt install ./EMAPKA_0.3.19_amd64.deb. Android: install EMAPKA_0.3.19.apk over 0.3.18.

Known issues

An incoming call reaches the phone only while the app process is alive; there is no push wake from a killed process. Two-phone live calls on user devices were not measured in this release. Installers are not signed with a paid Windows code-signing certificate.

Files

File	Bytes	SHA-256	Update signature
EMAPKA_0.3.19.apk	66,378,530	26c5ab551475e46b94d750afde9bf6a4eb73bd00e179799088ef19e769414007	yes
EMAPKA_0.3.19_amd64.deb	8,572,704	62ce32864c68433e3dfa09feb6e90aec87a793ea0b72c42493de62787f92bff6	yes
EMAPKA_0.3.19_x64-setup.exe	5,495,658	b842230562d9f24837294e50edf3438757f5c041166cfaa0ac83907356542973	yes

2026-10-04 · Windows, Linux, Android

• On Android, new messages now reliably appear in the notification shade and clear after reading
• On all platforms, temporary server and network failures retry gradually without flooding the server

Fixed

• Drive Android notifications from successfully deduplicated and durably stored incoming messages instead of changes in the total unread count; reading or deleting another message no longer hides a new arrival, and old data restored after restart is not announced as new.
• Stop Android UI network loops when the activity is hidden and use the existing single background receiver; remove the separate polling loop and minute wake alarm.
• Serialize auth-token acquisition and apply capped exponential backoff with jitter to 429, 5xx and transport failures, honor Retry-After, and hold terminal rejections instead of retrying indefinitely.

For administrators

Compatibility

Windows 10 21H2 or later (x86-64). Ubuntu 22.04 or later (x86-64); package dependencies unchanged. Android 8.0 or later (arm64-v8a, x86-64).

Network

No server protocol or server binary change. Clients now coalesce concurrent auth-token requests, use capped exponential backoff with jitter, honor Retry-After, and do not run hidden Android UI polling.

Data and privacy

No change. Android notification title and body remain obfuscated.

Security

Updates are signed with the same Ed25519 (minisign) key D5ABFA97CEDEBABF; a version older than the installed one is never installed. The Android package is signed with the same installation key as 0.3.15–0.3.17.

Installation

Existing 0.3.17 installations receive this version through the card on the main screen. Fresh install — Windows, silent: EMAPKA_0.3.18_x64-setup.exe /S. Linux: sudo apt install ./EMAPKA_0.3.18_amd64.deb. Android: install EMAPKA_0.3.18.apk over 0.3.17.

Known issues

Installers are not signed with a paid Windows code-signing certificate. Android battery use and delivery during physical-device deep sleep were not measured on physical hardware.

Files

File	Bytes	SHA-256	Update signature
EMAPKA_0.3.18.apk	37,902,177	12bef65158070161feb68f8b04a74d8a6d459d7b2e2955d7494445edb5e42d5e	yes
EMAPKA_0.3.18_amd64.deb	8,486,862	38721de024cf1ef4d174774cf36101c31582ad5102543737e8b6a36e84ab34e8	yes
EMAPKA_0.3.18_x64-setup.exe	5,444,530	f812c2f2ed8421d820bb219c5feddbc860379f9f163dca8ceefbbe36753db59e	yes

2026-10-03 · Windows, Linux, Android

• On the phone, see the priority message and the Join button above the keyboard when entering a group or Channel +1
• On the computer this version is the same as 0.3.16

Fixed

• Keep the Android priority-message overlay above the keyboard so the text and send controls stay visible while typing.
• Keep the name field and Join on the Android join screens for a group and for Channel +1 reachable when the keyboard is open.

For administrators

Compatibility

Windows 10 21H2 or later (x86-64). Ubuntu 22.04 or later (x86-64); package dependencies unchanged since 0.3.2. Android 8.0 or later (arm64-v8a, x86-64).

Network

No change.

Data and privacy

No change.

Security

Updates are signed with the same Ed25519 (minisign) key D5ABFA97CEDEBABF; a version older than the installed one is never installed. The Android package is signed with the same installation key as 0.3.15 and 0.3.16.

Installation

Existing 0.3.16 installations receive this version through the card on the main screen. Fresh install — Windows, silent: EMAPKA_0.3.17_x64-setup.exe /S. Linux: sudo apt install ./EMAPKA_0.3.17_amd64.deb. Android: install EMAPKA_0.3.17.apk over 0.3.16.

Known issues

Installers are not signed with a paid code-signing certificate, so Windows warns on first manual installation.

Files

File	Bytes	SHA-256	Update signature
EMAPKA_0.3.17.apk	37,835,157	540b46588effd3e4396479a4bd44878b2604db0216372c898ea38627a9cbc45d	yes
EMAPKA_0.3.17_amd64.deb	8,330,436	fef7e8ee38fbeace463c2ceef73c5643b592a2a225a178ce838ade20a22d4f96	yes
EMAPKA_0.3.17_x64-setup.exe	5,441,951	030c9df91b41fd6e2eb873b89e79e48b1be38186ef71d025a8c8a220ea647a17	yes

2026-10-01 · Windows, Linux, Android

• Turn screen protection off with a checkbox in Settings — the app remembers your choice
• Return to where you left off: the app opens on the same screen with the menu already open
• See the same icon on Android as on the computer: a white E on a black square

Added

• Turn screen protection off and back on with a checkbox in Settings on Windows, Linux and Android. Protection is on by default, and the choice is kept after the app is closed.
• Open the app on the screen where it was closed, with the menu already open, once there is at least one group, membership or Channel +1. Back leads where it led before the app was closed. A first start without groups still opens the main screen with the menu closed.

Changed

• Show a white E on a black square as the Android app icon, matching the computer.

For administrators

Compatibility

Windows 10 21H2 or later (x86-64). Ubuntu 22.04 or later (x86-64); package dependencies unchanged since 0.3.2. Android 8.0 or later (arm64-v8a, x86-64).

Network

No change.

Data and privacy

Two more items are kept in the app's encrypted local data on the device: the screen protection choice and the last open screen. Nothing new leaves the device.

Security

Updates are signed with the same Ed25519 (minisign) key D5ABFA97CEDEBABF; a version older than the installed one is never installed. The Android package is signed with the same installation key as 0.3.15. Screen protection is on unless the person turns it off; Linux desktops do not support blocking screenshots, so there the checkbox has no system effect.

Installation

Existing desktop installations from 0.3.13 and Android 0.3.15 receive this version through the card on the main screen. Fresh install — Windows, silent: EMAPKA_0.3.16_x64-setup.exe /S. Linux: sudo apt install ./EMAPKA_0.3.16_amd64.deb. Android: install EMAPKA_0.3.16.apk over 0.3.15.

Known issues

Installers are not signed with a paid code-signing certificate, so Windows warns on first manual installation.

Files

File	Bytes	SHA-256	Update signature
EMAPKA_0.3.16.apk	37,835,153	5d47c28dbb5a79db3b0ea84eb7edde7b6736fd0bd8c528d93b49c2a47131e2fe	yes
EMAPKA_0.3.16_amd64.deb	8,331,704	79d841941d5ea0a01f37901f3b209fed9f0dddf37ae93b8bdfc080c29a6bfccd	yes
EMAPKA_0.3.16_x64-setup.exe	5,439,528	37c541d7d281972475cc679b30f04abe307032ccb4f417e7ee7aa27aea8280a5	yes

2026-09-23 · Windows, Linux

• See a new version right after you open the app, not a day later

Fixed

• Check for a new version at every app start, not only once a day: a version released during the day was previously shown only on the next day, and restarting the app or the computer did not help.

For administrators

Compatibility

Windows 10 21H2 or later (x86-64). Ubuntu 22.04 or later (x86-64); package dependencies unchanged since 0.3.2.

Network

One extra HTTPS GET to emapka.app/update/<language>.json per app start (about 1.5 KB). The daily check with a random offset stays for an app that is already open. Everything else unchanged.

Data and privacy

No change. The check carries only the app language and the installed version number.

Security

Updates are signed with the same Ed25519 (minisign) key D5ABFA97CEDEBABF; a version older than the installed one is never installed.

Installation

Existing 0.3.13 and 0.3.14 installations receive this version through the card on the main screen. Fresh install — Windows, silent: EMAPKA_0.3.15_x64-setup.exe /S. Linux: sudo apt install ./EMAPKA_0.3.15_amd64.deb.

Known issues

Installers are not signed with a paid code-signing certificate, so Windows warns on first manual installation.

Files

File	Bytes	SHA-256	Update signature
EMAPKA_0.3.15.apk	37,797,925	f9b4b858b01c4dbb63eded95daf59f12e34c2553475ab5d5b8fdc038ff85ab9b	yes
EMAPKA_0.3.15_amd64.deb	8,473,062	74f569e15f25637b064aeb0dd4f605b9776bd5324d01128a391b9f44f16e0b6e	yes
EMAPKA_0.3.15_x64-setup.exe	5,443,956	db9aa60822b3d2b2dc4089071a8ae2c28f46f7375f79dfcc1c64bb9e6da4ee10	yes

2026-09-23 · Windows, Linux

• Update the app from the card on the main screen — the first update that arrives by itself
• Keep working calmly when the connection drops: the app waits instead of hammering the server

Changed

• Deliver this version through the update card: the first release people receive without visiting the website.

Fixed

• Wait after losing the connection instead of asking the server for mail every fifth of a second.

For administrators

Compatibility

Windows 10 21H2 or later (x86-64). Ubuntu 22.04 or later (x86-64); package dependencies unchanged since 0.3.2.

Network

Unchanged since 0.3.13: a daily HTTPS GET to emapka.app/update/<language>.json, downloads from emapka.app/releases/<version>/, messages through relay.emapka.app, diagnostic logs to emapka.app/report only with consent. New: after a lost connection the app waits with a growing pause (1 s doubling to 60 s) before asking for mail again.

Data and privacy

No change. The update check carries only the app language and the installed version number.

Security

Updates are signed with the same Ed25519 (minisign) key D5ABFA97CEDEBABF; a version older than the installed one is never installed.

Installation

Existing 0.3.13 installations receive this version through the card on the main screen. Fresh install — Windows, silent: EMAPKA_0.3.14_x64-setup.exe /S. Linux: sudo apt install ./EMAPKA_0.3.14_amd64.deb.

Known issues

Installers are not signed with a paid code-signing certificate, so Windows warns on first manual installation.

Files

File	Bytes	SHA-256	Update signature
EMAPKA_0.3.14_amd64.deb	8,476,096	50dc0a4eede7690891f44ae3460dfaa1386d9229672cbd14213a463f06989152	yes
EMAPKA_0.3.14_x64-setup.exe	5,435,613	9f6ad3194469ca5101b9fe683d5703e73837208d4cc62f6daf50e06b92744ab6	yes

2026-09-20 · Windows, Linux

Changed

• Wait after a server refusal instead of retrying faster, and reuse connections to the server instead of opening a new one for each request.

Fixed

• Keep error reports from breaking their own pause after a refusal.

Security

• Fix a security issue in opening received files. Details will be published on 2026-10-20.

For administrators

Files

File	Bytes	SHA-256	Update signature
EMAPKA_0.3.12_amd64.deb	7,670,378	258ac685687669b3a03f25ba8cf34277c42ee97dcc5d244cb970b58ef056a311	no
EMAPKA_0.3.12_x64-setup.exe	4,878,055	a4c3e1c5ffedb1f22a1c128110cce1907eb76af83b36b6f39bf9e06fe336f1a0	no

2026-09-18 · Windows, Linux

Added

• Join a group by pointing the computer's camera at an invitation QR code, or by dropping a picture of the QR code onto the join screen. Typing the code by hand still works.

Changed

• Require a name before joining a group.

Fixed

• Say that an invitation no longer exists (revoked, expired or used) instead of reporting "no network".

For administrators

Files

File	Bytes	SHA-256	Update signature
EMAPKA_0.3.11_amd64.deb	7,668,260	af62d7ad91131ac18cc7f62a38d86b20b306a5adb5ce527642f041202574518a	no
EMAPKA_0.3.11_x64-setup.exe	4,880,883	07b7f2db42d027fe8544916749814300f3233b3cfd05f6e5ab45cb33271369fd	no

2026-09-16 · Windows, Linux

Fixed

• Open the app window fully inside the visible area of any monitor, centred and no larger than 420×760.

For administrators

Files

File	Bytes	SHA-256	Update signature
EMAPKA_0.3.10_amd64.deb	6,969,906	5c092163f4444578bbf3bebc3282305d2b79586e638a0431f91af43415b55b01	no
EMAPKA_0.3.10_x64-setup.exe	4,508,696	2f05484b1a2ceeeec47ecc8431233d9856b7e77cd64927657a2abe692fa36172	no

2026-09-15 · Windows, Linux

Fixed

• Send several messages in a row evenly, without asking the server for a new pass for every message.
• Stop reporting a busy server as "no network".
• Stop retrying delivery to a recipient whose mailbox no longer exists.

For administrators

Files

File	Bytes	SHA-256	Update signature
EMAPKA_0.3.9_amd64.deb	6,971,842	18faf8ebc64618ec17f909ad0e159c5f2117b7d17450aa75c1ad57189d60bc78	no
EMAPKA_0.3.9_x64-setup.exe	4,507,402	65b50734455d4b322fdb6e49d38fee13c6eb612c8ddb7e81d52ed0c2efbbea7c	no

2026-09-14 · Windows, Linux

Changed

• Show the whole conversation instead of the last fifty messages.
• Show new group members the names and pictures of everyone, including those who are offline.

Fixed

• Keep the app window inside a low screen by scaling it down.
• Keep the message field and the Send button visible when many documents are attached.
• Shorten long document names in the middle with an ellipsis.
• Accept a document dropped anywhere over the chat.

For administrators

Files

File	Bytes	SHA-256	Update signature
EMAPKA_0.3.8_amd64.deb	6,967,618	01f7bb24939fb8ab1b723efc017d730d876d5f30f5808059c85a1cba31833599	no
EMAPKA_0.3.8_x64-setup.exe	4,498,618	e5bac5c9bd2d7faab9867c67788ca9fd60b295c831a94618a7e3a67ea262cd5a	no

2026-09-12 · Windows, Linux

Changed

• Lock the app only when it starts, not when its window is minimised.

Fixed

• Work fully after entering through the start-up lock screen: connection, groups, invitations and Channel +1.

For administrators

Files

File	Bytes	SHA-256	Update signature
EMAPKA_0.3.7_amd64.deb	6,923,622	dde648b693d23fe9c98881211e951e5e0c0e3d108c656f672c28c4c6d4a6dfa5	no
EMAPKA_0.3.7_x64-setup.exe	4,481,447	a925b54859a284ad3b1700569413936b3ffc397429aa5ec3d8032dfffe6c9127	no

2026-09-12 · Windows, Linux

Changed

• Mark each digit of the start-up lock screen with a light circle; only that circle enters the digit.

Fixed

• Keep a click right after scrolling on the start-up lock screen.
• Hide the scroll bar on the start-up lock screen on Linux and Windows.

For administrators

Files

File	Bytes	SHA-256	Update signature
EMAPKA_0.3.6_amd64.deb	6,950,944	afa4501ce0cd0cf78834f8b0e5ac7961c717cf180d8dc51342478d5e6e40984a	no
EMAPKA_0.3.6_x64-setup.exe	4,508,502	54a21dd7a487d8de67ae2e40d93fd5a0526b6d3f1f98a7360f2cc9fffd418346	no

2026-09-11 · Windows, Linux

Fixed

• Protect priority messages from being selected or deleted by hand; a tap only marks an unread priority message as read.

For administrators

Files

File	Bytes	SHA-256	Update signature
EMAPKA_0.3.5_amd64.deb	6,947,748	ea81558530d8d31ac76231f89a0d778bf54b349bc60888bfadd36ce9c808f954	no
EMAPKA_0.3.5_x64-setup.exe	4,510,517	5516c7e9d8e19758a4af5920a4b0afd445543967ca02257c44b657d0c1c47fa4	no

2026-09-11 · Windows, Linux

Changed

• Show newcomers the names of group members right away.
• Remove the whole chat with a participant who has left.

Fixed

• Pause background checks, not the person's taps, after the server refuses a pass.

For administrators

Files

File	Bytes	SHA-256	Update signature
EMAPKA_0.3.4_amd64.deb	6,951,848	aad5e77e4f6bb7b09732959e793144339b74a8c86373a016ab6a44f9c2007bdb	no
EMAPKA_0.3.4_x64-setup.exe	4,508,555	ce7ec35a540d90c4557f3014b8b2513d0aca546c1022c214ab0163842c6e8a3d	no

2026-09-10 · Windows, Linux

Changed

• Make the consent box a one-time choice: once ticked, it stays ticked.

For administrators

Files

File	Bytes	SHA-256	Update signature
EMAPKA_0.3.3_amd64.deb	6,944,754	36785e0c4b2754dcee58dd66c5db8233ff77997a3fd4cc44fa02d166880c38d5	no
EMAPKA_0.3.3_x64-setup.exe	4,508,788	9ff002915faf1917016e149f4d787471515d1cba6beff19018efdf88c5f2e802	no

2026-09-08 · Linux

Build for diagnostics; never announced as the latest version.

Added

• Add diagnostic markers that link the app's requests to the server's records (sent only with the user's consent).

For administrators

Files

File	Bytes	SHA-256	Update signature
EMAPKA_0.3.2_amd64.deb	6,948,016	3eb05320bed0413cd6fb933a1d1ac9dd891f811075c9b850af5c4cf003440324	no

2026-09-02 · Windows, Linux

Fixed

• Keep a received file that finished downloading when the app is closed and reopened during the download.
• Deliver a file sent while offline together with its description instead of as an empty message.

Security

• Require authorization on the server for all attachment storage routes.

For administrators

Files

File	Bytes	SHA-256	Update signature
EMAPKA_0.3.1_amd64.AppImage	89,807,352	981d50523e070e0a9425c60a825e99808bd8a04f638857413519e60f0ea3c124	no
EMAPKA_0.3.1_amd64.deb	7,074,576	9a570a448f9e12e9ab78aaac582b157248d96d3a95558640a362664525b44a4c	no
EMAPKA_0.3.1_x64-setup.exe	4,497,596	62ea6edd7882fb4bdc152f92a673813f4e104cb972e8b873fcda212ab8193681	no

2026-08-28 · Windows, Linux

First public beta.

Added

• Create end-to-end encrypted groups of 2 to 10 people and private two-person channels (Channel +1).
• Invite people with an eight-character code; messages, files and keys stay encrypted on the device.

For administrators

Files

File	Bytes	SHA-256	Update signature
EMAPKA_0.3.0_amd64.deb	7,052,428	415b084ab290c076522c0cceac01612afa2edcc9e94de7d6d60bc70bafe944f4	no
EMAPKA_0.3.0_x64-setup.exe	4,490,171	0a20a26582fb7c166f562e5e3a80ec05cc1c86f7fbbef59abcae175bd3ed3ede	no