The author went through the trouble of figuring out the protocol but never bothered to just run dict. Okay.
The author went through the trouble of figuring out the protocol but never bothered to just run dict. Okay.
Here's a hint:
macbook% dict
zsh: command not found: dict
desktop$ dict
bash: dict: command not found
You'd have to be pretty into retro-computing before you'll find an OS that ships /usr/bin/dict . $ dict
Command 'dict' not found, but can be installed with:
sudo apt install dict
After installing, $ dict example
6 definitions found
...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:// 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.
DICT(1) DICT(1)
NAME
dict - DICT Protocol Client
SYNOPSIS
(...)
DESCRIPTION
dict is a client for the Dictionary Server Protocol (DICT), (...)
but, yeah, not everybody has that backgroundwhich is fine! nobody is born knowing all the unix commands
finger, ftp, ssh, talk, telnet, tftp, maybe whois too?
It’s entirely possible they were already aware of other software that supports dictionary lookups.
I for one had never heard of the dict:// protocol, so I was curious about it.