What changed
in every release.

1.8.06 — late and repeat alerts say what is happening, and descriptions say what is known

Release 1.8.06 · 3 November 2026 · Full release notes

• Repeat red alert: after you silence it, the alert returns only when things really get worse: a new object or one at least 10 km closer, within 30 km of the province (point position, high confidence, at least 2 reports), at most twice and at least 15 minutes after the previous one, or an Alert RCB of level 2 or 3. Running on the server since 2 November.
• A late alert on Android is no longer silent: it plays normally and says how late it is and what time the threat is from.
• Heading descriptions: a wave gives the number of objects and how many headings are known, presumed and unknown, instead of “heading at Poland”. A drone with a presumed heading is described by its distance from the Polish border. Scoring is unchanged.
• iPhone: “Silent” mutes yellow even with the app closed, and notifications arrive in the app's language. Red is not affected.
• GROTA: PSP list of 2 November, 88,138 points. If your saved shelter has changed, the app says so.

1.8.05 — a siren that an accident cannot silence, and an alert log

Release 1.8.05 · 1 November 2026 · Full release notes

• Siren: while the alert screen is open, other notifications, expanding the panel and the volume buttons do not interrupt it. On emulators each of these could previously silence it for good, depending on the Android version.
• Full screen: red now gets it after an earlier yellow too, and on Android 9 no longer ends up as just a banner.
• Alert log in Alerts and permissions: when an alert arrived, how long it took, the state of the phone and how the alert ended. The data stays on the phone.
• Drone with no heading: confirms red only with high confidence and at least 2 reports, or within 30 km of the border. The description no longer says “heading towards the border” when the heading is unknown. The server has worked this way since 1 November.
• The checklist card warns about battery optimisation on phones other than Google's.

1.8.04 — updates through Google Play and stronger app protection

Release 1.8.04 · 31 October 2026 · Full release notes

• Updates through Google Play: on a phone with the Google Play Store, the APK version offers Open Google Play once the new release is approved in the store. Both versions carry the same signature, so the store updates without uninstalling. Installing from a file remains as the second option; Play Protect could stop it with a red warning. Works from the next update after 1.8.04.
• Phone storage: before downloading an update the app checks free space and says how many megabytes to free up; the file no longer sits in the cache that Android clears.
• The update window no longer appears on top of the welcome screen and settings.
• In landscape content and dialogs no longer go under the camera cutout or the iPhone island.
• Content Security Policy (CSP) in the app: the app runs only its own scripts and does not execute code from text — just like the straznik.eu website.

1.8.03 — an honest description of drones reported “heading to…” and fewer false warnings

Release 1.8.03 · 28 October 2026 · Full release notes

• Drone “heading to…”: such a report gives only the target, and the angle on the map was computed by NEPTUN from a nominal point in front of the target. The icon no longer shows a direction, and the card says plainly what was reported, that the position is nominal and that the flight direction is unknown. In western Ukraine this angle pointed at Poland in 99% of cases and usually differed from the flight observed later by more than 90°.
• Points: such a drone counts only when it is closer than 150 km to the border. Over 30 days of data: 20 fewer yellow warnings without a later RCB alert; the lead over an RCB alert was lost once.
• Heading from movement: the jump from the nominal point to the town is no longer counted as the drone's movement.
• Aircraft: the sources window names the fallback source — FlyItalyADSB (CC BY-SA 4.0 licence).

1.8.02 — the correct date in the GROTA warning, aircraft within the adsb.lol limit

Release 1.8.02 · 26 October 2026 · Full release notes

• GROTA: in the warning about a changed shelter (places saved before 1.8.01) the “pointed to” sentence now gives the register in which the number still meant the old building — in 1.8.01 both dates were the same. The rest of the warning worked correctly.
• Aircraft: adsb.lol allows 500 requests a day per address. The server now asks evenly within that limit (every 173 s), so the aircraft layer and the ADS-B indicator in the sources work again; a phone in serverless mode stays within the limit too.

1.8.01 — GROTA with the 26 October PSP list and a warning about a changed shelter

Release 1.8.01 · 26 October 2026 · Full release notes

• PSP list of 26 October — 87,835 shelter points, built into the app.
• Warning about a saved shelter. In the 26 October list the same point number pointed to a different building in 25 cases, 2.9 to 23.3 km away. GROTA now says next to the place that the number now means a different building, that PSP corrected the position, or that the point is gone — and that choosing a new shelter is necessary. Nothing is deleted; “Leave it as it is” silences only that one change.
• GROTA search finds Gdańsk, Gdynia, Hel, Jastarnia and Puck, and shows the province for places with the same name (two Olsztyns).
• Offline map tells you when the server has a newer version and can be replaced.
• Serverless mode understands the new RCB alert formats, full inflected place names and a small bonus for a drone heading towards a province.
• Fewer third-party services: no CARTO fallback map and no fallback ADS-B sources (adsb.fi, airplanes.live) — their terms do not allow this use. The privacy policy describes the fallback mode.

1.8.00 — a shorter alert screen with a 15-minute limit, alerts only for your provinces

Release 1.8.00 · 21 October 2026 · Full release notes

