I’m sceptical about this idea but, to give it full credit, it’s a custom piece of hardware that would presumably be more accurate than previous software-only attempts. Maybe it will actually work this time, idk, although I still don’t really see the point.
>>While you type, the keyboard quietly records how you type — the rhythm, the pauses between keys, where your finger lands, how hard you press.
>>Nobody types the same way. Your pattern is as unique as your handwriting. That's the signal.
This very precisely makes my point:
Yes, the typing pattern of any human is highly and possibly even completely unique to that human — UNTIL any of a myriad of everyday issues makes it falsely deny access because the human's typing pattern has changed in a way the human can't do anything to fix at the moment.
If you are only attempting to distinguish a human from an automated system, it'll be better, until someone just starts recording the same patterns and re-playing them to this upstream process; then its a mere race to who can get their hooks in at a lower level. And someone is always going to say: "Oh, this system can identify the specific human", and we're off to the races again.
So, no. Unless you can account for ALL of the reasonable everyday failure modes, typing with either hand, any finger or combination of fingers out of commission for a minute or a lifetime, this idea will fail.
IOW, if you are doing this, it does not matter what you are doing afterwards.
You are assuming that a human's particular typing pattern is consistent, when the fact is that any number of ordinary events will render your assumption false (one or more fingers bandaged, sprained, whatever, or one hand occupied ATM).
This is not a hardware or software problem, and no amount of code, hardware, or cleverness will fix it; this is a fundamental mismatch between your assumption vs reality.
That indemnity clause is only for Team, Enterprise and API users. Do you know what was used here?
Also the commercial version is limited to “…Customer and its personnel, successors, and assigns…”. I am very much not a lawyer and couldn’t find definitions of these in the agreement but I am not sure how transferable this indemnity would be to an open source project.
This post reminds me of a 14-year old boy reading the MS-DOS manual to figure out what AUTOEXEC.BAT and CONFIG.SYS at his younger brother’s football games.
If you are truly incapable of even imagining the objections (that you might disagree with!) you should probably get out of your bubble and expand the content you consume.
This is great! I have been meaning to implement this sort of thing in my existing Shortcuts flow but I see you already support it in Shortcuts! Thank you for this!
No corporate body ever admits wrongdoing and that's part of the problem. Even when a company loses its appeals, it's virtually unheard of for them to apologize, usually you just get a mealy mouthed 'we respect the court's decision although it did not go the way we hoped.' Accordingly, I don't give denials of wrongdoing any weight at all. I don't assume random accusations are true, but even when they are corporations and their officers/spokespersons are incentivized to lie.
>I keep seeing folks float this as some admission of wrongdoing but it is not.
It absolutely is.
If they knew without a doubt their equipment (that they produce) doesn't eavesdrop, then why would they be concerned about "risk [...] and uncertainty of litigation"?
It is not. The belief that it does is just a comforting delusion people believe to avoid reality. Large companies often forgo fighting cases that will result in a Pyrrhic victory.
Also people already believe google (and every other company) eavesdrops on them, going to trail and winning the case people would not change that.
reply