mirror of
https://github.com/seemoo-lab/AirGuard.git
synced 2026-04-25 15:35:49 +03:00
[GH-ISSUE #79] Give further hints for potential reasons on false alarms regarding traveling #52
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/AirGuard#52
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @patrickhanft on GitHub (Jun 25, 2022).
Original GitHub issue: https://github.com/seemoo-lab/AirGuard/issues/79
Hi!
I recently got an AirTag warning on a 3 hour trip on a long distance train, I traveled almost 500km with.
For me that was great, as I had a real world example for the app working. Also, because I got no further warnings after the train ride, I am quite sure, that this was not a malicious tracking attack on me, but a fellow traveler sitting nearby probably had an active airtag for her or his own purposes.
As an alarm warning can be a little bit intimidating in the moment when I receive it, making the connection, that it was during a train journey together with strangers, took a few moments. Maybe a hint to this idea could be incorporated into the alarm message or the guidelines regarding "false alarms"?
Although we are after two years of pandemic only getting used to it, but I guess long distance travel on busses, trains and maybe planes would be a usual reason for triggering false alarms?
@Sn0wfreezeDev commented on GitHub (Jun 28, 2022):
Thanks Patrick for this contribution and your real-world example. I agree we could do a lot better in wording here. I'll add this to our feature log to improve in this area.