johnrichter / beacon Goto Github PK

We can build a list of possible usernames by using common short configurations of first/middle/last names, domain names, social media profile urls, and information from social media API calls.

Use the first_name, last_name, and middle_name parameters

Using the list of usernames and domain names, attempt to determine the user's email address(es), verify they exist via pinging the appropriate mail server and obtain supplemental information from clearbit.com.

Mail servers can be found via MX records.

Some APIs have monthly caps (Clearbit is 50/mo) and we don't want to use them up in one day.

Choose some public figures, and private figures to capture someone easy to find and someone hard to find.

We need to use the AngelList, Twitter, and LinkedIn APIs, all of which require OAuth to query the endpoints we need to find out a person's contact information.

Simple Route: Have all users create dev applications on each service and give us the tokens.
Better Route: Have users authenticate this app against their credentials so we may contact the APIs on their behalf.