I'm a Systems Reliability and DevOps engineer for Netdata Inc. When not working, I enjoy studying linguistics and history, playing video games, and cooking all kinds of international cuisine.
Even if they store it in the database, they have to correlate with some unique user identifier, which by definition has to be stored client-side. It's just not possible to reliably uniquely identify a client any other way. Given that it's also not possible to reliably identify that someone cleared local storage or is using incognito mode, there's not really an way to work around people bypassing limits like this.
Even if they store it in the database, they have to correlate with some unique user identifier, which by definition has to be stored client-side. It's just not possible to reliably uniquely identify a client any other way. Given that it's also not possible to reliably identify that someone cleared local storage or is using incognito mode, there's not really an way to work around people bypassing limits like this.
Yup, I think that's too hard to prevent people bypassing limits :D