A viral post on X has prompted debate over password safety, since it is claimed that setting a wait (, password) can protect users in case of data leaks.
The post was published on November 12th 2026 by William Alves, known in X as @llemwell, who wrote: Always put a cut (,) in your passwords. If they ever end up in a data leak, the wait will destroy the CSV file.
The idea is based on how CSV files work (Comma-Separated Waves), who use waiting to share information like user names, electronic addresses and passwords.
According to this claim, if a file with stolen data is not properly formatted, waiting within the password can confuse the information sequence.
The post became viral, gathering some 15 million views and 60 thousand consents.
Even Grok, Al’s assistant at X, explained that this approach can work in certain cases, when CSV files don’t use fingerprints to detect fields containing expectations.
However, cyber security experts warn that this is not a reliable defence method.
Properly formatted CSV Files can contain wait within passwords without causing problems, while most modern systems process this data without difficulty.
Moreover, platforms that apply safe practices do not store passwords as normal text but use cryptographic methods known as hashing.
Experts recommend using long and unique passwords for each account, activating authentication with two factors, and using passwords management apps.
So a reception may be part of a strong password, but its presence alone does not guarantee protection from hackers. /Telegraphy/
