@matburt I'm not really a back end guy so having to write an oauth2 client is kind of a hassle to me. Also it seems using socket.io & node.js mean the app will require a server to run on. As it is now, even if my host die people could just get the source code and run the html, and I prefer it that way.
I don't use any concurrent requests spamming to boost the search speed, so even if someone search continuously it would be just like when he's clicking through pages, so I'm quite sure they won't get auto-blocked by the server. The requests are made from their own PC so it doesn't increase workload on my server as well (it's a very cheap one )