Obviously I can't fully express it in text here, but try to imagine this as a coworker speaking to you: "Hey, write down this IP address. It's ten, seventy, one twentyyyyyTWO, five."
They didn't actually say "period" or even "dot", but I bet you'd type 10.70.122.5 .
having a clear seperator helps me say the numbers faster
I've never once heard anyone drop out the dots in an IP. Non technical users aren't confident enough to do anything but read it exactly as it appears (one zero dot seven zero dot...) and technical users who are generally experienced enough to know what an IP address is, know that the dots are meaningful.
If it's something like 56.7.23.231, I'm definitely going to disambiguate it by deliberately saying each one of of those three dots.
But if it's more like 192.168.0.1, I'm probably not going to bother with speaking any delimiters in conversation with another person who has at least reasonable familiarity with common IP networking layouts.
Bringing it back to the topic: UUIDs should not ever follow familiar content patterns (if they do, then that's an issue in and of itself), so I'm always going to speak the delimiters of a UUID -- whatever they consist of.
(If nothing else, doing so breaks up the pattern into human-digestible chunks -- which is probably the sole reason we have those delimiters in UUIDs to begin with.)
There also isn't one for "w", yet we get by with that as a letter.
Warning: Tangential rant ahead.
I'm teaching my toddler to read (Distar alphabet).
Even with the modified alphabet, it's a chore to "know" how to pronounce a letter.
'a' has at least 4 different pronunciations in words used by toddlers: apple, came, eat, bread.
All the vowels are like that, and even some consonants ('y' has at the very least: baby, yesterday, cycle, buy)
The only well-behaved letter in English is 'x': pronounced the same wherever you see it, as 'cks'[1].
[1] For toddlers, anyway. I doubt a 4-year old would be interested in LaTeX :-)
Well, we didn't cover sounding out of `ph` yet, and it isn't a toy he has, so thankfully it is not a word he uses.
There's dub.
Dub-dub-dub is pretty widely understood to mean www.
But I get that it's confusing with dashes.
0000-0000-0000-0000-0000-0000-0000-0000
Another VERY nice feature is it hashes each set of 6 digits as you type, so if you transpose one, you immediately get feedback instead of "invalid key!" after typing the whole thing out.
nice, now i can dictionary attack any key, 6 digits at a time
At worst, the key would have some portion less entropy since there's a lot of bits used for checksums.
Regardless of how many dashes you have or how (ir)regularly they are spaced, to select the whole ID you must carefully click-drag-release around its boundaries, you can't just double-click anywhere in it to select.
0000v0000v0000v0000v0000v0000v0000v0000
Like the coconut in TF2.
True, but alas, on iOS I found that a double-tap selected only one of the digit groups.
In my view the touch interface UX is just as significant - perhaps even more so in recent years - given that the backdrop to many of these identifier format decisions is ensuring nontechnical end-user support, under time pressure, over possibly quite unreliable channels, goes as well as it can.
But look on the bright side, at least it didn't try to call the number
No! That's throwing the baby out with the bathwater! Removing all separators means rare-but-important manual tasks of transcription or comparison become terrible, since there are no clear chunks.
Instead use a different character which doesn't have the same problem, one that most software considers part of the same "word"... such as the classic underscore.
For most people, double-clicking on this 123_456_789 will select all 9 important numbers. (And maybe a trailing space, but that's a separate problem.)