NAPTIFY

Release notes

What changed in each version of naptify-server.

naptify-server 1.1.6

2026-10-17

  • Multi-login: notices from the server now go to every device, not just one. This covers muzzle, cloak, level changes, channel invitations, operator and voice, server redirect instructions, ping, data port notices, direct browse and more. Nothing changes with a single device.
  • Multi-login: replies to a transfer request now go back to the device that asked. If that device has disconnected, they go to every device.
  • Multi-login: when you toggle your own cloak, your other devices are told too. A change of line speed is now applied to every device.
  • Fixed: data port notices (626) could show garbled names when the sender and the receiver used different character encodings.
  • Added a “Main features” section to the README included in the download.

naptify-server 1.1.5

2026-10-17

  • Fixed: with local2global, direct browse and transfers through linked servers or guilds received a LAN IP address and could not connect. The IP address of a user who connects from the server’s LAN is now replaced with the external IP address at sign-in (the same as SlavaNap and FaceNap), and that address is used everywhere: the user list, whois, transfers, direct browse, search results, links, guilds and ban checks.
  • Admin page, “Host name settings”: the check result is now shown as a list of items and values (the verdict, plus the likely cause and effect when they do not match). The externally visible IP address is now shown here instead of on the local2global card.
  • Extensions for naptify-client: connection compression, a notice when a bulk share registration finishes, and private message syncing for multi-login. Nothing changes for existing clients such as Utatane.

naptify-server 1.1.4

2026-10-16

  • MOTD is back. Write it over several lines under “MOTD” in the “Messages” settings, and it is sent line by line right after the version and host name lines at sign-in. Variables such as $user$ and $users$ are replaced with each user’s values (the settings page lists them). Lines starting with “;” are not sent, and users with the -MOTD user mode do not receive it.
  • The server also answers MOTD requests from clients with the same content.
  • Importing from FaceNap now brings over the MOTD together with the settings.
  • Removed the trailing “(-)” from the points shown in whois (it now reads “User Point: balance”). With points turned off, only the level name is shown.
  • local2global: removed “.pas” from the sign-in notice. In the admin page’s operation log, local2global lines are shown in orange and no longer include the sign-in notice status.

naptify-server 1.1.3

2026-10-16

  • local2global: each conversion of a local IP address is recorded in the admin page’s operation log (category local2global) and in logs/operations.jsonl.
  • local2global: a user who signs in from a local IP address is told about the conversion in the same format as FaceNap. IPv6 local addresses (::1, fc00::/7, fe80::/10 and IPv4-mapped addresses) are supported too. Settings take effect as soon as they are saved (no restart).
  • If the external IP address cannot be obtained from D-DNS.JP, the external address reported by the UPnP router is used.
  • Added an “Online rate” column to the registered users list in the admin page (the share of time online, averaged over 7 days). On first start, one table is added to the database (existing data is not changed).
  • Guild connections, refusals, disconnections and failures are recorded in the operation log (category guild).
  • Link: disconnections on the side that disabled the link, refused incoming links and links that never answered the login are now recorded in the operation log. When both sides connect at the same time, the link now comes up without waiting for the next retry.
  • Extensions for naptify-client: notice of the other side’s supported features, exchange of certificate fingerprints for encrypted file transfers, and registering, searching and checking file hashes. Nothing changes for existing clients such as Utatane.
  • Fixed: right after signing in with naptify-client, the server could stop responding for about 20 seconds.

naptify-server 1.1.2

2026-10-15

  • Extensions for naptify-client: supported features are checked at the start of the connection, and the connection can be encrypted with TLS. Nothing changes for existing clients such as Utatane.
  • TLS uses the D-DNS.JP SSL certificate (the same one as the admin page’s HTTPS); without one, the server creates a self-signed certificate. Turn it on or off under “TLS (for naptify-client)” in the connection settings (on by default).
  • The admin page shows which certificate TLS is using and its SHA-256 fingerprint.
  • Connection checks now use the standard OpenNap ping (751) for every client. When the same name signs in again, or a second device signs in with multi-login, only connections that answered a ping before and now stay silent are disconnected as ghosts. Connections that never answered (such as Utatane) are not disconnected.
  • Fixed: when the same name signed in again, or a second device signed in with multi-login, the server sent an unneeded direct browse request (640) to Utatane, which reacted on screen.

