News for hackers. Stuff that matters.
Re:The UX of UUIDs by Terr_ on Thursday April 11, 2024 @02:04PM (#40005020)
> One way to enhance the usability of unique identifiers is by making them easily copyable. This can be achieved by removing the hyphens from the UUIDs,

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.)

Re:The UX of UUIDs by ssl-3 on Thursday April 11, 2024 @02:15PM (#40005112)
Is there an unambiguous, accepted, monosyllabic way to verbally speak the _ character?
Re:The UX of UUIDs by Terr_ on Thursday April 11, 2024 @02:31PM (#40005283)
Alas, no... however you might not need a sound if you can use tonal inflections and pauses to express the boundary instead. Particularly when chunks are short and when the receiver (or the software they're typing into) knows the format already... Although with a tech-illiterate relative you'll have bigger problems, like explaining what an underscore even looks like and where it is on their keyboard.

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 .

Re:The UX of UUIDs by jareklupinski on Thursday April 11, 2024 @03:10PM (#40005691)
yes, but to confirm I'd repeat it back to them as "was that ten dot seventy dot one-twenty-two dot five?"

having a clear seperator helps me say the numbers faster

Re:The UX of UUIDs by inopinatus on Thursday April 11, 2024 @09:05PM (#40008469)
or you could say 172390917
Re:The UX of UUIDs by stephenr on Friday April 12, 2024 @08:45PM (#40019256)
I've worked in IT (support, network mgmt and development roles) for 20 years, with colleagues, customers and clients from dozens of countries.

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.

Re:The UX of UUIDs by ssl-3 on Monday April 15, 2024 @11:38AM (#40042005)
Generally, yeah.

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.)

Re:The UX of UUIDs by mcherm on Thursday April 11, 2024 @02:16PM (#40005125)
No.

There also isn't one for "w", yet we get by with that as a letter.

Re:The UX of UUIDs by lelanthran on Thursday April 11, 2024 @06:05PM (#40007312)
> 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 :-)

Re:The UX of UUIDs by __float on Thursday April 11, 2024 @06:24PM (#40007443)
Unless it's at the beginning of a word, like xylophone?
Re:The UX of UUIDs by ssl-3 on Thursday April 11, 2024 @06:58PM (#40007698)
The only rule in English is that there is an exception to every rule (including this one).
Re:The UX of UUIDs by lelanthran on Friday April 12, 2024 @01:52AM (#40009745)
> Unless it's at the beginning of a word, like xylophone?

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.

Re:The UX of UUIDs by Aloisius on Thursday April 11, 2024 @11:04PM (#40009014)
> There also isn't one for "w"

There's dub.

Dub-dub-dub is pretty widely understood to mean www.

Re:The UX of UUIDs by revlolz on Thursday April 11, 2024 @02:24PM (#40005215)
If "underscore" gets tedious I just say "tac"

But I get that it's confusing with dashes.

Re:The UX of UUIDs by djbusby on Thursday April 11, 2024 @04:26PM (#40006468)
Unicode call it a lowline. PostScript calls it underscore and HTML says UnderBar.
Re:The UX of UUIDs by floating-io on Thursday April 11, 2024 @05:15PM (#40006898)
I feel like "slab" would work.
Re:The UX of UUIDs by v-yadli on Thursday April 11, 2024 @06:05PM (#40007314)
nono, was it slab or slash [over a 8k bandwidth phone call]?
Re:The UX of UUIDs by ubitaco on Thursday April 11, 2024 @06:14PM (#40007368)
I would back "blank" as the most likely to be understood by the other person.
Re:The UX of UUIDs by bmicraft on Friday April 12, 2024 @01:50AM (#40009738)
I'd understand that as space, but then I'm not a native speaker
Re:The UX of UUIDs by mh0pe on Thursday April 11, 2024 @11:12PM (#40009059)
Screenreaders pronounce it "line".
Re:The UX of UUIDs by adontz on Friday April 12, 2024 @02:22AM (#40009904)
It's a mess. In Georgian we say "lower dash". No short name in any language I know.
Re:The UX of UUIDs by dheera on Thursday April 11, 2024 @04:51PM (#40006684)
Or at LEAST make the dashes evenly spaced.

0000-0000-0000-0000-0000-0000-0000-0000

Re:The UX of UUIDs by accrual on Thursday April 11, 2024 @07:27PM (#40007902)
BitLocker does this and it's nice UX for walking someone through a recovery key over the phone.

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.

Re:The UX of UUIDs by dheera on Thursday April 11, 2024 @11:14PM (#40009075)
> hashes each set of 6 digits

nice, now i can dictionary attack any key, 6 digits at a time

Re:The UX of UUIDs by Mavvie on Friday April 12, 2024 @12:46AM (#40009469)
I don't think that's how it works... It's a checksum, not letting you check if each section is part of the key.

At worst, the key would have some portion less entropy since there's a lot of bits used for checksums.

Re:The UX of UUIDs by Terr_ on Thursday April 11, 2024 @05:02PM (#40006772)
I don't think we're talking about the same problem here.

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.

Re:The UX of UUIDs by dheera on Friday April 12, 2024 @12:26PM (#40014688)
use the character 'v' to separate sections? That would solve that problem, and it isn't a hex character

0000v0000v0000v0000v0000v0000v0000v0000

Re:The UX of UUIDs by initplus on Thursday April 11, 2024 @07:26PM (#40007894)
Speaking of which, why are we stuck with this terrible "trailing space selected" behaviour? It's not the case on all platforms, macos/ios perform fine and only select the actual word but Windows still includes the trailing space. There are posts online complaining about this going back 15 years at this point, it's super low hanging UX fruit.
Re:The UX of UUIDs by brokenmachine on Thursday April 11, 2024 @08:35PM (#40008253)
Probably they tried to fix it in Windows, but it caused all your files to be deleted or something.

Like the coconut in TF2.

Re:The UX of UUIDs by mixmastamyk on Friday April 12, 2024 @11:27AM (#40014015)
When you hit the delete key once, the word and extra space are gone, nothing more to do.
Re:The UX of UUIDs by inopinatus on Thursday April 11, 2024 @08:51PM (#40008374)
> double-clicking on this 123_456_789 will select all 9 important numbers

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

Re:The UX of UUIDs by hot_gril on Thursday April 11, 2024 @09:15PM (#40008532)
Text selection on iPhones has been unusable since iPhone OS 1. It's the one thing that's actually easier on Android.
Re:The UX of UUIDs by eviks on Friday April 12, 2024 @04:28AM (#40010493)
Get a better baby for the rare cases, no need to always suffer