quits immediately
Response from developer
Can’t argue with any of that — v1 crashing on launch was less a bug and more a personality trait. We didn’t patch it, we replaced it. v2 is a ground-up rebuild that actually opens and stays open. If the support link still 404s on you, reply here directly and we’ll fix you personally, out of spite for our old website.
Doesn’t do anything.
Response from developer
You’re right, and that one’s genuinely not on you. v1’s US frequency data came from a third-party database, and that provider quietly went out of business — taking US search down with it without us changing a single line of code. Great business model for them, less great for you. v2 rebuilds US coverage in-house as part of a proper 60+ country database, so it’s back, and it’s no longer riding on some other company’s server staying online.
Did not work at all for also!!!
Response from developer
Sorry about this one — v1’s US frequency data came from a third-party database that had already gone out of business by the time you tried this, so the address box was asking for details it had nowhere left to send. Not a great experience, and not a great look for us for depending on it in the first place. v2 replaces that pipeline entirely with native coverage across 60+ countries, so Los Angeles is back on the map — literally.
Did not work at all for me
Response from developer
The map wasn’t broken, exactly — it was faithfully querying a US data source that had already shut down, which from where you’re sitting is a distinction without a difference. v2 rebuilds that coverage in-house across 60+ countries instead of leaning on a single external vendor’s continued existence. Update and your city should show up properly now.
