This is especially disappointing considering the time, legal and administrative effort and money will be spent on trialing and detention of alleged non-citizens.
For a government which has attained a historical majority for the second time, just imagine the impact they can have if they focussed this energy on improving economic and human-life indicators instead. India still ranks 103 on the world hunger index, even below its less developed neighbour – Pakistan.
I hope they don't squander this majority away, but I fear they will.
TLDR;
A gas supply utility, Indane, provided an un
-authenticated, non-rate limited API proxy to the authenticated Aadhar API, allowing anyone to make more than a thousand requests a minute to fetch personal information, by just iterating through the Aadhar numbers.
Not to mention the numerous results from Google SketchUp and Autodesk SketchBook that popup when you're searching for "sketch <help-me-with-something>"
As someone who has developed for mobile web, it can be surprisingly hard to push back on bloat from marketing / seo / analytics teams. I hope this becomes a W3C standard so us developers can show them the finger the next time they want to bring mobile web to a crawl.
Does Google not have any guidelines that say to keep pages small and fast? Seems like they should have a list of things to keep in mind when looking at search-rankings
The problem doesn't seem to be related only to web. These dark interstitial patterns are present in every platform.
Recently used Ola's (Uber's main competitor in India) native app on android, and right when you're about to book a pool ride, at times, they'll show you a full page interstitial advertising pool rides. And if that wasn't ridiculous already, they provide no way to cancel the popup. The only way to proceed is by clicking "Try share".
And when you do so, it throws a generic "Uh Oh, Something went wrong error", and you're basically stuck without a ride.
Marketing teams are usually data driven rather than user experience driven.
How does one counter the argument that "anecdotal evidence suggests people who sign up with us are 2x more likely to convert, so let's force more sign ups to increase revenue".
But it's easier for them to extrapolate data and say, hey, we couldn't get emails of xxx thousand users, so we lost xxx amount, vs our argument that they probably lost a number of users who were annoyed by the popup.
Except, you can count conversions, but you can't "measure annoyance"
What's disheartening is that many websites have started finding workarounds to show these interstitials after a delay or in between screen transitions.
The inherent problem is that app experiences somehow lead to better conversions, and no company would want to lose revenue due to dropped install numbers.
I think cancelling HTTP requests is quite a useful in some scenarios.
Eg 1) Say you're fetching heavy json/binary data on an user action, and before data arrives, he changes his action. Not only do ypu download all of the extra data, but the fetch for the next action is slowed down like hell.
Not sure, but does this mean that I can't cancel a heavy file upload if a user changes his mind?
For a government which has attained a historical majority for the second time, just imagine the impact they can have if they focussed this energy on improving economic and human-life indicators instead. India still ranks 103 on the world hunger index, even below its less developed neighbour – Pakistan.
I hope they don't squander this majority away, but I fear they will.