hachyderm.io is one of the many independent Mastodon servers you can use to participate in the fediverse.
Hachyderm is a safe space, LGBTQIA+ and BLM, primarily comprised of tech industry professionals world wide. Note that many non-user account types have restrictions - please see our About page.

Administered by:

Server stats:

10K
active users

Lex Friedman

Super excited for the return of this bug.

@lexfri is LeL the super hero or super villain alter ego in this story?

@lexfri I know this won’t make this any more pleasant to deal with but I might have a reason why this is happening. There is a popular cycling event that rides from London to Edinburgh and then back to London. It is commonly abbreviated LEL. It is quite popular so they have a lottery to get in. The lottery was just recently held and participants notified. You might be dealing with all the machine learning stuff seeing the use of this abbreviation. londonedinburghlondon.com

londonedinburghlondon.comLondon Edinburgh London 2025Britain's greatest cycle challenge. Ride from London to Edinburgh and back in five days. 3-8 August 2025

@lexfri That's odd.

I think normally when auto-correct fixes something, it leaves a little line for a bit (blue or red). In your case, it doesn't do that -- it almost looks like a text substitution has been added?

Can you double check in Settings > Keyboard > Text Replacements (you have to click the button…) there's not something set up there?

Barring that, you could add “Lex" replace with “Lex" to override this. I mean it'd be a band-aid, but at least it would let you type your name, LeL.

@wklj

When it first happened, someone suggested the macOS Lex/Lex text replacement. I added it. It didn't work. I restarted and the bug went away.

aText imports those System replacements too. I think the system and aText compete to replace Lex with Lex, and it collides only in Mimestream, not other apps?

Removing the aText version of Lex/Lex seems to fix it.
But that doesn't explain how it started the first time.

@lexfri When did it happen the first time? The text replacement in pre iOS 17/macOS Sonoma "had its challenges.” The new one seems better, so hopefully the old workarounds aren't needed. As far as various text replacement services competing with each other -- it sounds like an "automation Thanksgiving dinner" from hell amirite?

@wklj It was DEFINITELY pre-Sonoma. I'll see if it's all behind me now!

@lexfri Looks like a bastard relative of this bug that’s screwed with me in Notes.app for the last six months or so. (To be clear, I typed that sentence without a typo.)