Numeronyms are fun, but they have one major problem: namespace collision.

What is a11y? Is it accessibility? Associatively? Axiomatically? Autobiography?

This is obviously a problem that needs solving.

My solution? SHAsum hashing.

We can avoid the ambiguity of "a11y" with this unique, cryptographically sound alternative:

Accessibility? a884a5f3609f2cca635fed56d4ec5795da56fb970y

Axiomatically? a20c4bcee8f977a3f5a3b6b499d52d7dd32584771y

Simple, easy to visually distinguish, everyone wins.

I was actually racking my brain for 'starts with a, ends in y, same length' words to make this dumb joke but then I remembered that /usr/share/dict has _huge_ flat-file lists of words of many languages in it, so I could just get them from that?

Ninety seconds of grep, awk and sort later, there it is. For future reference there's 223 of them, alphabetically going from abdominoscopy to axiomatically.

Y'all these computers have so much in them already. _So much_. But nobody knows.

You know what an accessibility problem really looks like? It looks like thousands of people standing up web services and slapping ads on them that do exactly nothing that you couldn't do 1000x faster without ever leaving your machine, because nobody knows how to make their machines do those things.

I joke but a note about language usage and open source _cultural_ accessibility: Numeronyms are bad.

There's no meaningful distinction between "a884a5f3609f2cca635fed56d4ec5795da56fb970y" and "a11y".

Neither is recognizable as "accessibility" to anyone new to the field - great work nerds, we've managed to give the word "accessibility" its very own accessibility problem - and I gotta tell you, "not typing out long words because they're long words" seems childish as hell to most people.

Anyway, we took _the word "accessibility"_ and made it incomprehensible to new community members, look like a different, real but unrelated word if you use the wrong font or have weak eyesight, and screw over anyone using a screen reader.

We've made it harder for people who rely on accessible tech to so much as participate in conversations about them and the tech they rely on, to save able-bodied people a few keystrokes.

This is bullshit. There's no better term for it. It's just lazy bullshit.

@mhoye trendiness above all serves no one
@kboyd I should thank you for the "hashonym" term though, it's good.

@mhoye @kboyd Don't you mean h6m?

/joke

@november @mhoye @kboyd d2t y1u m2n h6m?

There, fixed it for you. Or maybe T3e, f3d i0t f1r y1u. 🙃

@mhoye it also won't show up in search results for "accessibility" (think ctrl+f not Google)
@mhoye Some of us are typing-challenged but accessibility only considers the visually impaired.
@mhoye @mwl
On behalf of my screen-reader-dependent wife, a wholehearted 💯
@mhoye this feels like the same thing that results in 3 letter variable names as though we are working on punchcards still
@petrillic It's not from as far back as punch cards, but it does date to Bell Labs. Kernighan wrote about how the Unix tradition of shortened names comes from the keyboards of the terminals at Bell Labs being so terrible that they'd start hurting to type on very quickly.
@petrillic null terminated strings, though, those date all the way to punchcards.
@mhoye I remember how unpleasant the model 33 were to type on. Whew.

@petrillic @mhoye I still see that in code from science/university backgrounds. Which is fine if your fellow scientists or faculty are the only ones who will ever read that code (and only in the next month or so before one forgets what variables g3_old, ph230nn37, and v_u stand for).

I can only imagine their work would be made much easier with more descriptive variables (and comments lol).

But there is probably historical/practical reasons why some communities will not use more verbose naming.

@petrillic @mhoye To be clear, I'm not talking about using the short forms of well-known math/physics/chem constants or names. [Although I'd still recommend spelling those out in the comments to quickly orient anyone new to the code or not especially familiar with the domain.]

What I'm talking about is super short names for variables, functions, classes, etc.

@petrillic @mhoye It *has* to make their work more challenging when going back to code after some time or trying to collaborate with fellow scientists and academics. (Right? 🤔)

Would love to read/hear perspectives from folks that have been in these communities and transitioned to/from the wider tech world.

#Programming #Science #Academics #Coding

