I think you are both greatly overestimating the number of people who remember what xkcd is and their willingness to do what a webcomic prescribes uncritically. What you describe as "bespoke" is likely the normal way someone might use it: with their chosen format.

For instance, I have multiple separator characters, multiple beginning and end characters, and numbers places at specific places, and arbitrary casing. That may be overkill but it's still essentially the xkcd format.

▲

applfanboysbgon 42 minutes ago | parent [-]

> I think you are both greatly overestimating the number of people who remember what xkcd is and their willingness to do what a webcomic prescribes uncritically

XKCD's youtube videos get millions of views each. It is a very popular comic, and that particular password advice has spread beyond it.

> What you describe as "bespoke" is likely the normal way someone might use it.

And yet the issue in question is about someone who refuses to adapt it.

▲

strbean 28 minutes ago | parent | next [-]

The user in question might have their own personal format that doesn't meet the RustDesk constraints. E.g. they may not use capitals, but use `word1$word2&word3@word4`.

Tayloring your format to the requirements of each site is a step towards defeating the utility of the system; now the user needs to remember some arbitrary hard-to-remember details for each password.

Although having a standard format for your passphrases across sites removes some of the advantages over just using the exact xkdc format (when one of your passwords is compromised and attackers can guess your custom format elsewhere now)...

	▲	throwaway27448 6 minutes ago \| parent [-]
		This is a non-issue with a password manager

▲

throwaway27448 6 minutes ago | parent | prev [-]

> And yet the issue in question is about someone who refuses to adapt it.

Does this person exist?