jonathan-kosgei

Airfare

More like a list of every proxy providers proxies

>>> import requests

>>> data = requests.get('https://www.cryptocompare.com/api/data/coinlist/')

>>> data = data.json()

>>> len(data['Data'].keys())

2148

I thought this was a troll on every cryptocurrency ever

If you need a way to identify EU users then you can do so via our IP Geolocation API (ipdata.co) that returns an `is_eu` flag. Then do whatever you like.

https://ipdata.co - a Free IP Geolocation API I've been working on the last few months

Docker 1. What containers, images, image repositories are and how to create them 2. How to write a simple Dockerfile and build it into an image 3. Launching multiple containers with docker-compose 4. Basic docker commands, starting, deleting containers, listing running containers, checking container logs, exec'ing into a container, deleting images, running daemonized containers etc

AWS 1. Creating an ec2 instance 2. Writing a lambda function 3. s3

This is very non-exhaustive but would cover the very basic. Good luck!

For Nosql try writing something simple with redis, look at mongodb etc

You could use Ingresses, the nginx controller has the widest support and feature set, that would handle managing sockets for your application.

Our API now supports Tor Exit Node detection: https://api.ipdata.co/103.10.197.50, you can also try it against a current list of Tor Nodes here https://check.torproject.org/cgi-bin/TorBulkExitList.py?ip=1...

Hi gsqaui, our API now supports detecting Tor nodes https://api.ipdata.co/103.10.197.50

Our API now supports detecting Tor nodes https://api.ipdata.co/103.10.197.50

We're working on creating our own offering on this. We'll have Tor Exit node detection first and are planning to make that generally available to all our users within the week at no extra cost.

IP Geolocation might never be the silver bullet for determining user location. Like I've mentioned before if it can't pin you exactly it'll give your co-ordinates as being at the center of the population. Use it where you're okay with having a general idea of your user's location or as a fallback where other means of geolocation are not available eg. via browser, or GPS via mobile apps

Just a few reasons why to use Ipdata;

1. Currency Data - The user's country's Currency ISO code and symbol are returned in the API output.

2. Phone Code Data - The user's country's Calling code is returned as well.

3. Global Footprint - Endpoints in 10 locations globally. 4 on both US coasts, 1 in Canada, 2 in Europe, 1 each in Mumbai, Seoul and Sydney. This ensures you get pretty low latencies wherever your app is hosted and wherever your end users are located.

4. Solid Infrastructure - The infrastructure backing Ipdata is pretty impressive, and built to scale to a substantial amount of traffic - in the hundreds of millions.

5. A free tier of 1500 requests daily (45 000/month) with no signup or credit card needed.

6. Examples in multiple languages on the Docs page at https://ipdata.co/docs.html, to make integrating with your site absolutely painless.

7. Regularly updated data - we check for changes daily and regularly update our data.

Coming soon; VPN/Proxy and Tor exit node data.

Fixed https://github.com/ipdata/python/blob/master/ipdata/ipdata.p... will add enhancements when I can.

You're right. I guess it makes sense to let Request's exceptions propagate in case there are network issues. I'll work on ensuring pep-8 adherence and adding custom exceptions for the error codes in https://ipdata.co/docs.html#status-codes

You're absolutely right! Not sure how/why that got in there in the first place. I'm fixing a new release right now. I'm also going to have the repo/package cleaned up.

Pushed a new release: https://pypi.python.org/pypi/ipdata/2.6

Too cool! Ping me at jonathan at ipdata dot co and I'll set you up with free api keys for this! :) We can also talk about adding including some examples on the docs page.

That sounds like a great idea, I'll consider adding this, is there a specific use case for this format?

Removed the link :)

Geoslack looks really cool!! Using it as a fallback when location isn't allowed via the browser or if within an app from GPS would be a valid and common usecase!

I'd say you can pretty much trust it up to the country level and greater region, more specific than that the results will not always be highly accurate.

Fixed the front page.

Thank you for sharing your need for this. I'm going to make this a priority. If you'd send me an email jonathan at ipdata dot co, just a quick hello, I could keep you up to date on our progress as we develop this.

We actually haven't setup our Google+ presence yet.

Thanks coderholic! :). I took a lot of inspiration from your service but built around solving a number of pain points. Would love to chat and talk sometime :)

Good point, I think there's another way we could do it. Let me fix that.

Yeah definitely, you can reach me at jonathan at ipdata dot co. Feel free to reach out any time!

Please send an email to jonathan at ipdata dot co or support at ipdata dot co

I don't mean to take anything away from freegeoip, this is basically the self-hosted vs external API debate that I've already responded to here. In short, there're cases where each solution shines more than the other.

Right, this is why we have multiple copy-pasteable examples in different languages. To make it as straight forward and quick as possible to get started.