Welcome to Cordnewyork
Cordnewyork is the home page of CORD New York, a community organization based in New York. The site also collects short articles and updates spanning technology, lifestyle, and travel. Use the menu on the left to jump to specific sections, or scroll down for the latest posts.
Within these pages you will find notes on CORD NYC's past events, profiles of the Leadership Advisory Board, and a growing archive of newsroom-style features published under the Cordnewyork byline.
Five Things You'll Find Here
- WordPress-powered news and notes from the CORD NYC desk.
- An events archive covering community activities in and around New York.
- Profiles of the Leadership Advisory Board members who guide the organization.
- Reports on the impact of community projects, including food drives and walkathons.
- Reader-friendly technology and travel write-ups, refreshed on a rolling basis.
Why Siri fumbles commands that include VPN in a shortcut name
Every Australian iPhone user with a work VPN has hit the same wall. You build a shortcut called "Connect VPN", say "Hey Siri, connect VPN", and the phone either searches the web for cheap flights to Europe or announces that it cannot find a matching shortcut. The failure is not random, and it is not simply your accent. It sits in the gap between how speech recognition turns sounds into characters and how the Shortcuts app compares those characters against a name you typed in capitals.
The underlying story is bigger than one abbreviation. The same behaviour shows up in everyday language, in device and network integration, and in the habits people form when talking to assistants. Understanding why Siri trips over strings like VPN, NBN or FIFO means looking at natural language processing, hardware behaviour, connectivity, and the way we phrase requests out loud — and at what has to change before the assistant becomes genuinely dependable.
When a shortcut name turns into a recognition test
Siri handles a request through a chain: wake-word detection, speech-to-text, intent resolution, and finally a lookup in the shortcut registry. That last step is close to literal. The transcript produced from your audio is matched against names, aliases and trigger phrases stored on the handset, and the comparison is far less forgiving than a human listener.
If your shortcut is titled "VPN" and the recogniser returns "v p n" or "vee pee en", there is no clean match, and the request slides into a generic web search instead. If you named it "Connect VPN", the recogniser may split the utterance into "connect" plus a stray token and lose the second half entirely. Either way the shortcut exists, it is visible in the Shortcuts app, and it still cannot be invoked by voice. Writers documenting these quirks, including the team behind Cord New York, have logged plenty of cases where the assistant understood every word correctly and still could not run the obvious thing.
Why acronyms break the language pipeline
Speech recognition relies on a language model to guess the most plausible characters for a stretch of audio. That model is trained mostly on written prose and ordinary conversation, where "VPN" appears far less often than "virtual private network" or "connect". Letter strings with no vowels are unusual in speech, so the recogniser has to guess, and its guesses drift.
Australian workplace vocabulary makes the guessing harder. Your provider might be "NBN" or "nbn", an employer might be "ATO" or "CBA", and a FIFO roster becomes "f i f o" the moment somebody says it aloud. Even Melbourne's airport code "MEL" suffers the same fate in dictation, because the model expects "mel" to be a word, an email address or a person's name.
Capitalisation compounds it. Shortcut names are stored with the exact characters you typed, and the matching step is often case-sensitive, so a transcript of "vpn" fails against a registry entry of "VPN" even when the phonetics were flawless.
Australian voices and borrowed pronunciations
Australian English has its own rhythm, and the assistant was not built with it in mind. The letter V tends to come out as "vee", N as "en", so "VPN" is said "vee pee en" rather than the clipped "v-p-n" many people assume they are using. The diphthong in "connect" can flatten into something closer to "conn-ect", and the final consonant of words like "stash" or "fetch" is often dropped in casual speech.
Accent is a proven factor rather than a myth. A Southern US accent study found that a strong regional accent reduced recognition accuracy for short, near-homophone words such as pin and pen, which is exactly the same class of problem as VPN beside a spelled-out phrase. People who code-switch between Australian and workplace jargon get hit hardest, because the recogniser switches language models mid-sentence and loses confidence right at the acronym.
Connectivity, accessories and hardware quirks
Recognition is only half the job. The audio has to reach the phone cleanly, the phone has to be online, and the assistant has to be permitted to wake. Australian conditions make all three unreliable in specific ways. A Bluetooth headset on a Sydney ferry competes with engine noise, wind and announcements; a case that muffles the microphone or earbuds with a worn seal will quietly swallow the final consonant of your shortcut name.
Connectivity adds a layer of its own. On a fixed NBN connection requests travel quickly, but on a mobile network in regional Victoria, or while driving the Pacific Highway towards Coffs Harbour, congestion can cause the shortcut lookup to time out after the words were already recognised perfectly. Telstra, Optus and Vodafone coverage maps all show the same black spots, and people in regional towns increasingly lean on satellite services, which helps yet never matches good fibre.
Device-side states can block the wake phrase altogether. The technical reason Siri's water lock mode affects wake detection is worth reading for anyone who has owned a phone that went for a swim, because the acoustic thresholds change and the assistant goes deaf to "Hey Siri" before any language model sees your words. The same publication has also covered Diggline's technology feed style coverage of cases where the microphone, not the software, is at fault.
Workarounds and diagnostic checks worth trying
Two short lists cover most of the cases Australian users report, and both are worth working through before concluding the assistant is broken.
Short-term fixes for acronym names
- Rename the shortcut with spelled-out words, such as "Connect my private network", so the transcript and the stored name overlap.
- Add a spoken alias in the shortcut's details, since the trigger phrase can be set independently of the display name.
- Include a plain-language fallback step inside the shortcut, such as a single action that opens the VPN app directly.
- Retrain the assistant by saying "Hey Siri, restart" after making changes, which refreshes the on-device voice profile.
- Update iOS and the Shortcuts app, because dictionary and alias handling has improved in recent releases.
Checks to run before blaming the assistant
- Confirm the device is online on a stable connection, not a congested mobile network in a known black spot.
- Test the microphone in a quiet room with the case removed, checking input levels in a voice recording app.
- Verify the wake phrase still triggers after a restart, separating hardware faults from language faults.
- Check whether a paired accessory is the actual microphone source, since Bluetooth headsets take priority on iPhone.
- Look for a low-battery power state, which restricts background listening and background shortcuts.
What a smarter assistant would need
| Shortcut naming approach | Likely Australian transcript | Outcome | Effort to fix |
|---|---|---|---|
| "Connect VPN" | connect vee pee en | Frequently missed | Rename the shortcut |
| Stored as "VPN" | v p n or vee pee en | Registry mismatch | Rename and re-record |
| Added phonetic alias | connect vee pee en | Matches the trigger phrase | One-off per shortcut |
| Triggered inside the Shortcuts app | not applicable | Always runs | Slower for daily use |
The pattern is plain: every approach that gives the recogniser a phrase it hears often, and matches it to a name stored in the same characters, succeeds, while every approach that depends on the assistant guessing an abbreviation fails. The same logic explains why "Hey Siri, turn on do not disturb" works and "Hey Siri, DND" does not.
The deeper fix belongs to Apple and to the on-device models: phoneme-aware matching for acronyms, case-insensitive registry comparison, and context that reads "VPN" as a noun attached to "connect" rather than three random letters. The accent research and hardware edge cases linked above point the same way — reliability improves when the assistant hears the phrase a human would hear and compares it the way a human would compare it.
Start with the rename today. Open the Shortcuts app, change acronym-heavy names to the words you actually say out loud, add a phonetic alias for anything you cannot spell sensibly, then test the command on the same connection you use every morning. If it still fails after that, the culprit is almost certainly the microphone, the accessory or the network rather than the phrase, and the checks above will isolate it within a few minutes.
Need a Hand Navigating?
If you are looking for something specific, the left-hand menu leads you to the main sections: About Us, Join Us, Past Events in New York, Impact of CORD, and the CORD NY Leadership page. The Donate page is the place to support the organization financially.
Ask a Question
Use the form below to send a note to the editorial team. We read every message.
What Readers Say
The events archive is the easiest way to follow what CORD NYC has been doing over the years. Clean and to the point.
— Recent visitorI appreciate having the leadership profiles alongside the community news. It keeps the people behind the work visible.
— Site readerThe technology and travel write-ups are a nice surprise on a community-focused site.
— Subscriber