Elucalidavah
Joined 11 years ago
Joined 11 years ago
I wonder how feasible is it to use a separate phone and access it remotely from the main phone.
If all events need to arrive, then the problem is not "notification" (which would be solved by webhooks) but "database replication": subscribe to new events, fetch the full snapshot, fetch the updates in range, have the monotonic value to establish the "range" in the first place. Reach the eventual consistency.
The proposed SCROLL handles half of these, which limits its use-cases.
That 'tapping phones' could also be used to facilitate key exchange verification, making that chore technically useful.
Then again, that would be better done in an open-source app and not tied to any particular domain.
What's your PM2.5 baseline, and did you measure TDS in the water?
Have you looked at EasyOCR?
Count the amount of `Any` / `unknown` / `cast` / `var::type` in those codebases, and you'll notice that they aren't particularly statically typed.
The types in dynamic languages are useful for checking validity in majority of the cases, but can easily be circumvented when the types become too complicated.
It is somewhat surprising that dynamic languages didn't go the pylint way, i.e. checking the codebase by auto-determined types (determined based on actual usage).
Is anything preventing the provider from denying a SIM swap based on IMEI?
See "But how do we solve arrays" part:
> > .map() is special. It does not send JavaScript code to the server, but it does send something like "code", restricted to a domain-specific, non-Turing-complete language. The "code" is a list of instructions that the server should carry out for each member of the array