Convert image to fingerprint file format by 
Ciro Santilli 34 Updated 2024-12-15 +Created 2024-08-27
Ciro Santilli 34 Updated 2024-12-15 +Created 2024-08-27Bibliography:
- stackoverflow.com/questions/37147480/convert-fingerprint-bitmap-to-iso-iec-19794-2-template
- stackoverflow.com/questions/33412977/how-to-convert-a-byte-array-of-fingerprint-image-to-iso-19794-2-in-java-basica
- stackoverflow.com/questions/43937986/convert-png-image-fingerprint-to-minutiae-xyt-fingerprint-format
Fingerprint imaging with smartphone by Ciro Santilli 34 Updated 2024-12-15 +Created 2024-08-27
Ciro Santilli 34 Updated 2024-12-15 +Created 2024-08-27Possibly 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.
A Conversation Between God and Man performed by Ding Chengyun
. Source. 
This became a flag for the dissidents.
Portuguese Wikipedia: pt.wikipedia.org/wiki/Seja_Marginal,_Seja_Herói
@cirosantilli/_file/nodejs/next/nodejs/next/inject-into-static by Ciro Santilli 34 Updated 2024-12-15 +Created 2024-08-27
Ciro Santilli 34 Updated 2024-12-15 +Created 2024-08-27In this example we attempt to inject React elements into statically rendered HTML coming from the server, and properly hydrate them.
Questions by Ciro Santilli:
@cirosantilli/_file/nodejs/next/nodejs/next/ref-twice by Ciro Santilli 34 Updated 2024-12-15 +Created 2024-08-27
Ciro Santilli 34 Updated 2024-12-15 +Created 2024-08-27This 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!Tried to do a React only reproduction at: react/ref-twice.html.
Bibliography:
There are unlisted articles, also show them or only show them.