Yesterday, the #Russians activated Electronic Warfare (#EW) systems in #Kaliningrad, resulting in almost half of #Poland and the #Suwalki Corridor losing #GPS#Polish media.
Did you know that the context menu for the #Map in #NeoFinder can move the #GPS#GeoTags of multiple selected photos or videos to the clicked location on the Map?
That is a great way to adjust the often slightly off location images taken by an iPhone.
The #GPS View Direction editor in #NeoFinder 8.5 now shows a real map of the #GeoTag location, to make it easier for you to set up the correct view direction of the camera when the photo was taken.
The #GPS View Direction editor in #NeoFinder 8.5 now shows a real map of the #GeoTag location, to make it easier for you to set up the correct view direction of the camera when the photo was taken.
Currently de-googling my old Samsung J6 (as well as any other crap that it no longer needs) -
A week of good testing, and it works very successfully as my GPS timer/tracker
No SIM card
Fitotrack (installed from FDroid)
GPS only
and
The latest Open Street Maps (12/2023)
Alors, suite de mes tests de #GrapheneOS avec le #GPS, car j'ai persisté malgré mes premières constatations de mauvais fonctionnement : surprise ! Pour je ne sais quelle raison, ça fonctionne parfaitement bien. Pourquoi, je ne sais pas car je ne sais pas ce que j'ai pu changer dans la configuration, mais en tout cas, ça marche bien. Je suis en train de comparer avec mon autre téléphone la précision des traces, mais pour l'instant, je n'ai rien à dire. Bonne nouvelle donc.
An OSINT researcher on the Twit-site as discovered the rough location of a GPS jammer near the Baltic. The centre of the area is (not surprisingly) Kaliningrad.
"@auonsson: I think I found the location of the Baltic Jammer. In Kaliningrad, Russia.
"Since Dec 15 aircrafts have suffered from navigation errors over south Baltic Sea, on and off.
"By plotting an assumed max jamming-range for each bad position there is one area standing out: Kaliningrad."
#Cars#Surveillance#Privacy#GPS: "A car, to its driver, can feel like a sanctuary. A place to sing favorite songs off key, to cry, to vent or to drive somewhere no one knows you’re going.
But in truth, there are few places in our lives less private.
Modern cars have been called “smartphones with wheels” because they are internet-connected and have myriad methods of data collection, from cameras and seat weight sensors to records of how hard you brake and corner. Most drivers don’t realize how much information their cars are collecting and who has access to it, said Jen Caltrider, a privacy researcher at Mozilla who reviewed the privacy policies of more than 25 car brands and found surprising disclosures, such as Nissan saying it might collect information about “sexual activity.”
“People think their car is private,” Ms. Caltrider said. “With a computer, you know where the camera is and you can put tape over it. Once you’ve bought a car and you find it is bad at privacy, what are you supposed to do?”
Privacy advocates are concerned by how car companies are using and sharing consumers’ data — with insurance companies, for example — and drivers’ inability to turn the data collection off. California’s privacy regulator is investigating the auto industry."
New Year’s Eve: Musings on Y2K
At 3pm PST on 31 December, 1999, I sat down at the computer in my home office in Yakima, Washington. I logged remotely into the network at HQ and started monitoring our systems. The most critical moment would come at 4pm local time. We were in Pacific Standard Time (PST), -0800 UTC. In other words, at 4pm in Yakima, it would be midnight in Greenwich, England, where the time zone aligns with Coordinated Universal Time. (Coordinated Universal Time is abbreviated as UTC, not CUT, because there are actually other languages in the world besides English, and… never mind. Look it up if that story interests you).
Anyway.
The GPS satellites run on UTC, and our entire multi-state operation depended on GPS timing. My first hint of system failure because of a Y2K bug would occur at midnight, UTC.
Beginning at 3:55pm I began testing the major system once a minute. At 4:05pm I sent out the notice to corporate management that all was well.
I tested hourly, then, but the next critical moment wasn’t until 9pm PST, which was when midnight occurred on the US East Coast. Our equipment was all in MST and PST, but some of our many telecom providers might have systems with local time coordination in some other US time zone. (They’d all be using GPS now, but – this was 1999, and US telecommunications had plenty of legacy systems with other clocking methods).
In the end, nothing failed. Our entire system worked.
This wasn’t because Y2K was overblown.
It was because we replaced our billing system, which wasn’t able to generate an invoice after the date flip.
It was because we did software updates on several proprietary systems that would have failed.
It was because we did firmware updates, too.
Equipment inventories.
Application inventories.
Operating system inventories.
Software version inventories.
Firmware version inventories.
The reason January 1, 2000 seemed like such an ordinary day is because of the MASSIVE amount of work and money spent to make it ordinary. There are unsung heroes around the world who put in the work to update or replace systems that would’ve failed otherwise.
If you’re one of those people, I would love to hear your story.
A number of possible explanations have been proposed, from #NATO exercises to #Russia testing its jamming equipment. More information in this article (in Polish):
@CharlieMcHenry nothing new, since basically everyone is #oversharing their images with #metadata like #GPS in them and it's also trivial to #OSINT most images based off basic info about the photographers origin/place of residence as well as whereabouts...
That's no big deal, just basic #DataScience to the point that I think this should be mandatory about #journalism to be taught in #schools...