Uman Shahzad

Yeah it'd be great for sure. Will keep it in mind.

@nick-lironi-irvine You could only get a 403 if your token was invalid. Can you confirm it isn't gibberish before calling `handler.getDetails()`? (You can check `handler.access_token`). Also can you confirm that...

We could throw a special error type `APIError()` which takes the JSON body as a parameter. Will add this at some point, sure!

@SobanMahmood can you check this one out when free.

Yeah a `quota` subcommand would be nice. But we probably need a different endpoint for this as the existing one gives potentially confusing data, like when it says `limit`/`remaining`, what...

Tagging this as something we can do for v2.

I guess the flow could look like: ```bash $ ipinfo signup Fullname: Email: Password: Signing you up... Done! Please check for a confirmation code. $ ipinfo signup-confirm Code: Confirming... Done!...

Oh that's really nice, I especially like that it consolidates the login process into it in a simple way. Right, so: 1. We can make a strongly rate-limited endpoint for...

Right, that reduces one endpoint needed, and the `/signup/cli/` endpoint can do the actual pairing of id+ip, and pinging + getting the token will require both. Looks well-fleshed out to...

Tagging this as something we can do for v2.