3 ms·

Hi Ruphin, Frits from Qeys here. I highly appreciate your comment and I totally agree with what you're saying. Not being able to reach our servers should not br

by frits1993 8y ago

Hi Ruphin, Frits from Qeys here. I highly appreciate your comment and I totally agree with what you're saying. Not being able to reach our servers should not break your app. The small piece of code is designed to only invalidate and deny access when a valid response is returned from our servers. That means that if our service is unreachable you won't be notified about invalid use, of course, but the app assumes the positive and allows everyone access until a valid "denied" response. Did you experience the contrary, or was this simply not clear from what you read? In that case, I'll try and add that to the FAQ section.

macca321 8y ago
Does this mean that they can access the site for free by blocking qeys.io?
- cdurth 8y ago
  From above, it would sound like it O.o
  - azeirah 8y ago
    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..
- frits1993 8y ago
  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.
- jpambrun 8y ago
  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.
- imtringued 8y ago
  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.
Ruphin 8y ago
Here's what I read from the FAQ: In a very bad scenario where our service is slow, the worst thing that happens is a user being able to use the web app for a couple of seconds before it is denied access. I understand now that you mean in case the website is an unauthorized copy the end user will be able to use it for a few seconds before it is disabled. In that case I retract my previous comments, but I would suggest changing the wording in the FAQ here to be more clear. :)

macca321 8y ago

Does this mean that they can access the site for free by blocking qeys.io?

cdurth 8y ago
From above, it would sound like it O.o
- azeirah 8y ago
  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..
frits1993 8y ago
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.
jpambrun 8y ago
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.
imtringued 8y ago
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.

Ruphin 8y ago

Here's what I read from the FAQ: In a very bad scenario where our service is slow, the worst thing that happens is a user being able to use the web app for a couple of seconds before it is denied access. I understand now that you mean in case the website is an unauthorized copy the end user will be able to use it for a few seconds before it is disabled. In that case I retract my previous comments, but I would suggest changing the wording in the FAQ here to be more clear. :)