Hacker News Reader

Yes, it does. Qeys is not designed to deny user access to protected sections of an application, though.

The ideal use case is a web app (e.g. awesome dashboard) you built and is ran on premise on one of your clients' servers. Their dayjob isn't pirating software, so blocking qeys.io probably has not been on their to do list.

But yes, if qeys.io is blocked, no validation takes place.

They would have to instruct all their users to start blocking qeys.io. Looks like this isn't designed to be foolproof, but to deter most from cheating.

I don't think the primary purpose of qeys.io is to block users of the webapp. The purpose of qeys.io is to block customers (not users) from hosting the webapp without your permission.

From above, it would sound like it O.o

That solution might sound absurd, but what's the alternative? I implemented my own basic license validation server for an application I wrote, and I ended up doing the exact same thing.

My server may go down every now and then, I don't want to deny access to the application just because my 5$/month server is too busy at the moment..