sudoshakes
If you were alive in 1960s America, you would have seen no seat belts, significantly lower life expectancy, children still dying to smallpox and polio, and if you are ethnically from the Middle East; everyone in America would have hated you. Race riots were a massive thing in the 60s, police brutality was rampant against people of color. Even the FBI was trying to suppress race progress.
You have presidents for decades trying to create racist drug politics to entrap only non-white non-affluent people into cyclical prison systems.
You have so much hidden then, that happens today, but it was both hidden and far far greater.
The ideal doesn’t exist at all and more so for someone like yourself.
It’s an F-18 super hornet.
Fucking degenerate.
Notice how I didn’t just use the service name?
<Disco>
<Netfucks>
<MailGoog>
Whatever nickname you use for your services. There is no requirement you also use the service name in the tagging template.
The idea that a breach of a service would have someone looking at your individual password is also pretty silly. There would be variations and pattern matching Lagos run against lists of hundreds of thousands to millions of passwords… but the decryption of a complete password to plain text is so reductions at this point, we are talking about the 0.01% case of a then even more silly “let’s look at this guys password in particular” 0.0001% case on top of it…
It’s not a real problem because if your service is at the point it is leaking not just salted and hashed passwords, but plain text passwords: you are in a big problem up no matter what for most users. Almost everyone reuses passwords. The real risk is the simple reuse. Get just a slightly different variation and you are miles more secure in the case of a breach that results in full decryption.
The majority still reuse Password1234! Everywhere. This gives you a easier way to be miles better.
Better still of course is some sort of managed password vault, assuming you trust their implementation. However, this costs zero in the training, or tech literacy upskilling that even the moderate change to a password vault requires. It’s simply an extension of what people already intuitively know. Thus, barrier to entry is easier while giving you several orders more protection.
Merica means freedom to do dumb things. Lemme fly!
https://dev-to-uploads.s3.amazonaws.com/i/it0fk0jbqphcgecnpbq7.jpg
You can take this a step further to segregate passwords as well.
Reusing passwords across devices is bad. If one gets compromised you don’t want a password being out into a brute force table to be used with all your other accounts elsewhere.
This method of tagging using HTML markup styles in your passwords lets you keep the same core passphrase but alter the tagging, specific to the service.
You can do this easily while also giving you artificial password complexity.
Example:
Core passpgrase is “yogurt”
Password for gmail becomes markup with a <mailPassGoog>yogurt</mailPassGoog>
I only need to remember yogurt.
Every device just gets a truncated service tag appended to the beginning and end using HTML style tags.
Suddenly you have a 26+ character password that you don’t forget and doesn’t compromise you across other services because each is different.
Most modern cancer drug treatment is sequenced to at least the specific proteins of the type of cancer it is.
Have breast cancer? Cool. We figure out which of the many variations so that we can give you medications for that exact type of breast cancer.
This sort of specific targeting has been increasing and increasing for the last 20 years. MRNA is the next step of that and is highly likely to be a means or become or for treatments in many other areas.