5 ms·
I feel like i'm missing something obvious here. This is for "webapps" which have been "licensed". Who is running licensed webapps without some form of user acco
by masukomi 8y ago
I feel like i'm missing something obvious here. This is for "webapps" which have been "licensed". Who is running licensed webapps without some form of user account? Either a login or an API key, which can easily be turned off if the person stops paying. If i have that, why do i need this? If i don't have that, haven't i just totally fallen down on the job of controlling access to my system?
What am i missing here?
- albertgoeswoof 8y agoIt's for on-premise deployments, where you don't have control over the deployment environment.
- masukomi 8y agothanks @albertgoeswoof "The small piece of code is designed to only invalidate and deny access when a valid response is returned from our servers." seems pretty easy to circumvent but... i guess you could make your app stop working if it fails to get a response within x days or whatever, but you'd have to use a compiled language to make that even remotely difficult to not circumvent too.
- theoctopus 8y agoI think the primary purpose is the notifications, not the blocking. Even if they browse to the page once, see the block and disable it, you'll still know.