Possibly not made not possible from userland due to privacy issues. Apparently not even kernelland can see it, only
Bibliography:
- Stack Overflow:
- stackoverflow.com/questions/35934729/capture-fingerprint-from-smartphone-and-save-to-a-file
- stackoverflow.com/questions/63257762/how-to-save-and-compare-2-fingerprints-on-android
- stackoverflow.com/questions/67104186/can-we-use-android-fingerprint-scanner-to-get-finger-pattern-and-store-that-patt
- stackoverflow.com/questions/41632225/android-where-and-how-securely-is-fingerprint-information-stored-in-a-device
- android.stackexchange.com/questions/161780/where-does-android-store-fingerprint-data
- Reddit:
They actually use fingerprint minutiae, not raw images, which is cool.
This became a flag for the dissidents.
In this example we attempt to inject React elements into statically rendered HTML coming from the server, and properly hydrate them.
Questions by Ciro Santilli:
This is a minimal reproducible example for the terrible problem of external effects applying twice to refs for effects that are not idempotent and thus blowup if applied twice.
The issue is currently discussed at: react.dev/learn/synchronizing-with-effects#step-3-add-cleanup-if-needed (archive) which says "you need to cleanup the thing yourself". web.archive.org/web/20240720100401/https://react.dev/learn/synchronizing-with-effects#subscribing-to-events is also says that for the specific case of
addEventListener.But that's annoying! Can't we just somehow tell if we applied twice or not to avoid having to implement a cleanup? What if a third party system does not provide a cleanup at all?
Is the correct solution to just just have a
useEffect with empty dependency list? Seems to be good according to posts and to ESLint!Bibliography:
The goal of this example is to understand when states and effects happen when changing between different routes that use the same component.
Behavior is follows:
- visit: localhost:3001/1
- click
count++. This makescount: 1 - click "2" to visit localhost:3001/2
- outcome: count is still 1
This is likely because in React the state kept in the virtual DOM structure, and identical structure implies identical state. So when we change from post 1 to 2, we still have a
Post object, and state is unchanged.Next if we click:then the count is back to 0. This is because we changed the
- "Index" to go to localhost:3000
- "1" to go to localhost:3001/1
Post object in the DOM to Index and back, which resets everything.This example also illustrates how to prevent this from happening with
useEffect. There are unlisted articles, also show them or only show them.