Show Posts
You can view here all posts made by this member. Note that you can only see posts made in areas to which you currently have access.
Thanks. Is it legal to transmit false IDs?
I’m not sure what you mean by anonymous? Data transmitted on ADSB and mode S carries the proper hex code. It’s a core part of the standards. I think it’s a massive manipulation of the ecosystem if the codes of aircraft are collected from OGN and then scrambled by SS? Do OGN know you’re doing this?
If the intent is to protect the personal identity of the pilot then their ownership details with the aviation authority should be anonymous. Not the call sign.
Thanks for copying the reply, it’s pretty clear now. Indeed, to guarantee being anonymous when needed from SafeSky to OGN, we are creating a hash of the internal id. In this specific case, since the PAW id was encoded in safesky (would be the same for an ads-b or mode-s ICAO hex), we should simply respect and pass over the entered id. That way, PAW will receive it and will be able to deduplicate the traffic naturally.
Thanks a lot for raising this point to us, we are going to take an action and fix this.
Fly safe,
Tristan
SafeSky assumes you wish to remain anonymous. For callsign to show you need to go into settings bottom right. Then on next page click top right above your profile name. This now enters your profile info. Scroll down until you see Public Profile and switch this on. Now click save top right. I would then log out and log back in. You should now, and everyone else, see your call sign instead of just your aircraft symbol. Cheers
@marioair
could you tell your friend to turn on his safesky, I am monitoring the data feed and want to see if the ICAO address re-appears
thx
Lee
I just checked for your flight, and I can see the traffic from hex code 40651B:
from PilotAware
as MODE-S using multi-lateration
as SafeSky from the app
By design, SafeSky will show the most up-to-date and precise traffic location, regardeless of its source.
There is nothing in our logs that relates to 393F76. Could you please followup with PilotAware, and share with us their findings? Could it be that they do not de-duplicate traffic and were generating ghost alerts in PAW?
I suspect that on SafeSky, there was no alerts, since those 3 sources were you.
393F76 is not registered in SafeSky transponder list.
