A stray "j" ruined my evening

One tiny typo turned shared links into a mini social disaster, and the comments had a field day

TLDR: A developer discovered that one invisible extra character was quietly breaking every link he shared, turning a simple shortcut into a social embarrassment. Commenters loved the irony of the fix, argued over whether the chat app was really to blame, and swapped their own bizarre tales of random letters causing chaos.

A developer thought he was just living the dream: click a script, shorten a link, paste it into chat, move on with life. Instead, he accidentally launched a one-letter reign of chaos when every shared link picked up a mysterious extra "j" at the end, sending friends straight to 404 error pages. The reveal was painfully simple: an invisible line break was being copied too, and in his chat setup it showed up as a literal j. Cue what he himself called five solid minutes of immense shame.

But the real entertainment was in the comment section, where readers treated this like a tiny tech whodunit. One of the biggest crowd-pleasers was the instant dad-joke victory lap: "I like how -j fixed the stray j problem...." Yes, the fix for the rogue j was literally an option called -j, and commenters were absolutely not going to let that comedy gold slide. Others were less amused and more suspicious, with one person basically going, wait, why on earth does a line break become a j? That confusion quickly turned into the thread's mini-drama, with people wondering whether the real villain was the author's script or the chat app mangling pasted text.

Then came the nostalgia brigade. One commenter shared an old horror story about support tickets ending in a random J, only to discover it was actually a smiley face hiding in a weird old font. Suddenly, this wasn't just one developer's embarrassing evening — it was a full-on support group for everyone who's ever been betrayed by a single cursed character.

Key Points

  • The article centers on a personal shell script used to shorten links and copy the resulting URL to the clipboard.
  • The problem appeared after the author began using the terminal-based Signal client gurk to share links.
  • Recipients reported 404 errors, and the author later found the sent URLs consistently ended with an extra `j`.
  • The root cause was a trailing newline emitted by `jq` when extracting `.short_url`, which was rendered as `j` in the terminal context described.
  • The issue was resolved by switching to `jq --join-output` (`-j`), which omits the trailing newline.

Hottest takes

"I like how -j fixed the stray j problem...." — benj111
"So this is a bug in that Signal TUI he was using?" — meindnoch
"tickets would often end with a single \"J\"" — Cyykratahk
Made with <3 by @siedrix and @shesho from CDMX. Powered by Forge&Hive.