characters

So, the argument is because the hash is displayed it can be reversed by subsequently hashing every known combination of characters with every known mail provider?

You do realize that the limited characters is perhaps the single most important feature in its success so far?

So both always were somewhat of a problem, except combining characters are obviously more important and hence more justified.

But with your real name and with some added characters at the end of your twitter-handle, because the algorithm says so.

Does Unicode only accept characters which are in an already standardized or widespread character set?

There's no complexity to combining characters Show me one fully compliant and correct implementation.

And it's 5 characters to prevent a whole class of errors for free (erroneous assignments to method parameters), so why not do it?

You can already tweet photos, videos, but not more than 140 characters?

All this bullshit, and we still can't have separate Chinese and Japanese characters that were Han-unificated.

As you say, if this brings the risk of splitting combining characters to the fore maybe more software will handle it in the future.

There have been known bugs and vulnerabilities caused by combined characters.

I thought that fmt only separated text by columns not by characters or words?

From observing friends, less and less are interested in reading beyond "140 characters" or whatever is considered byte size.

Twitter needs multi-level threaded discussions and "sub-tweets" that are more than 140 characters.

In case it isn't clear, "people like me" and "people like you" refer to the hypothetical characters in the above paragraphs.