Live data from Hacker News

I made a simple geolocation service

maxkostinevich.com

71–80 of 187 posts

Re: I made a simple geolocation service

#71

The cheapest alternative has to be to ask the users where they are and store it on the user device? I never understood the need for geoip unless you ship spyware. If the exact location is important geoip is not accurate enough anyway. Forwarding to regional sites automatically is just annoying when it doesn't work properly or someone is traveling abroad.

1) Users don't want to be asked where they are 2) GeoIP has plenty of uses that go beyond spyware

Re: I made a simple geolocation service

#72
This only work’s if geocoder is accessed directly from browser. It will not if you need to geocode ip addresses received in other ways on the server side.

I guess it’s ok for a basic consumer website, although it’s not exactly equivalent to ip geocoder databases/services - they allow passing ip addresses as part of geocoding request.

Re: I made a simple geolocation service

#74

The cheapest alternative has to be to ask the users where they are and store it on the user device? I never understood the need for geoip unless you ship spyware. If the exact location is important geoip is not accurate enough anyway. Forwarding to regional sites automatically is just annoying when it doesn't work properly or someone is traveling abroad.

If it's just to route to regional sites, that's fine. Letting the user select just makes sense.

However, there's a lot of use cases that semi-accurate geo-locations make sense. The first of which is analytics. If I'm a marketing person at a SaaS company, I want to know where my customers physically are if possible for a variety of useful reasons.

Good quality estimates for location also help with security and compliance use cases as well. If a user logs in from a new country on the opposite of the world, you can flag that and take whatever action you want whether it's to block them, fire off an email to the person who owns the account or whatever.

Re: I made a simple geolocation service

#75

https://ifconfig.co/

I got this:

"Application error An error occurred in the application and your page could not be served. If you are the application owner, check your logs for details. You can do this from the Heroku CLI with the command heroku logs --tail"

Re: I made a simple geolocation service

#77

The cheapest alternative has to be to ask the users where they are and store it on the user device? I never understood the need for geoip unless you ship spyware. If the exact location is important geoip is not accurate enough anyway. Forwarding to regional sites automatically is just annoying when it doesn't work properly or someone is traveling abroad.

I can provide you a valid user centric use case: we have shops in different cities, we can preselect on the order form the closest one according to the city, if the customer chooses the pick up delivery method (faster than courier). We don't need to be more precise that this and asking the user defeats the purpose, it will have to take another action just to allow this. We don't do anything else with this information.

Re: I made a simple geolocation service

#78
post #59

Earlier quoted context omitted.

I always find it funny when people brag about cost savings on cloud services while overlooking the insane premium they're paying by using the "cloud" to begin with. It's kinda like a construction firm using a supercar to haul materials and then bragging about their efforts to make cosmetic repairs cost-effective... maybe you could just not use an overpriced car to begin with and then damage won't be an issue?

The main advantage of the cloud for me that it provides PaaS services. You don't have to administer a VM, etc, you just use the services and it's someone else's job to install security updates and stuff.

Installing updates and stuff is easy to automate.

Re: I made a simple geolocation service

#79

The cheapest alternative has to be to ask the users where they are and store it on the user device? I never understood the need for geoip unless you ship spyware. If the exact location is important geoip is not accurate enough anyway. Forwarding to regional sites automatically is just annoying when it doesn't work properly or someone is traveling abroad.

We have had clients that need it for content licensing requirements, it doesn't make sense to allow users to choose their region in a scenario where content is region dependent.

Of course, you can just get around this with a VPN.

Re: I made a simple geolocation service

#80
TECHNIQUE: use the proprietary HTTP Request headers available through CDN/Cloud providers like Cloudflare Workers' cf-country [1], Amazon CloudFront's CloudFront-Viewer-Country [2], and Google App Engine's X-Appengine-Country/-Region/-City/... [3] to get client Geolocation data.

[1] https://developers.cloudflare.com/workers/reference/apis/req...

[2] https://docs.aws.amazon.com/AmazonCloudFront/latest/Develope...

[3] https://cloud.google.com/appengine/docs/standard/go/referenc...

Post reply on HN