jks

I see those occasionally and don't quite understand them. But I also haven't spent any time trying to track them down. My guess would be some buffering problem where a configuration save command from a prior admin session is leftover someplace and gets flushed out to the Kiwi during the next connection (the arrival from China in this case). I don't believe anything malicious is going on here.

October 7/8: Massdrop is active again for 7 days. $80 discount on the Kiwi kit ($219 vs $299). Free (but slow) shipping to the USA. Best deal out there. Limited quantities available and over 70 people were on the notification list. So don't delay.

v1.238 is out that uses the new map provider. There are still many problems (you don't have to report them, I know what most of them are). But the new maps are now better than the current Google situation. To revert to using Google maps start the TDoA extensions in the URL and use the "gmap:" option, e.g. "my_kiwi:8073/?ext=tdoa,gmap:"

You'll note some serious problems:

• The map tile provider doesn't yet have high-resolution satellite imagery except in some special areas (e.g. The Netherlands). They're working on improving this situation. It's also possible we can use multiple providers if the licensing terms are acceptable.
  
• Sometimes not all the map tiles appear (or are clipped).
  
• Sometimes the markers point at the wrong locations as the map is zoomed.
  
• Lots of minor things like the day/night overlay getting lost on kiwi-map / result-map switches etc.
  
• As usual, things seem to be worse on iPad and no doubt other mobile devices.
  
• I'm not completely sure, but some of the mapbox-gl code might contain Javascript ES6 which means it might not work on older browsers.
  
• The marker and cluster colors aren't that good and are not final.
  

On the plus side there are a few improvements:

• The layer icon at the top right of the map lets you select 6 different base maps.
  
• The TDoA options list lets you toggle the Kiwi host markers, same as for the reference location markers.
  
• The "quick zoom" menu has a new entry for the entire world.
  
• The "old map" option has been removed as taking the coastline plotting out of the Octave script will speed up the TDoA process for everyone.
  

v1.238 is out that uses the new map provider. There are still many problems (you don't have to report them, I know what most of them are). But the new maps are now better than the current Google situation. To revert to using Google maps start the TDoA extensions in the URL and use the "gmap:" option, e.g. "my_kiwi:8073/?ext=tdoa,gmap:"

You'll note some serious problems:

• The map tile provider doesn't yet have high-resolution satellite imagery except in some special areas (e.g. The Netherlands). They're working on improving this situation. It's also possible we can use multiple providers if the licensing terms are acceptable.
  
• Sometimes not all the map tiles appear (or are clipped).
  
• Sometimes the markers point at the wrong locations as the map is zoomed.
  
• Lots of minor things like the day/night overlay getting lost on kiwi-map / result-map switches etc.
  
• As usual, things seem to be worse on iPad and no doubt other mobile devices.
  
• I'm not completely sure, but some of the mapbox-gl code might contain Javascript ES6 which means it might not work on older browsers.
  
• The marker and cluster colors aren't that good and are not final.
  

On the plus side there are a few improvements:

• The layer icon at the top right of the map lets you select 6 different base maps.
  
• The TDoA options list lets you toggle the Kiwi host markers, same as for the reference location markers.
  
• The "quick zoom" menu has a new entry for the entire world.
  
• The "old map" option has been removed as taking the coastline plotting out of the Octave script will speed up the TDoA process for everyone.
  

Progress, but still a long, long way to go:

Progress, but still a long, long way to go:

Progress, but still a long, long way to go:

Progress, but still a long, long way to go:

@Kevin Not a problem at all. What led me straight to the bug was the report in the other thread: click the "kick" button on a WSPR auto-run connection and the server crashes.

Okay, I see the bug. It was actually introduced in v1.235 but doesn't get triggered until a restart (like when updating to v1.236)

I'll fix it in today's update. But the issue now is that you'll either have to temporarily turn off WSPR auto-run or go through the manual update procedure one more time to get past this problem.