@mhoye

I feel it's perfectly adequate to just take the first two characters of the hash. After all, there could never be a problem with "a88y", right?

You could even start an advice column entitled "Dear A88y"…

@tsukkitsune we doing cutesy-fash jokes in here? Fuck that.
@mhoye @tsukkitsune I can't see inside their head but I don't think that's what's going on here. The hash you provided did in fact start with 88, 8 is in fact l33t-speak for "B", and I'd wager the vast majority of people, probably even tsukkitsune themself, don't know that "88" is a neo-Nazi dogwhistle. I think it was a harmless joke that accidentally wound up adjacent to a fascist meme.

@cholling @mhoye

Having set out to riff a little on what I took to be the original intent of the post, a jocular suggestion to "cause less confusion" which would instead cause more confusion, I guess I can't complain that OP was in fact confused.

(For the record, my opinion is that the use of "88" by neo-Nazis is one of the more minor reasons to despise them, but it's on the list. I've seen it happen that someone was attacked on-line for having that in their username when it was, as people still sometimes do, their birth year, and I'm sure that kind of dissension is at least part of the intent behind it.)

@tsukkitsune @mhoye i think this was a joke about the name “Abby”

@mhoye I hate Three Letter Acronyms ("TLA") for similar reasons.

They are...

+ elitist
+ exclusionary
+ domain specific
+ place an onus on the listener/reader to decipher

We have rich expressive languages that should be used to their full extent.

@slackline @mhoye indeed. And digital letters are free. There is no need to save some pixels.
@slackline @mhoye I take it you're not a fan of CBT.

@barubary @mhoye

Core Body Temperature
Computer Based Training
Complete Binary Tree
Chicago Board of Trade
Carotid Body Tumors
Cognitive Behavioural Therapy

???

🥴

@slackline @mhoye

Cross-Browser Testing

But no, it's Cock and Ball Torture, of course.

@slackline @mhoye Came here to say exctly this.

But I'll add: If I don't take care to who I am and where I'm from search engines will give me your acronyms most common usage in my language.

And skew that heavily towards business interests, because search engines.
@mhoye i would extend this to acronyms in general. everyone just gave up on actually naming their software or protocols and now smash a bunch of random words together so they make a nice acronym. it makes trying to find out what the fuck tech people are talking about so much harder
@mhoye i phrased it like it's a new phenomenon but actually this was always a problem in tech "www" "ftp" "ssh" all of these are purposefully named something long and uncatchy to be acronymized
@mhoye @doofus_canadensis It’s like people took the shortcuts we used when T9 was the only mobile input method and tried to make them grown up to look “cool”

@mhoye It's worth noting that the earliest examples most people encountered were used for words that were self-referential problems: "i18n" (spelled as "internationalisation" where I am but not everywhere) et al

That made a certain kind of twisty sense for people who had to work with them. The same absolutely did not apply to "a11y" because if "accessibility" is your problem something's making plain text one.

@mhoye it took me forever to figure out what i18n meant.. in the end I had to Google it.
@Euph0r14 @mhoye
It's obviously institutionalization, which is what should be done with whoever came up with the abbreviation i18n.

@mhoye

I blame the use of i18n for "internationalization".

I think it was back in the mid 90s.

When everyone was scrambling to translate user interfaces to non-English languages.

I understand being lazy, and not wanting to type a bit of jargon over and over again, but then the "short cut" becomes the jargon, and opaque to new folks to the field.

Language changes, but I have to agree that "accessibility" going to "a11y" is an ironically bad choice.

@mhoye FWIW, I've seen the word a11y on social media for years and recognized that it was about accessibility but thought that it meant ally in leetspeak and was therefore really about telling able-bodied people how to be better allies to the disabled.

UPDATE: now looking at the other @-replies it looks like I'm not at all the only one.

@Alon Not by a long way, no.

@Alon @mhoye In an accessibility newsletter I follow... Plenty of publications they link to use it this way!

Looks like "ally" but isn't, I but that's familiar to plenty of people...

@mhoye > "not typing out long words because they're long words" seems childish as hell to most people.
It also shows they don't use a proper text editor.

Both vim and Emacs could trivally complete it once it's been typed at least once in the document.

@mhoye @Kiwicoder

We say HTML not HyperText Markup Language

And html has a fix of this too become searchable too: wrap <abbr> around all a11y and i10n done ✔️

@mhoye when I was a kid I loved a genre of books that was basically “here’s weird stuff you can do with household objects and chemicals, science is fun!” They weren’t focused on teaching chemistry or electricity beyond the absolute basics, but more about cultivating a sense of excitement and wonder.

I want that but for Linux.

@mhoye I saw someone excited about a GitHub Copilot feature that would "tell you which commits have previously changed a file".

Finally, through the world-changing power of AI, we have replicated `git log`

@scubbo @mhoye oh wow, thanks ai, can’t believe it took them this long to implement git blame
@mhoye like, seriously. Folks telling me to use online services like ClipChamp to edit or downscale videos. They don’t even know ffmpeg exists! It’s so absurd to me!
@nitinkhanna @mhoye Honestly, even if you know it exists... the command line flags exposing /nothing/ but accessibility problems of their own.

So many opaque abbreviations.
@lispi314 @mhoye @nitinkhanna and the documentation is no less confusing

@xarvos @mhoye @lispi314

Don’t hate me for it, but I’ve taken to asking LLMs to create ffmpeg commands for common things I want to do. They do a good enough job for most things. For more complex stuff, they give a good starting point.

Agree that it’s not the most user friendly tool.

@nitinkhanna @mhoye @xarvos I'd argue that when you start having to lookup search engines or LLMs for remote help to determine how to use a program, it has already thoroughly failed at self-documentation and usability.
@lispi314 @mhoye @xarvos yeah… I agree. Though, with something as esoteric as video manipulation and something as powerful as ffmpeg, it would be extremely difficult to get the documentation right. That said, if they could explain their damn filter options better, that would be worthy of a Nobel Peace Prize.
@mhoye SHAsums are a tad impractical, you could map the hash to a series of words instead. For instance Accessibility/a884a5f3609f2cca635fed56d4ec5795da56fb970y could be "very good carrot"

@mhoye I have two remote jobs, both of which use VSCode as standard editor for everything.

The amount of coworkers at BOTH jobs–one at a Fortune 500, one at a scrappy codeschool–who routinely copy paste JSON and navigate to jsonformatter dot whatever in their browser, instead of just pressing Shift + Alt + F... it makes my head spin.

It's like wanting to take a bath, leaving the bathroom, and dragging a garden hose inside to fill the tub. 😵‍💫

@mhoye Good points. I happened down this road a few years ago.

Sometimes I think we should have some voluntary "fully-stocked Linux distro + open data + isolated island w/ no Internet + see what you can create" teams out there for science.

Also I ended up really appreciating resources like this: https://github.com/first20hours/google-10000-english/tree/master

GitHub - first20hours/google-10000-english: This repo contains a list of the 10,000 most common English words in order of frequency, as determined by n-gram frequency analysis of the Google's Trillion Word Corpus.

This repo contains a list of the 10,000 most common English words in order of frequency, as determined by n-gram frequency analysis of the Google's Trillion Word Corpus. - first20hours/google-1...

GitHub

@mhoye so... it's a silly thing to ask.. but surely just typing the word is better than typing a hashtag that is 3 times the length of the word?

Or is that the joke?

@mhoye hashonyms. such a timesaver. and what a boon to clarity.
@kboyd
SHA1 is considered a bad idea, those should be SHA256, or for absolute certainty SHA512
@mhoye
@viq @kboyd @mhoye True! You never know when an adversary might invent a pair of English words with colliding SHA-1 digests and get them adopted into the standard lexicon just so they can do a rug-pull on you 20 years later.
@varx @viq @kboyd We need to start working on quantum-resistant hashonyms immediately.