This conflicts with the "for now" on the linked page. I would also recommend actually explaining how it works in the "How it works?" section, instead of hand-waving it away with "we convert it on our service and collaborate with other services." I also cannot find a privacy policy anywhere.
It's a bit ironic that the 'random' IP address you used in your demo (8.8.8.8) is anycast, which means that geographically, it is located at hundreds of sites all over the world.
You might want to expand on what you mean by "IP geolocation" and exactly how you are creating your mapping from IP to geographic location.
They said they are scraping other sources. So it's the RIR data from whois, rdap or the delegated files, modulated through curated lists like maxmind, and collections from GEOFEED sources as defined in the rfc.
There are other models. I'd be surprised if they do any triangulation (for instance) because it's success rate in finding errors or misreporting in the above is low, unless you are Akamai and have 400+ points of BGP to get closest match from.
I can't wait until somebody invents a solution to prevent geolocation via IP. It's a pointless "feature" that has big privacy implications, and if you really need location or region information, we have much better tools for that.
> It's 100% free with unlimited uses—no catch
This conflicts with the "for now" on the linked page. I would also recommend actually explaining how it works in the "How it works?" section, instead of hand-waving it away with "we convert it on our service and collaborate with other services." I also cannot find a privacy policy anywhere.
> Read more about the Ip2Geo at https://minilibs.com/ip2geo.
Also, this link on your NPM page simply redirects to a mostly-empty Github profile.
As currently presented, I do not find this service trustworthy.
It's a bit ironic that the 'random' IP address you used in your demo (8.8.8.8) is anycast, which means that geographically, it is located at hundreds of sites all over the world.
You might want to expand on what you mean by "IP geolocation" and exactly how you are creating your mapping from IP to geographic location.
They said they are scraping other sources. So it's the RIR data from whois, rdap or the delegated files, modulated through curated lists like maxmind, and collections from GEOFEED sources as defined in the rfc.
There are other models. I'd be surprised if they do any triangulation (for instance) because it's success rate in finding errors or misreporting in the above is low, unless you are Akamai and have 400+ points of BGP to get closest match from.
I can't wait until somebody invents a solution to prevent geolocation via IP. It's a pointless "feature" that has big privacy implications, and if you really need location or region information, we have much better tools for that.
it's called "VPN"
Not really possible with how internet routing works, routing tends to correspond with the layout of physical infrastructure.
Plus, your IP will always have at least a sovereign state due to the ASN associated.
This looks similar to iplocate.io, which I’ve run since 2017. There are also plenty of others.
Free and unlimited is going to be a tough deal to maintain forever if it gets popular. Good luck!
Feel free to reach out if there’s anything I could help with