Live data from Hacker News

Go-based freegeoip.net now supports SSL for its API

freegeoip.net

21–30 of 38 posts

Re: Go-based freegeoip.net now supports SSL for its API

#23

fiorix, I am curious why you are using sqlite/redis as a store for the geoip data, instead of using cgo in conjunction with libGeoIP. Was it to enable updates to the geoip data if you get corrections (crowdsourced or otherwise)?

Some of the early versions used libgeoip, but the database has changed many times over time; it started with MaxMind data, then switched to ipinfodb.com, then ip2location.com came into the mix, and currently is back to using MaxMind again with a few tweaks. The idea is to be free to change to whatever is more suitable whenever is necessary... Redis was initially used in the Python version (twisted+cyclone) to share usage quotas between multiple instances (one per cpu), and ended up in the Go version just because; actually, it could use a map or something, but I'd have to implement the ttl part... In other words, it's mostly for historical reasons.

Re: Go-based freegeoip.net now supports SSL for its API

#30

For those unfamiliar, this free usage limit is much more relaxed than Google's Geocoder, which limits you to 2,500 free requests per day. https://developers.google.com/maps/documentation/geocoding/#...

Also note that Google's geocoder can only be used for results to be displayed on a Google map (mentioned in emptystacks's link, also section 10.1.1 (g): https://developers.google.com/maps/terms)
Post reply on HN