There seems something a bit ironic or maybe recursive about having to provide my own email address to be able to easily search someone else's emails.
Then maybe you will get hacked and someone else will put up a dataset containing my email address. Ah, the world we now live in.
The login requirement was only to prevent garbage requests. No intention to use the email addresses for any purpose other than authentication.
Oh, I know. I make my customers give me their email addresses, too, and I'm happy to provide it. It just felt circular, that's all.
Just use a disposable email address like 10 minute mail, that's what they're for.
This is pretty good, the folks in the security space could proabably use this for analysis. Any intention to inform organizations such as the center for security policy?
But why?
Was this directed at the previous commenter or the API itself?
I would guess the API, since the WL page for the Clinton emails already has a search facility. Is this a school project?
We decided to build this after a friend and I discovered that you couldn't really quantify the Clinton emails. Yes, you can search on WL or WSJ, but it's much harder to gain any data-driven insights from that. Yes, you can search for "Benghazi", but can you query against a list of nearby Libyan cities, or run all emails containing the strings "Bernie" or "Sanders" through a sentiment analyzer, etc.
Not a school project, though it was a hobby project.
I must have missed the parts of the API docs that describe sentiment analysis and geofencing queries.
Curious why the domain was registered through Domains By Proxy.