naptify-server 1.1.1

2026-10-13

  • Fixed: the server version shown to clients. 1.1.0 appeared as “NAPTIFY-SERVER 1.10”; it now appears as “NAPTIFY-SERVER 1.1.0”.
  • Fixed: clicking a member in the member list on the chat page did not select the row.

naptify-server 1.1.0

2026-10-13

  • Multi-login: one registered name can now sign in from several devices at the same time. Turn it on with “Multi-login” under “Login restrictions” in the settings (off by default; when off, nothing changes).
  • Other users, linked servers and guilds see one user. Sign-in and sign-out are announced only for the first and the last device.
  • Incoming private messages appear on every device. A message you send appears on your other devices as a message from the other person (a device with an auto-reply set will also auto-reply to it).
  • Shared files from all devices are listed together; the same folder and file name appear once. Download requests go to a device that has the file, preferring devices with an open port.
  • whois lists the IP addresses and ports of every device, separated by commas. The online list and user information in the admin page show each device.
  • The reason is now optional when adjusting points in the admin page.

naptify-server 1.0.54

2026-10-12

  • Settings page layout fixes: shortened long labels in English, German, Spanish, French, Portuguese and Ukrainian to fix broken columns and line wrapping. “Flood protection” is now “Flood Block”.
  • The outline that appeared around the heading when opening the settings is no longer shown. The outline for keyboard navigation is unchanged.
  • The chat page now writes a diagnostic log entry when a server reply could not be delivered to the screen.

naptify-server 1.0.53

2026-10-11

  • Fixed: private messages sent from the chat page to services such as MsgServ were shown as failed, and their replies did not appear.
  • The Linux version now shows the server’s IPv6 address and can register it (AAAA) for the host name.
  • Admin page layout improvements: fixed cut-off text and extra line wrapping in the settings for some languages. Channel settings now use three columns on wide screens.

naptify-server 1.0.52

2026-10-11

  • Fixed: on Windows, writing changes back to the database could stop partway while the server was running, so main.sqlite-wal kept growing. We recommend updating soon.

naptify-server 1.0.51

2026-10-10

  • Linux builds are now available (x86_64 and ARM64, glibc 2.17 or later), with a systemd unit file included. See the included README.txt for setup.
  • Removed the explanatory text from the “Update check” settings.

naptify-server 1.0.50

2026-10-10

  • Added a right-click menu to the member list on the chat page: private message, user information, shared files, granting and removing operator and voice, muzzle, kick, ban, changing the level, and copying the name. From the keyboard, press Shift+F10.
  • The chat page now shows the result of commands sent from the message box, and the reason when a message could not be sent.

naptify-server 1.0.49

2026-10-10

  • Before each hourly backup, the server now finishes writing to the database and empties the file that holds unfinished writes (main.sqlite-wal). In 1.0.48, on busy servers the write could stall and this file could keep growing.
  • If the write could not be completed, a warning now appears in the operation log on the admin page.

naptify-server 1.0.48

2026-10-09

  • Safer data handling: the server first writes changes to a separate file (main.sqlite-wal) and later merges them into the database itself (main.sqlite). Until now, if that merge failed, nothing was shown anywhere. From 1.0.48, a failure appears as an error in the operation log on the admin page.
  • When the server is stopped or restarted, it now always finishes that merge before exiting. This also applies to restarts from the admin page and to OS restarts.
  • Fixed an error shown when opening the admin address with /admin/ at the end (the operation log screen now opens).
  • Shortened the channel setting “Private (hide from the list)” to “Private” (in all 9 languages).

naptify-server 1.0.47

2026-10-09

  • The totals in the bottom bar of the admin page (logins, transfers and so on) now use a short notation for each language and fit on one line.
  • On a phone-width admin page, the values in the network cards now wrap instead of being cut off.

Before you update

  • Updating works as before: stop the server, replace the executable and start it again. No data migration or settings change is needed.
  • When you move the data folder to another PC, or copy it as a backup, always stop the server first. While it is running, recent changes may still be in main.sqlite-wal, so copying only main.sqlite would miss them.

Downloads are on the Download page.