Is there some means to monitor the queries it's sending (or hold and review before transmission) or throttle to avoid triggering abuse thresholds on any single domain?
> The case later took a turn, when Microsoft attempted to reframe it as a copyright dispute. VL was leaning on the EU's UsedSoft ruling, which established that secondhand software licenses could legally be resold. Microsoft changed tack and countered that Office's icons and help files made it a creative work...
This isn't unique to touchscreen interfaces. I have the same frustration when performing a sequence of keyboard commands and the OS can't keep up (or some other application or unwanted notification pop-up steals the focus).
I have a real problem with the pretense posed by the article that the club has no blame. They should have understood the risk they were taking on by subcontracting a vendor to collect passports, and better vetted that vendor. Obviously the service provider was completely inept, but that doesn't absolve the fools using them.
I preach to my clients this sort of PII should be treated as a toxic, hazardous substance. Ideally don't touch it with a 10 foot pole, and if you can't help it then limit the scope, protect it with strong access policies that severely limit who can touch it (including encryption keys conservatively custodied), and securely delete it all as soon as possible.
Too many companies these days point you to shoddy third parties for some kind of functionality (e.g. book an appointment, perform KYC on you, host the online learning platform for your course, etc.), inappropriately foisting both a new business relationship on you that you never asked for along with their partner's terms of service that you have no bargaining power in negotiating.
This is a side-effect of the SaaS era, and the model is broken.
The same time every day, around 11pm, I go to the kitchen, select two different treats, say the word “choice”, and present the treats in either hand, allowing Bebop to only take one... By the time the experiment started, Bebop was used to the routine and sniffing both treats before taking one.
Winner was Pur Luv Chicken, closely followed by MON2SUN duck + rawhide. Greenies and Pork Chomps fared poorly.
With those slower drives, programmers tended to be more careful about not wasting those preciously expensive I/O's - they had to put more care into architecture, often resulting in more optimized, efficient code. And since lags were expected, they handled waits more elegantly - hence the hourglasses and such. This immediate feedback even when there was a delay is what made the experience feel more responsive.
Modern apps that ship with browser engines just to show some UI are hugely bloated by comparison.
You also didn't have dozens of different telemetry, update, crash collection etc. services constantly running in the background eating up resources and I/O's. Go into Event Viewer, Services, and Scheduled Tasks on a pre-Win7 era workstation and you see how much less crowded it is.
This is such a typical pattern of enshittification from Microsoft. Something Windows 3.1/95/2000/XP made easy - adding a File Type Association - became increasingly contorted over time.
If I recall correctly, in Windows 7 they removed the File Types Manager and you had to either edit the registry directly to adjust existing associations, or resort to a third party app.
By Windows 10 even simply creating a new association for an unrecognized extension seems to require more clicks and scrolling down to a hidden option.
I would love to meet the mastermind morons behind this himan-unfriendly UI and give them a piece of my mind.
Will the $60B be newly minted SPCX shares? Does this effectively dilute investors by about 2-3% (minus some fraction representing the fair value of Cursor)?
Is there some means to monitor the queries it's sending (or hold and review before transmission) or throttle to avoid triggering abuse thresholds on any single domain?