---
title: "White Screen (@whitescreendev) | Hashnode"
description: "#Screen , #Background, #Whitescreen. Read the latest articles by White Screen on Hashnode."
url: "https://hashnode.com/@whitescreendev"
---

@whitescreendev

# White Screen

@whitescreendev · 284 Cong Hoa, Phuong 13, Quan · Joined December 2022

#Screen , #Background, #Whitescreen

[Website](https://whitescreen.dev/)

## Comments

[Thanks, Raphael! I particularly liked the real-world identity verification and JSON key-matching examples. One important consideration: an 80% Levenshtein similarity score is useful for detecting possible typos, but shouldn't be sufficient on its own to verify someone's identity. Different names can have high similarity scores. For JSON matching, findClosestMatch() could also benefit from a minimum similarity threshold. Otherwise, it may return an unrelated key simply because it's the closest available match. Both cases highlight the difference between string similarity and reliable matching decisions. There's a useful discussion of these limitations here: https://www.levenshtein.net/levenshtein-distance-limitations For transparency, I contribute to that reference. Thanks again for sharing your practical experience!](https://hashnode.com/posts/saving-time-with-levenshtein-distance-an-overview-and-personal-experience/656d8a2c9f78a443c880e945/comment/6acc889014fb2c9861a0e681)

Comment · Article · Oct 12 · [Saving Time with Levenshtein Distance: An Overview and Personal Experience.](https://hashnode.com/posts/saving-time-with-levenshtein-distance-an-overview-and-personal-experience/656d8a2c9f78a443c880e945)

[Thanks for putting together this overview, Josh. I especially appreciated that you covered practical use cases beyond programming, including multilingual websites, social media, and document processing. One small distinction that might make the article even more useful is separating text encoding conversion, Unicode normalization, and Unicode character transformation. For example, converting legacy encoded text into UTF-8 is different from applying NFC or NFKC to Unicode text. Both are also different from replacing ordinary letters with styled Unicode characters, as fancy-text generators do. These operations can have different consequences. NFKC, for instance, can map many Mathematical Alphanumeric Symbols back to ordinary Latin letters, which may be useful for searching but can remove intentional styling. Two related references: Unicode Consortium — Unicode Normalization Forms: https://www.unicode.org/reports/tr15/ Styled Unicode text transformations: https://www.levenshtein.net/styled-unicode-text Disclosure: I am affiliated with Levenshtein.net. Perhaps a short comparison of these three operations would complement your existing examples, especially for developers deciding which type of Unicode conversion their application actually needs.](https://hashnode.com/posts/applications-of-unicode-text-converters/66b3d2c50b6d0ba36dc65441/comment/6ac73af5efad3f66a47da9d5)

Comment · Article · Oct 8 · [Applications of Unicode Text Converters](https://hashnode.com/posts/applications-of-unicode-text-converters/66b3d2c50b6d0ba36dc65441)