• Red alert screen. “ACKNOWLEDGE — silence alert”, and after it the choices (Where to shelter, Watch the map, I'm in a safe place), sit right below the score — no scrolling. At most 3 reasons; the panel shows the rest.
• 15-minute limit. The siren, vibration and flashing screen stop by themselves after 15 minutes — for the battery and to keep the phone from heating up. The alert stays: the province remains red, and the next alert sounds again.
• Shorter notifications: a headline, at most 3 reasons and one sentence on what to do.
• Alerts only for the provinces you watch (issue #15): a phone with a place in Masovian received alerts for Lublin because an old subscription stayed on Google's servers after the province was changed. The app now unsubscribes from every province outside your choice, and drops an alert for another province before anything rings.
• An RCB alert that expired without being cancelled stays in the panel for an hour as “expired at …” instead of vanishing.
• Media: an announcement of a meeting, lecture, workshop or webinar gives no points. Place names: “powiat opolski” is a county in Lublin province, not Opole province; Rawa Mazowiecka → Łódź; Chełmek → Lesser Poland; Janów and Międzyrzec Podlaski → Lublin.
• Small things: the province header no longer hides under the panel bar; a new privacy policy with the data controller and your GDPR rights.

1.7.99 — fairer scoring, confirmed and uncertain drones on the map, new PSP list

Release 1.7.99 · 19 October 2026 · Full release notes

• Drones are not passed to neighbours. Every drone has its own distance to every province, and spillover counted it a second time in the neighbour — on 19.10 Świętokrzyskie, with 1.1 points of its own, showed red (9.5 points). On the 11–19.10 history: red from neighbours only 1510 min → 0; no red alert disappears.
• An article about an RCB alert scores nothing extra (a reader's suggestion): a report that only repeats an RCB alert issued up to 4 hours earlier, and an article about the end of the threat — 0 points. Information beyond the alert (a drone over Poland, a violation, debris, sirens, a search) keeps its points.
• Drone descriptions in Polish: “wiarygodność: wysoka”, “180,9 km”, “3 potwierdzenia”; a drone added to a farther province — “X km from … province”, “⏱ to … province”.
• Confirmed and uncertain drones on the map. A drone whose position comes from a “heading towards …” report rather than a fix has a dimmed icon with a dashed outline — on 19.10 around Lviv 11 of 16 tracks were such reports. New legend entry.
• Points on the object card: a “confirmed / uncertain position” badge and “Points now” for each province, and when it adds nothing, the reason (NEPTUN limit full, or the same point counted from another report). Uncertainty circles by default only for the tapped drone and confirmed positions within 50 km of the border — they used to merge into a blot; turn all on in Settings → Map. Scoring unchanged.
• GROTA: the PSP register of 19 October — 87,316 points (604 more); 183 changed availability, most in Racibórz, Grudziądz and Mogilno. Check the place you saved.
• iPhone: “Alert volume” describes Critical Alerts instead of an empty expander.

1.7.98 — back buttons at the top of every window

Release 1.7.98 · 18 October 2026 · Full release notes

• “‹ Menu” at the top of every window opened from the Menu: Settings (the button used to sit below the list of sections), About, Foreign aircraft and Legend.
• “‹ Settings” at the top of the Settings sections and the My places window. After Notifications and My places you can go all the way back to the Menu.
• On a narrow screen in the web version the drone counter no longer covers the legend header.

1.7.97 — small-screen layout, map above the panel, drone near the border

Release 1.7.97 · 18 October 2026 · Full release notes

• Small screens and large text: the object card no longer runs off the screen and always has its cross; the chart header, history bar, permission windows and “About” fit at 320 dp width and up to 200% system font size. A permanent test now checks this.
• Map above the bottom panel: when you open Signals or the history, the map moves over the uncovered part of the screen and goes back when you close it. A reader's suggestion.
• History: province cards collapse on tap as in live view, the bar buttons have labels, the uncertainty circle grows with the age of the report.
• Settings opened from the Menu have a “‹ Menu” button. The object card says “heading to a target” when the heading was derived from a target given by the source.
• Scoring: a drone or Shahed within 30 km of a province (at least 2 reports, point position) gives it at least yellow; a report with a presumed heading does not open red; a late article about an alert already cancelled in RSO and faulty reports from Lithuania and Latvia give no points. Offline mode scores every province in range, like the server.

1.7.96 — Map section, source outage bar, “place of shelter” in alerts

Release 1.7.96 · 17 October 2026 · Full release notes

• Settings → Map: object tracks and flight direction have their own, fifth section (they were hidden under “Language, text and version”). On iPhone the sound row is called “Sound”, because quiet hours are Android-only.
• “NEPTUN not responding since…” bar above the map when the source has been silent for more than 2 minutes. Objects stay on the map, because an empty map during an outage would look like calm.
• “Go to a place of shelter” also in the notification and in Android's full-screen alert (the in-app alert screen has said so since 1.7.95).
• Smoother map with many objects. 12-hour chart: “most at once”, average over the last 30 minutes, round missile dots on wide screens.
• Offline mode scores alerts the same way as the server: no red from area-only reports, RCB alert level changes in place, correct alert issue time, Baltic drills and tests ignored, backup ADS-B for the Baltic states.

1.7.95 — new look, drone and missile counter, quiet hours

Release 1.7.95 · 15 October 2026 · Full release notes

• New look: a floating bottom bar with GROTA in the middle, Menu instead of “More” (settings, notifications, legend, 3D view and foreign aircraft moved there from the top bar), settings in four sections with an alert-readiness card, a dark object card, “About” as a sheet.
• Drone and missile counter in the top bar — exactly as many as there are icons on the map; tapping it explains what is counted and why the number jumps. In History it shows the moment on the slider.
• History: 12-hour chart — drones (30-minute average) and missile dots above the slider, collapsed by default.
• Quiet hours (Android): during chosen hours yellow is silent, red vibrates only or stays unchanged. They never make an alert louder.
• Phone language: until you pick one, the app speaks Polish, Ukrainian or English — like the phone and like GROTA. Alerts still arrive in Polish.
• GROTA: bottom tabs in landscape and on tablets, “Try again” instead of an endless “Loading points…”, questions in the panel instead of system dialogs that also blocked the alert screen, better screen-reader support. “Your data” and the privacy policy say plainly what leaves the phone with NOW and with the offline map.
• Touch targets of at least 44 px, larger fine print, named dialogs for screen readers, a layout that holds at 200% system font. During an alert open windows and the card close. iPhone: the “Sounds” note corrected after a measurement — the red critical alert sounds even with them off; blurred backgrounds also on iOS 16–17.

1.7.94 — new PSP shelter list, “Feel” like the real alert

Release 1.7.94 · 13 October 2026 · Full release notes

• Strażnik is on Google Play — the website and guide now link to the store; the APK file is still available. You can install the store version over the APK, and your settings stay.
• GROTA on the PSP list of 12 October (86,712 points; the app had the list of 28 September until now). 136 points changed availability, almost all from “24 hours” to “On request” — in Ustrzyki Dolne “24 hours” now has 9 instead of 52, in Leżajsk 2 instead of 33. Check your shelter.
• “Feel” vibrates like the real signal (Android): yellow like a notification, red like an alarm, silent mode included. When yellow cannot vibrate, the app says why; a note under the buttons says the patterns are not a choice.
• History matches the live map: the points of a drone that disappeared from the data fade after about 30 minutes (near the border — as before).
• Messages shown with settings open now appear above the window. iPhone: the red test goes out as a critical alert when permitted, and without the permission the app warns it will be silent; the test text is in the app language; a note says the yellow volume only affects the open app. Alerts arrive in Polish — the note at the test says so.

1.7.93 — alerts on your watch, Morse-code vibration, three red-alert modes

Release 1.7.93 · 11 October 2026 · Full release notes

• The red alert reaches Wear OS watches. It was marked as an ongoing notification, and Android does not forward those to a watch. Bands and watches with their own app show it if you allow Strażnik in them.
• Morse-code vibration: yellow is “U” (· · —), red is “A” (· —) — impossible to mistake for an ordinary text message. ⚙ → Sound has “Feel” buttons. Disabled channels and vibration settings carry over to the new channels.
• Three red-alert modes (Android): Siren, Vibration only or Regular notification — no full screen and no siren, with a warning that in Do Not Disturb it may not reach you.
• “Held until …”: when the score falls below the threshold, the card says how long the level stays, and history and the slider bar show the same as the live map.
• Settings show how long the last alert took and whether Google lowered its priority; with the app open a silent notification stays in the shade, so later alerts are not delayed.
• A one-sentence situation summary for screen readers, a circle of at least 40 km for objects positioned from their target, PAŻP zones in history, the legend ending above the province pill, and a fixed “−1 min” step in history.

1.7.92 — security fix

Release 1.7.92 · 10 October 2026 · Full release notes

• We recommend updating. The app engine (Capacitor) is raised to the version that fixes a publicly announced vulnerability. Our weekly dependency check caught it.
• Links from external sources — articles, signals and aircraft photos — can no longer lead into the app itself.
• Interface, scoring, alert thresholds and notification text are unchanged.

1.7.91 — Podkarpackie hears the drones, the phone warns about app sleep

Release 1.7.91 · 8 October 2026 · Full release notes

• An object now scores every province within range, weighted by the distance to that particular province. Until now only the province with the nearest stretch of border scored — regardless of where the object was heading. A drone over Lviv flying straight at Przemyśl therefore scored for Lubelskie, because the border bulges east near Hrebenne. Between 12 September and 8 October Lubelskie received 574 object signals and Podkarpackie 18. Reported by a user, Małgorzata Urbańska.
• Before the change we replayed two months of real data: Podkarpackie gains 17 → 27 yellow signals and 610 → 1030 minutes above the threshold, Lubelskie loses nothing, and not a single extra red alert appears.
• If your phone restricts Strażnik's battery, the app now warns you and takes you straight to the right setting. On Samsung, Xiaomi and similar skins, app sleep can stop notifications entirely even though every permission is granted. Reported from two Galaxy phones on the same day.
• ⚙ → Alerts now shows the time of the last signal received from the server. It tells “nothing arrived” apart from “it arrived, but I did not hear it”.
• PAŻP zones disappear in the history view. We do not store them in snapshots, so the slider was drawing today's zones over a past situation — and the ad-hoc zones opened during an incident were invisible anyway.
• The object card no longer claims we “assume the worse case”. A plain drone is counted as a Shahed (180 km/h), but a jet Shahed flies 300–600 km/h and is recognised only when the source marks it. The card now says so plainly. Raised by a user.
• Fixed: the website cache grew without limit, keeping one copy of every file from every release.
• Alert thresholds and notification wording are unchanged. A red alert still requires a key.

1.7.90 — text size, a fresh shelter register, one speed

Release 1.7.90 · 4 October 2026 · Full release notes

• You can enlarge the text across the whole app. ⚙ → App → “Text size”: Normal, Larger or Largest. It applies at once, with no saving and no restart. Every piece of text grows together — the panel, the cards, the legend, the alert screen and GROTA — while spacing and buttons keep their size so the layout holds. On Android it multiplies with the system font size, so with a large system font “Normal” is usually enough.
• GROTA carries the State Fire Service register of 28 September: 86,533 places instead of 86,388. For the first time no place dropped out of routing — eight came back. There are 82,000 fewer people living further than 5 km from the nearest place, and 205 municipalities without any place instead of 225.
• The Bartoszyce district lost 405 places (Bartoszyce 491 → 229, Górowo Iławeckie 105 → 28). We checked by coordinates: these are real removals by the Fire Service, not renumbering. The Service also corrected its own errors — a place on Łucka street in Warsaw had been sitting 144 km away, near Łódź.
• GROTA: a “List” button on the Map screen. The same places and filters as the map, but as a list you can walk with a keyboard and a screen reader — with the address, the distance, the walking time and how certain the position is. Keyboard focus is finally visible throughout the module.
• Arrival time now follows one rule on the server and in the app: the typical speed is a floor, and a speed derived from movement may only raise it, never lower it. The card now shows exactly the speed the alert is based on — for jet drones it used to show a longer time than the notification, promising more margin than we ourselves assumed.
• We say plainly what we do not know. In practice the source does not tell ordinary drones and Shaheds apart — they arrive together as “Drone / UAV”. The object card now says we assume the worse case, and the legend explains that splitting them into separate icons is ours, not the source's.
• Fixed: the expanded source bar slid under the title bar and its text showed between the icons for the first five seconds. The connection badge covered the start of the source list.
• Fixed: reconnaissance drones got no arrival time on the card and no allowance for the age of the report on the map. Scoring and alerts were correct for them — only what a person saw was wrong.
• Scoring, thresholds and alert wording unchanged.

1.7.89 — tidier windows: collapsible sections and one shape

Release 1.7.89 · 3 October 2026 · Full release notes

• Settings, the legend and the About window no longer dump everything at once. Explanations now sit behind named collapsible sections next to the option they describe, while switches and rows stay visible. The Alerts tab fits on one screen instead of three, and the About window on one instead of six.
• The legend finally has a close button. Until now it was closed by tapping the toolbar icon again or tapping the map, and nothing said so. Its six groups expand one at a time, so every group name is visible at once.
• The aircraft and helicopter in the legend are drawn with the same pixels as on the map. The plane used to be a small square and the helicopter an emoji — the legend showed something other than the map.
• The legend lists all nine countries we colour, not three. The scoring window finally describes the six shadow neighbours added in 1.7.88.
• One shape across the interface — a rounded square, no pill sides. Cancel and Save have a 44 px touch target. The cross at the top of a window is enough, so the duplicate bottom Close button is gone from five windows.
• Emoji on buttons gave way to icons drawn like the rest of the app.
• Translations fixed. The legend and part of the settings stayed in Polish in the English and Ukrainian versions — 49 strings in the legend alone. A missing dictionary entry produced no error, it just left the Polish text, so nobody reported it.
• GROTA: every item in the Prepare checklist now has its own icon, not just the basement list.
• Scoring, thresholds, alert wording and alert volume are unchanged.

1.7.88 — six new neighbours on the map, cameras without previews

Release 1.7.88 · 3 October 2026 · Full release notes

• Strażnik now also reads the media in Moldova, Romania, Slovakia, Czechia, Sweden and Hungary — two feeds per country. An airspace event highlights that country on the map, and tapping it opens a card with the report.
• These six countries add no points at all. They will not raise the level, will not trigger a notification and will not change the colour of your province. Czech and Slovak newsrooms write about other countries’ airspace more often than their own, so the filter is being checked for a few weeks first — to be sure it does not take an event in Denmark, or over Poland, for one of theirs. Lithuania, Latvia and Estonia score as before.
• The neighbouring-country card never opened at all — not since 22 September, the day it was added. Tapping a highlighted Lithuania did nothing, because the card's code stopped on an error. Fixed and verified during a live alert.
• Ukrainian raion alerts showed the raw source text in the Polish and English interface too (“Бахмутський район · Ракетна загроза”). It now reads “Bachmutskyj raion · missile threat”. A reason we do not recognise is left quoted rather than invented.
• Sweden has been added to the map; it had simply been missing.
• Cameras in the region: the window was empty, and that was a bug — the thumbnail address had 30 July hard-coded into it, every one returned 404, and a dead tile hid itself. It is now a list with links: the preview is not shown here, because the worldcam.pl terms do not allow it, and tapping a tile opens the camera at the source. The phone no longer connects to their server.

Scoring, thresholds and alert wording unchanged.

1.7.87 — the circle shows where the object may really be

Release 1.7.87 · 30 September 2026 · Full release notes

• The circle around an object grows with the age of the report. We draw the last known position, so the circle now also covers the distance the object could have flown. A reader asked about a drone 14 km inside Moldova: the circle was ±12 km and did not reach the border, even though the report was 4 minutes old and a drone at 180 km/h could have flown 12 km in that time. The map was promising certainty it did not have.
• The object card splits the number: where it may be: ±13 km (4 km report + 9 km flown since). Without the split, the total would look like an unstable figure from the source.
• The growth stops at 15 minutes, after which the card says: the area has stopped growing; the object may be further away. Missiles, glide bombs and ballistic objects keep a fixed area — the source gives them no heading.
• For a “heading towards X” report the card now says plainly that this is an area on the approach line, not a measured position. For that drone, the bearing from the reported point to the target was 315.9° against the 316° heading given by the source — the point was computed, not observed.
• The legend and the guide describe the circle as it actually behaves.

Scoring, thresholds and alert wording are unchanged. The rule from 1.7.83 still holds: we do not compute positions, the icon stays where the source reported it — only the uncertainty circle grows.

1.7.86 — A red alert can wake you with vibration alone

Release 1.7.86 · 29 September 2026 · Full release notes

• A new switch in ⚙ → Sound: “Red alert: vibration only, no siren” (Android). Only the sound goes away: the vibration, the full screen, the flashing and getting through Do Not Disturb all stay, because anything else would be switching the alert off rather than changing how it reaches you. A paired watch vibrates just the same. Turning it on asks for confirmation and says plainly what it costs you at night. A reader on Facebook asked for this.
• The sound settings stopped fighting each other. Test: siren now plays even while the silence is on, because it is a request to hear the sound, not an alert; Test: full alert respects the silence, because it shows what will really happen. The “always at full volume” option is inactive and dimmed while the silence is on — there is nothing to turn up — and your choice comes back when you switch the silence off.
• On iPhone there is now a button to grant the alert-despite-silence permission. Apple granted us the Critical Alerts entitlement on 28 September. The button added in 1.7.84 did not work: iOS reports “not supported” until the app asks at least once, and we hid the button in exactly that case — so nobody ever asked. In the App Store build the permission would have been unreachable for everyone.
• The Ukrainian version of the Sound tab: two paragraphs were still in English (one of them since 1.7.84). They are Ukrainian now.

Scoring, thresholds and alert wording are unchanged. Alert-despite-silence on iPhone will only work in a build that passes App Store review; that is submitted separately.

1.7.85 — GROTA’s Rules tab matches the fire service’s written answer

Release 1.7.85 · 29 September 2026 · Full release notes

• We withdrew the promise to add a verification date to each shelter point. The National Headquarters of the State Fire Service told us in writing that the register does not keep one and does not plan to publish one — the empty field will also disappear from their own app. The facility type is a different matter: it belongs to the register’s statutory scope and is merely absent from the published dataset, so that promise stands.
• It now says plainly what “Availability” means: a helper parameter from the survey stage that can change with how the building is used. And what the authority did not explain — who opens an “on request” point during an alert, and how.
• It now says that the register also covers buildings in proceedings to be recognised as protective structures, former protective structures and planned locations for makeshift shelter, and that the official app publishes them “without indicating the final category of the facility”. That used to be our inference; it is now a quotation.
• It now says that the dataset is updated once a week and that there is no API and no plan to provide one.

This release changes no behaviour — it changes three sentences that had stopped being true. Source: letter BKG-III.065.119.2026 of 25 September 2026 from the National Headquarters of the State Fire Service.

1.7.84 — You can see which side of the border an object is on

Release 1.7.84 · 28 September 2026 · Full release notes

• The position-uncertainty circle no longer shades the map — only a dashed outline remains. The shaded ±4 km patch used to cover towns on the Polish side of the border, making it look as if the threat was above them.
• An object closer than 10 km to the border now has the distance written under its icon, for example “0.2 km from the border”. The icon is about 30 pixels wide, which at a regional view means several kilometres of ground — the drawing alone cannot settle which side of the border an object is on, but a number can. The label appears from medium zoom upwards, because when zoomed far out the labels collided with each other.
• Distances use the decimal separator of the interface language.
• On iPhone there is a new button granting permission for alerts despite silent mode. Apple issued that entitlement on 28 September; the permission is optional, reversible and applies to red alerts only — the yellow attention signal stays quiet.

Scoring, thresholds, alert wording and notifications are unchanged. This release closes the 28 September case: 1.7.83 fixed the drawn position, this one fixes the drawing itself.

1.7.83 — The icon stands where the object was reported

Release 1.7.83 · 28 September 2026 · Full release notes

• An object's icon now stands exactly where it was reported. Until now the map moved it forward along its measured course between reports — by up to 18 km and for up to 7 minutes — so that it would not stand still. An object just beyond the border, flying along it, could therefore look as if it were already over Poland.
• The uncertainty circle and the trail moved with the icon, so the map and the object card finally show the same place.
• Smooth movement is unchanged: the marker still glides for 45 seconds between two consecutive reports, only never ahead of the latest one.

Scoring, thresholds, alert wording and notifications are completely unchanged — they have always used the reported position, not the drawing on the map.

1.7.82 — Less data: a lighter app and fewer downloads

Release 1.7.82 · 27 September 2026 · Full release notes

• The app is 12 MB smaller. Eight object-class illustrations moved from PNG to WebP — 91 KB in total instead of 12.4 MB, and they look the same.
• The map of Ukraine, almost half a megabyte, is downloaded only when there are alerts there. It used to load on every visit even though it usually showed nothing.
• The server now sends only the part of the state that changed. Civil aircraft positions and source health change less often than threat data and no longer come with every update.
• When the whole country is quiet, the phone asks the server every 15 seconds instead of every 5, which saves battery and data. Whenever any region is raised the pace stays as before, and during an alert it is faster.
• The aircraft photo in the collapsed card is bigger. It used to shrink to a stamp floating in an empty band.
• Map files now stay in the browser for a year instead of a day, so a returning visitor does not download them again.

This release adds nothing — it reduces data, memory and battery use. Scoring, thresholds and alerting are unchanged.

1.7.81 — The alarm can be read by a screen reader

Release 1.7.81 · 26 September 2026 · Full release notes

• A screen reader now reads the alarm screen as soon as it appears, instead of staying on the map underneath. Tab cycles through the alarm's buttons and does not fall through to what is covered.
• When the level rises to yellow, the screen reader says which province. Until now a blind user heard only a short chime, with no information about what had happened.
• A return to the normal level is spoken too — with the caveat that this is not an official all-clear, only our own signals expiring.
• The system “reduce motion” setting now stops every pulsing element, not one out of six. The threat level stays readable without movement.
• The app can be operated with a keyboard or a switch: province cards expand with Enter and you can see where the cursor is. Touch works exactly as before.
• The update window no longer slides under the top bar — on narrow phones the bar hid the window title — and a longer list of changes scrolls inside the window.
• The row with data sources at the bottom of the map scrolls sideways with a finger instead of being cut off with an ellipsis.

This is a first step towards accessibility, not a claim that the app is accessible. A one-sentence situation summary, distinct vibration patterns and in-app text sizing are still ahead.

1.7.80 — An RCB alert for several provinces no longer vanishes

Release 1.7.80 · 26 September 2026 · Full release notes

• An RCB alert sent to several provinces at once vanished without a trace and scored nothing for any of them. The recipient list was recognised by one word form, and RCB uses a different one when the alert goes to more than one province.
• When an RCB alert stands for hours without being cancelled, Strażnik says so plainly instead of showing a calm map. The entry scores nothing and disappears after twelve hours.
• A cancellation worded “no threat on the territory of Poland” clears the alert in every province, not only in the one RSO happened to name.
• A position computed by ground receivers (MLAT) is no longer presented as ADS-B, and the aircraft icon no longer jumps tens of kilometres and back.
• Shelter: the PSP register updated to its 21 September state — 86,388 places. The Rules tab now says how current the data is and that the register is not fetched in the background.
• Shelter: added the rules from the government's “Response instruction” and a list of what to check before hiding in a cellar or a garage.
• The language preview in settings finally covers the “Map: object trails” section.

1.7.79 — A cancelled alarm no longer scores like an alarm

Release 1.7.79 · 24 September 2026 · Full release notes

• An alarm cancelled by RCB is no longer counted as an alarm. It happened twice on 24 September.
• The colour of a province in history comes from the alert level, not from the points alone — red shows only where the alarm really was red.
• The “what changed” window shows the whole list instead of one truncated item.
• The description of aircraft data sources now says where they really come from.
• On iPhone the siren plays with the app open even when the ringer is silenced by the switch.

1.7.78 — A quieter yellow signal, and RCB alerts read from the message itself

Release 1.7.78 · 24 September 2026 · Full release notes

• The yellow attention signal was louder than the red alert siren — a measurement showed a 4 dB gap in yellow's favour. It now sits clearly below the siren. The red alert was not made quieter.
• New setting ⚙ → Sound → “Attention sound volume (yellow)”: Normal, Quieter (about ten times quieter) or No sound (the banner and the vibration remain). On Android it works with the screen off too; on iPhone only inside the open app, because the system picks the volume of a push notification.
• The guide now says what Do Not Disturb actually does — measured on a Pixel 7: ordinary Do Not Disturb silences yellow while red gets through. But “Total silence” also silences the red alert and the app cannot work around it. Leave the “Alarms” exception on as well.
• For people who turned that exception off there is an optional 🌙 “Alert despite Do Not Disturb” button: red then shows full screen, though without sound.
• RCB alerts are now also read from the message text on gov.pl, not only from RSO. RSO sometimes carries only part of the recipients — podkarpackie was lost on 17 and 24 September. Fallback mode does the same now.
• An alert notification now starts with the time it was SENT (“10:54 · …”); the same time appears in the notification's own clock and on the full-screen alert. With a delayed push that differs from the arrival time, and the first one is what matters. On iPhone the server adds the time.
• The history bar showed a red alert where the level had actually been yellow — it derived the level from the score alone, while since 1.7.74 red requires a key. It now takes the level from the same assessment that colours the map.
• Fixed: fallback mode did not signal the yellow level at all (the notification went to a channel deleted at startup). Aircraft cards show the speed in km/h and in knots. The object card buttons no longer drift while scrolling, and the panel close button matches the rest of the app.

1.7.76 — Strażnik speaks Ukrainian

Release 1.7.76 · 24 September 2026 · Full release notes

• The whole app speaks Ukrainian: ⚙ → App → Interface language → “Українська”. The translation covers screens, object cards, the signals panel, history, alerts, My places and the source descriptions — not just buttons.
• Ukrainian place and oblast names stay in the original, without transliteration, and map labels switch to Ukrainian. Numbers keep the comma, as in Polish.
• GROTA now follows Strażnik’s language for Ukrainian too; its own choice in the Rules tab still takes precedence.
• The user guide is available in Ukrainian as well, with a PL/EN/UA switch in the header.
• Along the way, gaps in the English version were fixed: the alert screen (“What to do…”, the three choice buttons), the camera window title and note, the “Push alerts” heading and the own-server description were showing in Polish.

1.7.74 — Red alert now needs a confirmation; RCB alerts scored by their wording

Release 1.7.74 · 23 September 2026 · Full release notes

• A red alert no longer follows from the score alone. Besides 4 points it needs a confirmation: an RCB alert saying “find a safe place”, or a real strike object heading at Poland — 15 minutes from the border or closer than 50 km. Reconnaissance drones and media reports alone do not open red. With 4 points and no confirmation the province stays yellow, and the app says so on the card.
• Since 17 September RCB distinguishes three kinds of message, and Strażnik scores them separately: “the situation is being monitored” 1.5 pts, “a massive attack is under way… react to alarm signals” 3 pts, “threat of an air attack, find a safe place” 4.5 pts. A later alert does not add to the earlier one: the current one counts, and the surplus of a stronger one fades within 10 minutes.
• An article repeating the wording of an RCB alert no longer adds a second score — previously a different inflection of one word was enough to treat it as independent confirmation.
• A report about an event over the Baltic no longer scores a province just because a local outlet wrote about it.
• Reconnaissance drones weigh 0.15 instead of 0.5 pts. In exchange, three different objects heading at Poland within 15 minutes (closer than 150 km) add 0.5 pts together — so yellow still fires before the RCB alert.
• Time to the border is now computed for area-only positions too, so the red-alert condition has something to stand on.

1.7.72 — GROTA in English and Ukrainian; the map outside a downloaded area fixed

Release 1.7.72 · 22 September 2026 · Full release notes

• GROTA speaks English and Ukrainian. Choose the language in Rules → “Język · Language · Мова”; by default GROTA follows Strażnik's language, and if none is set — the phone's. Quotes from the Safety Guide are our translation; addresses stay in Polish. The full GROTA guide is also in Ukrainian.
• After downloading an offline map of one province, GROTA's map lost streets and buildings outside it, even online. Not any more — the update is enough, no need to download the map again.
• Expanded sections in GROTA (e.g. “Why are some points misplaced?”) no longer collapse by themselves after a few seconds.
• The app can no longer be zoomed by accident with two fingers or a double tap. The map zooms as before, and Android's system magnification still works.
• In English the “More” menu had shifted labels (GROTA read “About and scoring”). Fixed.

1.7.70 — GROTA: the aerial photo works again, on older Androids too

Release 1.7.70 · 22 September 2026 · Full release notes

• The aerial photo on a shelter's card shows again. In 1.7.68 it did not appear for anyone, because GUGiK's orthophoto service changed how it works. GROTA now retries and, if needed, uses the service's backup version.
• On Android older than 14 the photo never loaded: the phone did not trust the Geoportal server's certificate. The app now knows that certificate — for that one server only.
• Messages about a missing location permission say where to turn it on in the phone (Apps → Strażnik → Permissions → Location) instead of pointing to browser settings.
• A new, full GROTA guide with screenshots of every feature — in Polish and English.

1.7.68 — GROTA — where to shelter; clickable alerts in Lithuania, Latvia and Estonia

Release 1.7.68 · 22 September 2026 · Full release notes

• After you acknowledge an alert, the screen shows three buttons: “Where to shelter”, “Watch the map” and “I am safe”. Strażnik never switches the screen on its own — you choose.
• “Where to shelter” opens the new GROTA module straight on the TERAZ (now) tab: the nearest shelter points from the Fire Service's public list, with distance and route. It starts loading in the background as soon as the alert appears, so it opens at once. Outside an alert: More → “Shelter — nearest”. The list works offline; for now it is in Polish only and on Android only.
• Lithuania, Latvia or Estonia highlighted on the map now open a card when tapped — like a Ukrainian oblast: the article headline with a link, the time and the points for each province.
• Articles about preparing for alerts and question headlines from Baltic media are no longer taken for an alert announcement. On 22 September a piece about school drills in Tartu lit Lithuania red.

1.7.67 — 2D/3D view remembered, and an explanation when the map does not load

Release 1.7.67 · 22 September 2026 · Full release notes

• The app remembers your map view — 2D or 3D. If you prefer the flat map, you no longer have to switch it on every launch.
• If the map does not load within 20 seconds, an explanation replaces the empty screen: alerts still work, and something on the phone or network is blocking the map server (ad blocker, DNS filter, VPN). It also shows a technical detail for a screenshot.

1.7.66 — Collapsible map buttons and RCB alert fixes

Release 1.7.66 · 21 September 2026 · Full release notes

• The “my region”, “zones” and “whole PL” buttons can be tucked away with the arrow above them — they slide past the right edge, leaving a narrow strip. Tapping the strip or the arrow brings them back. The app remembers your choice.
• An active RCB alert is no longer taken for a cancellation. On 21 September the alert for Lublin province carried an RSO flag that Strażnik wrongly read as a cancellation, so it scored nothing. Cancellations are now recognised by the message text only.
• Articles that only repeat the RCB alert (“Polish aviation has started operations”, “the military scrambled aircraft”) no longer add a second score for the same information. An article reporting more — a drone over Poland, an airspace violation, a blast — still counts normally.

1.7.65 — Top bar clear of the clock; an explained empty map

Release 1.7.65 · 21 September 2026 · Full release notes

• On some new Android phones (e.g. POCO F9 Ultra) Strażnik's top bar sat under the clock and notification icons. The app now reads the system bar height from two sources and uses the larger one — on phones where everything was fine, nothing changes.
• If the phone does not allow map drawing (WebGL off), an explanation replaces the empty navy screen: alerts, signals and history keep working, and it says what to do to get the map back.
• The About text now mentions the Android and iPhone apps — Strażnik is also on the App Store.

1.7.64 — Updates work on Android 9 and 10

Release 1.7.64 · 21 September 2026 · Full release notes

• On phones with Android 9 and 10, updating from inside the app ended with the error “The update signature does not match the installed app”. The signature was fine — every release is signed with the same key. The app was reading it wrongly: Android 9 and 10 only report the certificate of a downloaded file when asked the older way. Fixed.
• If you have Android 9 or 10 and a version from 1.7.54 to 1.7.63, install this one update by hand: download Straznik.apk in your browser from the GitHub releases page and open the file. It installs over the old version and your settings and places stay. Later updates will work from inside the app again.
• Security is unchanged: the app still checks the checksum and the certificate of every update before installing it.

1.7.63 — Less work for the server, the same map

Release 1.7.63 · 20 September 2026 · Full release notes

• The app no longer keeps a permanent connection to the server. It asks for the state instead and gets a short “nothing new” when nothing has changed — that answer comes from the Cloudflare network, and our server never even learns about the question.
• Why: with permanent connections every phone occupied its own socket on the server and the load grew with the number of people. The server now serves one state every few seconds whether five hundred people are watching or fifty thousand — and during sirens everyone watches at once.
• For you the only change is that the map refreshes every two seconds during an alert and every five when things are calm. An alert reaching a closed app still arrives as a notification.

1.7.62 — History no longer loses the hours spent in the background

Release 1.7.62 · 19 September 2026 · Full release notes

• When the app was minimised, history left an empty hole: the slider jumped across the whole time the phone was not showing it. The app now notices the interruption and pulls the missing period from the server when you open history; if you return while the history bar is open, the timeline fills in on the spot.
• The data on the server was complete the whole time — it was only missing from the app's own memory.
• A neighbouring country no longer lights up on the map when its media report an air alert somewhere else in the world. On 19 September Lithuania turned red because of a story about an alert in the capital of Saudi Arabia.

1.7.61 — Three fixes reported from phones

Release 1.7.61 · 18 September 2026 · Full release notes

• History shows objects the way the live map does again. Since the previous release a drone icon could turn into a solid yellow disc: the report age that fades an icon never reached the stored snapshots, and without it the drawing fell back to its defaults.
• The My places window shows every saved place at once. With four or more the tab row scrolled sideways and, on a narrow screen, places simply vanished past the edge; they now wrap onto further lines and long names end in an ellipsis.
• On iPhone, touching a form field no longer magnifies the whole screen — fields now use the required 16 points. On Android nothing changes.

1.7.60 — You can see how old each report is

Release 1.7.60 · 17 September 2026 · Full release notes

• Under a drone or missile icon there is now the age of the last report, for example “7 min”, and the icon fades gradually between ten minutes and an hour. The object card has a “last report” line and, past a quarter of an hour, adds that the object may have moved on since.
• Why: NEPTUN collects human reports, not radar returns. An object stays where it was until someone reports it again, and sometimes no further report arrives. Measured on 17 September: one object out of fourteen changed position within ten minutes. A motionless icon means no new reports, not a frozen map.
• The “server connection lost” notice now waits six seconds. Before, it also flashed when the phone came back from the background and the connection returned within a second.

1.7.59 — A lighter live connection

Release 1.7.59 · 17 September 2026 · Full release notes

• Until now the server sent every phone the whole map state (about 55 KB) on each change and compressed it separately for each connection. Measured on 17 September: a fan-out to 1281 phones took almost a second and blocked the server meanwhile — this is what caused the stalls and the heavy-traffic notice during the sirens.
• Now the live connection carries a short “changed” signal (about 50 bytes) and the app fetches the map state from Cloudflare's edge cache. Sending that signal to a thousand phones takes 5 milliseconds instead of a second, and fetching the state mostly no longer touches the server.
• Nothing changes for you: the map refreshes as before, the first state arrives immediately after connecting, and alerts and notifications travel a separate path and work unchanged. The live-connection limit is now 15,000.

1.7.58 — A new server from Mikrus

Release 1.7.58 · 17 September 2026 · Full release notes

• Since 17 September Strażnik runs on its own server, provided to the project by Mikrus. Before, it shared two CPU cores with other projects; the move took under a minute and changed neither the website address nor how notifications work.
• Under the STRAŻNIK name there is now the Mikrus logo and a “hosted on Mikrus” link, and the popover shown after tapping the app name has a short thank-you with a link to the Mikrus website. The same note is in the About window, the user guide footer and the README.
• In English, the popover shown after tapping the app name has its GitHub source code link back.

1.7.57 — History scroll buttons and a working back button

Release 1.7.57 · 17 September 2026 · Full release notes

• The history slider now has a row of nine buttons below it: start (−12 h), previous alert, −10 and −1 minutes, play and pause, +1 and +10 minutes, next alert and end. Holding ±1 and ±10 keeps scrolling, and the ×1 button in the header switches playback speed to ×2 and ×4. Before, about 720 snapshots sat on a few centimetres of slider and a specific minute was hard to hit.
• Alert jumps go to the start of the previous or next period with an elevated or high level. Steps follow snapshot times, so after a gap when the app was closed a button jumps across the gap instead of standing still.
• The full-width “Back to live view” button has been replaced by a small “SWITCH TO LIVE” frame next to “HISTORY VIEW”. The bar covers less of the map.
• The Android system back button first closes whatever is open: the settings window, an object card, the legend, history view or the signals panel. Only on the plain map does it send the app to the background. Before, it minimised the app straight away. During a red alert back closes nothing, so an accidental tap cannot silence it.

1.7.56 — “Heavy traffic” instead of “connection lost”

Release 1.7.56 · 17 September 2026 · Full release notes

• During the sirens in Lublin and Rzeszów on 17 September more people connected at once than the live-connection limit allowed. The server kept working and the map kept refreshing, but for about two hours the app showed “server connection lost” and retried every few seconds.
• Now, when the server is busy, the app shows “heavy traffic — map refreshes every few seconds”, fetches the map state every 5–8 seconds and retries the live connection every 1–2 minutes. “Connection lost” appears only when even the map state cannot be fetched.
• On the server the live-connection limit went up from 3000 to 10,000, and extra users get a clear “busy” signal instead of a refusal. These changes already work on the website. Notifications and alerts do not depend on the live connection — they arrive through Android’s notification service.

1.7.55 — Full-screen alert reminder and a steadier connection

Release 1.7.55 · 17 September 2026 · Full release notes

• After every update on Android 14 and later the app shows a one-time “Full-screen alert — check the permission after an update” dialog. Android may turn this permission off when an app from outside the Play Store is updated, and without it a red alert will not wake the locked screen. The “Check permission” button opens the right system toggle. The dialog appears on the next updates, from 1.7.55 onwards.
• Previously the app could miss this: Android can report the permission as granted when it is not, and the warning banner, once closed, never came back. After an update the banner shows again.
• When a network (e.g. a corporate one) drops the live connection right after it opens, the app and the website no longer reconnect every second. After three short connections they fetch the state every few seconds and retry the live connection about every 5 minutes. The map keeps refreshing and the server is not flooded.

1.7.54 — Safer updates and a new licence

Release 1.7.54 · 17 September 2026 · Full release notes

• In-app updates download the file only from Strażnik releases on GitHub and, before installing, check not only the checksum but also that the file is Strażnik signed with the same key as the version on your phone. A forged file is rejected before the Android installer opens.
• From this version the code is under an “all rights reserved” licence; versions up to 1.7.53 stay under MIT. You can still download and use the app for free. The About dialog links to the licence and to third-party licences (NOTICE).
• Alert notifications quote an article title only from known newsrooms and from feeds configured directly; other reports are shown as “Media report” and the full title is visible in the app. An outside site can no longer put its own text into an alert.
• Security fixes after an audit: content from external sources in the signals panel and aircraft card is escaped more strictly, and the server rejects oversized requests and floods of notification sign-ups.

1.7.53 — Drones move again, alert colours no longer flicker

Release 1.7.53 · 16 September 2026 · Full release notes

• Why icons stood still: up to 1.7.47 the app moved a drone ahead of its reports — at a speed typical for its kind and along a presumed heading when NEPTUN gave none. The 1.7.48 audit showed that the icon then flew to where no drone was, sometimes a dozen kilometres further or the wrong way, so we turned it off. Side effect: a drone without a measured speed stood still until the next report and then jumped.
• What now: after each new NEPTUN report the icon glides smoothly from the old position to the new one over 45 seconds, and the track line ends at the icon.
• How this differs from the old movement: the icon only travels along the segment between two real positions — it never gets ahead of the source and never guesses the further flight. While gliding it is up to 45 s behind the report, and afterwards it sits exactly at the reported position. Jumps over 80 km and reports received after returning to the app are shown at once. Objects with a measured speed and heading move as before (up to 18 km, up to 7 min). Points and alerts are still computed from reports, not from the icon position.
• A province colour (yellow, red) is held for 10 minutes after the score last reached its threshold. On 16.09 podkarpackie changed colour 7 times in half an hour — now it would be 2 changes. Raising the level is immediate, and an RCB alert cancellation drops it at once.
• History shows the time offset as “−5 h 57 min”, and on short screens the history panel has more room. Articles saying that aircraft have ended operations no longer add points.

1.7.52 — Neighbouring alerts on the map and stricter Baltic media

Release 1.7.52 · 15 September 2026 · Full release notes

• Ukrainian districts with an air-raid alert light up red or yellow, as in NEPTUN. It is a preview only and adds no points. Tap a district to see the level, start time and reason.
• Lithuania, Latvia and Estonia get a red tint when their media report a declared alert that has not yet been lifted.
• Baltic media weigh less: an incident is 0.5 pt instead of 1. Only a report from the last 30 minutes about something happening now counts — no commentary (“Minister: …”), no reports about yesterday and no articles whose event time is over an hour old.
• Morning recaps and opinion pieces after a night RCB alert (“Nocny alert RCB…”, “Alert RCB zamiast ostrzegać…”) no longer add points.
• The legend has a new section, “Alerts in neighbouring countries (no points)”.

1.7.51 — Older phones, large fonts and a MiG-31K notice matching NEPTUN

Release 1.7.51 · 15 September 2026 · Full release notes

• The MiG-31K take-off notice now matches NEPTUN: “monitoring, not an alert” when Ukraine has not declared a nationwide alert. Previously the app always said “alert across Ukraine”.
• On phones with an older browser engine (e.g. a Galaxy S10 without WebView updates) My places and other dialogs scroll again and show the Save and Cancel buttons.
• With a large system font and on small screens the settings tabs are no longer cut off, map buttons no longer overlap the top bar (icons only when needed), and the signals panel starts below the bar.
• Airspace zones and the foreign aircraft log also load on older Android versions. On a browser engine that is too old, a screen explains what to update instead of staying blank.
• In the browser, objects no longer jump between an old and the current position — the server state is no longer taken from the browser cache.
• Settings say plainly when no province has been chosen for alerts yet, instead of “Unsubscribing this phone from provinces…”. The map adapts when the screen size changes during start-up (tablets, split screen).

1.7.50 — “Alerts on this phone” switch with confirmation

Release 1.7.50 · 15 September 2026 · Full release notes

• Turning alerts off is no longer lost when Android closes the app — previously the phone re-subscribed to its province on the next start.
• The “I don't want alerts” box is now an “Alerts on this phone” switch, as in Android settings.
• When switched off, the phone unsubscribes from every province and the status shows how many it is subscribed to, confirmed by Firebase. Even an alert that arrives before the unsubscription is not shown.
• With alerts off, the sound and alert tests no longer pretend an alert would work; they say how to turn alerts on.

1.7.49 — Fewer false media signals

Release 1.7.49 · 14 September 2026 · Full release notes

• Links to other articles in RSS descriptions (“CZYTAJ: …”) are no longer read as the entry's content — a story about a fraudster no longer scores for a “drone attack” in a recommended headline.
• The month “września” (September) is no longer mistaken for the town of Września, so dates no longer assign articles to Greater Poland.

1.7.48 — More accurate border, honest arrival times and emergency mode

Release 1.7.48 · 14 September 2026 · Full release notes

• Object distance is measured to Poland's actual outline, including the coast: an object over Poland shows “over Poland”, and its heading is compared with the whole country, not the nearest border point.
• A presumed NEPTUN heading (“towards X”) no longer triggers the arrival-time alert until the object's movement confirms it; jet drones (Geran-3) are counted at 450 km/h or their measured speed.
• The card shows arrival time as a range that allows for position uncertainty and data age; in the signal list it ages with the signal.
• Markers no longer drift without measured movement, approximate positions get a wider circle, and an object's track no longer breaks when its ID changes.
• History includes transfers from neighbouring provinces, and emergency mode shows a permanent badge that alerts will not arrive while the app is closed without the server.
• About now lists what the system cannot see: ballistic missiles, the Belarusian direction, Kaliningrad and the Baltic.

1.7.47 — Clearer MiG-31K notice and a steady history bar

Release 1.7.47 · 14 September 2026 · Full release notes

• The MiG-31K take-off notice explains what it means: the aircraft carries Kinzhal missiles, so the take-off alone is an alert for all of Ukraine; no source gives its position, and for Poland it is information, not a threat.
• In history the notice is a small badge in the bar header (full text on tap), so the bar and map buttons no longer jump from under your finger while scrubbing.

1.7.46 — Smoother history and MiG-31K take-off as a notice

Release 1.7.46 · 14 September 2026 · Full release notes

• The map history has a snapshot every minute instead of every two, so scrubbing is smoother.
• A MiG-31K take-off announced by NEPTUN for all of Ukraine is a notice above the province bar, not an icon parked in central Ukraine. It is a nationwide alert without an aircraft position and adds no points; an aircraft reported at a specific place is still on the map.

1.7.45 — Clear national borders on the map

Release 1.7.45 · 14 September 2026 · Full release notes

• Neighbouring countries have clearly different colours, so borders show as a continuous colour edge — no gaps on a tilted or zoomed-out map.
• Crimea is shown within Ukraine, and neighbouring countries no longer overlap in strips (e.g. Lithuania and Latvia).

1.7.44 — Opting out of alerts, drone heading and Baltic media fixes

Release 1.7.44 · 14 September 2026 · Full release notes

• The permission warning on the map has a close button, and ⚙ → Alerts lets you turn alerts off on this phone and keep only the map view.
• The drone icon's nose shows the heading measured from movement — the same as the track and heading line; the card notes when NEPTUN reports a different heading.
• Lithuanian, Latvian and Estonian media: an article about alerts (an interview, questions) is no longer an alert, and a strike in Ukraine is no longer a Baltic incident.

1.7.43 — National borders back to their previous look

Release 1.7.43 · 13 September 2026 · Full release notes

• The more visible white national border outlines have been temporarily removed: parts of them disappeared on the tilted map. The map shows borders as the base map draws them, and refined outlines will return in the near future.
• Object and aircraft tracks from 1.7.42 stay unchanged.

1.7.42 — Continuous borders when zoomed out and visible object tracks

Release 1.7.42 · 13 September 2026 · Full release notes

• National borders no longer break up when the map is zoomed out — including between Belarus and Ukraine, around Crimea and along the front line.
• Object and aircraft tracks show right after opening the app: the server sends a short position history.
• The heading line also uses the track reported by NEPTUN; the track line is more visible.

1.7.41 — More reliable alerts, siren volume and object tracks

Release 1.7.41 · 13 September 2026 · Full release notes

• The open app alerts for every watched province, not only the first place; a push received while the app is open is no longer lost.
• The red siren loops until silenced (the button on the alert screen or “Wycisz alarm” in the notification) and raises the “Alarms” volume to at least half. A full-volume option — off by default, only when deliberately switched on.
• The yellow attention sound respects silent mode and Do Not Disturb. A notification delayed by more than 10 minutes arrives silently with a note.
• Alerts arrive after a phone restart before unlocking; province subscriptions are renewed and confirmed at every start.
• Object tracks on the map: separately for drones and missiles and for aircraft — off, flown track, or track and heading.
• Native red and yellow alert tests in settings, a clearer alert (“what to do”, nearest object), more visible national borders and an RCB/RSO indicator.

1.7.40 — End and duration of Ukrainian oblast alerts

Release 1.7.40 · 13 September 2026 · Full release notes

• The end of an alert in a Ukrainian oblast zeroes its points and switches off the oblast highlight at once. Previously a 10-minute alert kept counting for up to an hour.
• A long alert keeps counting: full weight for the first 30 minutes from its real start, then half while it lasts. Previously an alert lasting hours dropped out of the score after an hour.
• The panel shows when the alert ended or “in progress since …, half weight”, and the oblast card shows when the alert started.
• Lithuania, Latvia and Estonia: feeds and the last alert in the Sources window (on the website since 1.7.38, now in the app too).

1.7.39 — Resilience to traffic peaks

Release 1.7.39 · 13 September 2026 · Full release notes

• On 13 September at 04:54 the server was stopped for lack of memory during a traffic peak and came back after 5 seconds. State, history and zones are now prepared in advance and served through Cloudflare, and the server itself turns away excess website traffic before memory runs out.
• After losing the connection, the app reconnects after a random delay so thousands of phones do not return in the same second.
• When the server is overloaded, the app fetches the state every few seconds instead of keeping a live connection, and tries to return after 1–2 minutes.
• Notifications and data collection work independently of website traffic.

1.7.38 — Readable drone heading, pulsing counted objects, UA oblasts and the Baltics

Release 1.7.38 · 13 September 2026 · Full release notes

• The UAV icon has a red nose and a red arrowhead ahead of it. An object without a known heading is no longer turned nose-north — every type then gets a dashed ring and a question mark. Reconnaissance drones are white-grey.
• Objects that currently add points to a province pulse with a red ring.
• A Ukrainian oblast with an air-raid alert that adds points is gently highlighted in pink; a tap shows the points for each province.
• Lithuania, Latvia and Estonia: new feeds (LRT, 15min, LSM, ERR). An alert announced there is a trace in the panel worth 0.12–0.3; the Sources window shows feed status, the last alert and zones.
• The update window shows the full list of changes. The drone card shows the correct heading offset from the direction to the border.

1.7.37 — Media scored after reading the article, no alert margin, new guide

Release 1.7.37 · 13 September 2026 · Full release notes

• The server reads the whole article before awarding points. A report on an earlier event, or an article that cannot be read, stays in the panel with its link but scores 0. Media add 0.5 or 1 point, capped at 1.
• The notification level always matches the current points. Returning to the same level within 60 minutes does not ring unless a new Alert RCB arrives.
• Alerts in more distant Ukrainian oblasts weigh less — the weight falls smoothly with distance.
• Overlapping zones: a tap opens the smallest one and lists the others as buttons on the card. In history, signal times count from the chosen moment.
• Website: the Strażnik icon in the browser tab, and turning notifications off in settings with the path to the browser permission.
• Helicopters have their own map icon with a rotor disc instead of an aeroplane silhouette. In English, drone cards give place and oblast names in English.
• The user guide was rewritten for the current version, with new screenshots in Polish and English.

1.7.36 — Spillover without double counting, RCB cancellations

Release 1.7.36 · 13 September 2026 · Full release notes

• The same event (an article, a Ukrainian oblast alert) assigned to two neighbouring provinces no longer comes back to the neighbour as spillover. Lubelskie and podkarpackie were inflating each other this way.
• Spillover can only trigger a notification with at least 1 point of own signals, and by one step at most. Colour from spillover alone is dimmed on the map and the card gets a dashed border.
• The in-app sound follows the alert level, not the map colour — a province coloured by its neighbours no longer starts the siren.
• A level drops 0.5 points below its threshold, and returning to the same level within 30 minutes does not repeat the notification without a new RCB alert or NEPTUN object.
• An RCB cancellation in RSO (including an edit of the existing entry) clears the alert and the articles that describe it afterwards.

1.7.35 — Closing a zone card no longer closes the signal list

Release 1.7.35 · 12 September 2026 · Full release notes

• Tapping the close cross on a zone card was closing the signal list instead of the card — the card sits outside the panel, so it counted as a tap beside it.
• Collapsing the panel also moved the card out from under the finger, so the actual click missed the cross. Hence both symptoms at once.
• Scoring is unchanged.

1.7.34 — A veto no longer deletes a genuine report

Release 1.7.34 · 12 September 2026 · Full release notes

• The veto “dni po” was matching inside the Polish word for “eastern district” and deleting a genuine report of fighters being scrambled. Keywords must now start at a word boundary.
• Vetoes are split into hard and soft. “Exercise” or “anniversary” cancel everything, because during a siren test the sirens really do sound. “Will last” or “what we know” only downgrade an operational report from 1.5 to 1.0 points — the event is real, the article covers its effects.
• A soft veto only applies when a critical phrase is present; a plain explainer is rejected exactly as before.
• Thresholds and caps are unchanged — media alone still never raise an alert.

1.7.33 — The zone card is readable, and the grace period really works

Release 1.7.33 · 12 September 2026 · Full release notes

• The zone-disappearance grace period described in the 1.7.30 notes had never been implemented. Without it, this morning’s PAŻP daily-plan rollover would have reported thirty zones as fresh activations.
• The zone designator was hiding under the collapse and close buttons — it now wraps in full.
• The card heading gave a contrast of 1.83:1 on the white card, below any legibility threshold. It is now 5.7:1, using the same approach object cards have used for a long time.
• The guide shows the zone layer in screenshots from the app, in Polish and English.
• Scoring is unchanged.

1.7.32 — The update box speaks in full sentences, a zone promises no end

Release 1.7.32 · 12 September 2026 · Full release notes

• The update box was showing three fragments of a single sentence cut in half — release notes are wrapped, and every line counted as a separate bullet. Now it shows whole points, up to eight, and scrolls.
• A PAŻP zone card said “Planned end: 13.09” even for a zone declared until December. That was the end of the daily slot, not of the zone — the row now reads “Reserved until” and says PAŻP publishes its plan day by day.
• The guide now explains in a table which zones score (D, R, NPZ, ADHOC), which do not (TSA, TRA, ATZ, parachuting, gliding, drones) and where that decision came from — a four-day measurement with no points awarded.
• Scoring is unchanged.

1.7.31 — An article lands where the event happened

Release 1.7.31 · 12 September 2026 · Full release notes

• A nationwide military statement was landing in Greater Poland, because the Polish word for “reconnaissance” contains “poznan”. A place name must now start at a word boundary.
• An article saying the threat is over (“alert cancelled”, “air operations concluded”) scores nothing and fades earlier media reports in that province. It does not touch an official RCB alert.
• A newsroom’s name no longer decides the region — “Romania: a drone hit a block of flats” from Radio Szczecin was landing in West Pomerania.
• The place-name dictionary grew from about 200 to 565 entries, 23 to 49 per province: colloquial region names, larger towns, border crossings and airfields.
• On the same feeds: before the change 8 attributions came from the text and 31 from a guess; after it, 17 from the text and none from a guess.
• A bomb hoax at a school and sirens at commemorations no longer score.

1.7.30 — PAŻP zones are visible, and the north stops being blind

Release 1.7.30 · 12 September 2026 · Full release notes

• A new “zones” button on the map shows active airspace zones. Tapping a zone explains in plain language what it is, since when Strażnik has seen it active, when it is due to end and at what altitude.
• Zones add no points and raise no alert — closing airspace is a decision by the military, not an independent measurement of the threat. The card says so explicitly.
• A long-standing zone gets a quiet outline; only a zone switched on while we were watching gets a 3D block — otherwise 31 zones flooded the map and looked like a nationwide alert.
• The north (Pomeranian, West Pomeranian, Warmian-Masurian, Kuyavian-Pomeranian) is scored differently, because NEPTUN covers Ukraine and gives it zero. A PAŻP zone weighs 1 pt there instead of 0.5, and Baltic incidents and Lithuanian or Estonian airspace closures finally reach the coast.
• No single signal still raises the level on its own: zone 1 + ADS-B activity 1 = 2 pts, zone 1 + Baltic incident 1 = 2 pts. Zones repeating within 7 days are routine and score nothing.
• A province fully covered by a large zone can be tapped again; the zone card leads to the province, and the province card lists its zones.

1.7.29 — You can see what arrived and where the score comes from

Release 1.7.29 · 12 September 2026 · Full release notes

• An article naming several provinces now reaches each of them. An RCB alert “for the Lublin and Subcarpathian provinces” used to reach Subcarpathia only, because the matcher took a single, longest keyword.
• A signal from the last five minutes goes to the top of the list with a NEW badge — a new object worth 0.1 pts used to land below hour-old entries. It returns to its place by contribution afterwards.
• The province card spells the total out: “adds up to: 1.2 RCB + 1.0 UA ALERT + 0.9 MEDIA · 2 signals add nothing”.
• A signal whose object left the map says “no longer tracked” instead of quoting a distance from 40 minutes ago.
• Scoring is unchanged apart from attributing an article to the right provinces.

1.7.28 — The object card and the signals agree

Release 1.7.28 · 12 September 2026 · Full release notes

• The object card only gave the heading in degrees; it now carries the verdict — “0 pts — heading 71° away from the direction to Poland” or “heading towards Poland” — the same wording as the signal list.
• A signal froze the distance from the moment it was raised: the panel said “192.5 km” while the same drone sat 130 km from the border on the map. While the object is still tracked, the row now appends “now 130.0 km”.
• Scoring is unchanged. The rule, for the record: full weight up to ±50° off the direction to the border, a linear fall to zero at ±70°, unknown heading ×0.5 and only within 150 km.

1.7.27 — An object on the map has to appear in the list

Release 1.7.27 · 12 September 2026 · Full release notes

• A drone near the border was visible on the map but missing from “Signals” entirely — because it was flying sideways and scored nothing. The zero was correct, but it looked like the app had missed it.
• The “Signals” section now ends with an “On the map, but scoring 0 pts” list that states the reason — e.g. “heading 86° away from the direction to Poland” or “heading unknown”.
• Scoring is unchanged: an object flying sideways 150 km from the border still contributes zero. What changed is that you can see the app noticed it.
• The “Data sources” dialog now has an English version — it was the last screen whose content stayed in Polish.

1.7.26 — Ukrainian alerts scored by distance

Release 1.7.26 · 12 September 2026 · Full release notes

• Rivne and Zhytomyr oblasts announced themselves as “borders Lublin province” and scored the same as Volyn — while lying 70 and 220 km from the border.
• Points now fall with distance: a shared border ×1.0, up to 120 km ×0.6, up to 220 km ×0.35, up to 320 km ×0.2. Beyond that, nothing.
• Ternopil, Ivano-Frankivsk, Khmelnytskyi, Chernivtsi and Vinnytsia oblasts were added. The same oblast can weigh differently for Lublin and Subcarpathia.
• The title gives the distance instead of an untrue “borders”. The 1.0-point class cap is unchanged — alerts still cannot replace an object on the map.
• Dialogs open from the top and clear the status bar; the legend has bottom padding and a “more below” shadow.

1.7.25 — The update dialog speaks English

Release 1.7.25 · 12 September 2026 · Full release notes

• The whole update path — messages, the “What changes” list, the buttons and the download progress — was hard-coded in Polish and stayed that way in the English interface. It now follows the interface language.

1.7.24 — Fixes after a day on a real device

Release 1.7.24 · 12 September 2026 · Full release notes

• “Check for updates” answers again. GitHub was rejecting the server’s requests with its 60/h per-IP limit; the server now keeps the last known release and serves it instead of an error.
• “Save on device” with an empty name is no longer a dead button — the message scrolls into view and the cursor lands in the missing field. A successful save closes the dialog and returns to Settings.
• The map always opens on the same frame: Poland and the whole of Ukraine. The “my region” button also shows the province in context rather than just its outline.
• The history bar stays put — it used to jump upwards from under your thumb when a signal appeared in the window.
• A new changelog page, reachable from the app: Settings → App → “Changelog ↗”.

1.7.23 — Navigation that stops covering the map

Release 1.7.23 · 12 September 2026 · Full release notes

• Bottom tabs Map · Signals · History · More — labelled and within thumb reach. The top bar now holds only the legend, 2D/3D, foreign aviation, notifications and settings.
• The object card opens as a thumbnail in the corner instead of covering the map; a chevron expands it to the full card. The selected object gets a white ring on the map.
• Dialogs (“About”, settings, “My places”) end above the tab bar and never reach the Android buttons.
• History mode names itself outright and the slider is considerably larger. Settings split into four tabs.
• Updates are checked at every launch instead of once a day.

1.7.22 — The alert has to be raised — and arrive

Release 1.7.22 · 12 September 2026 · Full release notes

• The source-class cap is assigned after age decay: during a longer attack a fresh object near the border no longer contributes zero.
• The threat level is recomputed every 45 seconds even without a new signal, and survives a server restart.
• Push messages carry a 15-minute expiry and three delivery attempts — a phone coming back online will not get a siren about an event from hours ago.
• Air alerts from western Ukrainian oblasts are finally read (they arrive as raions).
• Points spilled over from a neighbour no longer wake the phone — a notification needs the province’s own signal.

1.7.21 — More careful sources

Release 1.7.21 · 11 September 2026 · Full release notes

• A routine RSS article contributes 1 point, an unambiguous operational response 1.5, and the whole RSS class is capped at 1.5 — media alone can no longer raise the yellow level.
• Historical, anniversary, explainer and legal material stays visible but does not raise the threat level.
• The Lutsk centre point used in NEPTUN reports is recognised as an area position despite the source saying confirmed.

1.7.20 — Honest approximate positions

Release 1.7.20 · 10 September 2026 · Full release notes

• A point flagged approximate by NEPTUN is described as a report area, not a confirmed object position.
• For such a point the app does not move the marker artificially, does not draw an apparent route and gives no arrival time.
• An approximate position cannot trigger a threshold ETA alert.

1.7.19 — My places

Release 1.7.19 · 9 September 2026 · Full release notes

• Up to 8 place profiles stored locally; the old single-province setting is migrated into a “Home” profile.
• Each place can watch its province’s alerts; repeated provinces create a single subscription.
• Optional GPS is read only on request. Place names and coordinates never reach the server or notifications.

1.7.18 — Verified model photographs

Release 1.7.18 · 8 September 2026 · Full release notes

• A local library of 60 verified aircraft and helicopter photographs instead of a random picture from the web.
• Every photograph carries its author, source and licence; none depicts the specific tracked airframe.
• For an unknown or contradictory variant the card says outright that no verified photo is available.

1.7.17 — Consistent time in history

Release 1.7.17 · 7 September 2026 · Full release notes

• The map, aircraft list and aircraft details all show the same selected moment — an entry from the future cannot appear in an earlier snapshot.
• Dimmed last positions carry a timestamp and their own counter; they do not mean a landing or a shoot-down.
• The server journal also covers the time while the app was closed.

1.7.16 — English finished off

Release 1.7.16 · 6 September 2026 · Full release notes

• English descriptions for military aircraft: role, country of registration, telemetry and route following.
• The foreign-aircraft view and the missing legend explanations are translated.
• Country, city and region names on the map appear in English; missing names keep the safe source name.

1.7.15 — English interface

Release 1.7.15 · 5 September 2026 · Full release notes

• An English interface for the site and the app, with no change to sources, scoring or technical names.
• Picking a language previews the translated settings immediately; only “Save” makes it permanent.
• The red siren is louder so it is not quieter than the yellow attention signal.

1.7.14 — The update prompt says what it is about

Release 1.7.14 · 4 September 2026 · Full release notes

• The update prompt shows a “What changes” list — up to three key points.
• A non-critical update can still be postponed to the next session.

1.7.13 — Fuller history of foreign aircraft

Release 1.7.13 · 3 September 2026 · Full release notes

• History records entries and exits of Russian and Belarusian ADS-B aircraft together with their last position.
• A short-lived aircraft caught between snapshots no longer disappears from the historical map.
• A position reconstructed from an event is semi-transparent so it does not pose as a regular snapshot.

1.7.12 — Safer connections

Release 1.7.12 · 2 September 2026 · Full release notes

• External servers must use HTTPS; the app trusts only system certificate authorities.
• A custom HTTP address is not saved — an incorrect address stored earlier has to be corrected in settings.
• User settings are preserved across updates.