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

Hmmm. No.

You don’t partially decrypt passwords. You either get the full thing or you get gobble.

So if they get 1, they still don’t know you use <DiscordTag> or <Disco> or <DiscordSeevice> etc. I wouldn’t just straight up say “Netflix” in my service tagging.

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.

Lol. No.

9mm? 1 round? Nah.

Yes.

Just this month I was there and the pizza is a different concept there to be sure.

Street pizzas of thinly sliced zucchini or potato covering bread rounds with olive oil. That’s pizza in Rome.

Focaccia bread like crust with some anchovies and potatoe? Pizza.

Neapolitan style is just a different style again, but the theme is dough is not the delivery agent, it is the primary purpose. The dough is the important bit, with toppings being intended to enhance subtle flavors for it.

Italian pizza is most similar in American expectations of food typically found there, to flatbread dishes. It’s flatbread with some stuff on top to accent it. There is no cheese on most of the pizza I had in the various parts of Italy I was in. Cheese was not an expected component. Healthy or at least flavorful variations on additions to the dough are the goal.

Whether you are in Sardinia, Calabria, or Rome; pizza is pizza dough with local additives.

I have seen French fries on top of pizza in Sardinia, and this was called there “American pizza” :)

deleted by creator