So the causal chain would be: 1. Notice a URL scheme dict:// 2. Try to type 'dict' into a terminal, on the off chance there's a command-line tool with the sam

So the causal chain would be: 1. Notice a URL scheme dict:// 2. Try to type 'dict' into a terminal, on the off chance there's a command-line tool with the same name (would you do this for https:// https:// and expect the same outcome?) 3. Be running a distribution that modifies the user's shell environment to suggest packages related to unknown commands 4. Actually install and run that command 5. Be running tcpdump or wireshark at the same time to notice that the `dict` command is reaching out to the network, as opposed to doing some sort of local lookup in /usr/share/dict 6. Figure out from the network traffic that the tool is using a dictionary-specific protocol as opposed to just making an HTTP request to dictionary.com or whatever. -- Nah, the only way someone would know (or even suspect!) that dict:// is somehow related to an ancient Unix command-line tool is prior knowledge, and it's unreasonable to expect the article author to have somehow intuited such an idea.