[ancientsofmumu]

Why doesn't the author tell people to just got to https://dict.org in a browser, which is the default backend for the apps? SSL, POST queries, minimal and fast web output. Only javascript on the site is an old useless widget from a decade ago that bounced you to the internet strike of 2012. Works well even in elinks / links in a terminal if that's your thing, could probably whip up a cURL alias in minutes.

[everybodyknows]

A few minutes in Firefox' Network logger reveals that https://dict.org does not expose the search term in the URL, unlike all of:

  https://ahdictionary.com
  https://www.collinsdictionary.com
  https://www.merriam-webster.com
  https://en.wiktionary.org

Furthermore, the last three, excepting ahdictionary.com, issue HTTPS requests per-keystroke -- needed for auto-complete.

Note however one tripping hazard with dict.org: Unencrypted port 80 i.e. "http://dict.org" is functional, does not redirect to "https://dict.org", and Firefox responds to a bare "dict.org" in its search box by first trying "http://dict.org". FF presents the dict.org home page upon getting the port 80 success response.

[bawolff]

Why do we care about exposing search term in url on an HTTPS connection?

Regardless, wiktionary supports POST for search, its just not the default.