The discussion revolves around automatic link creation for non-TLDs in Discourse. Patrick_David inquires about the list of allowed TLDs for auto-linkification, noting that file extensions like .md are also turned into links. mpalmer suggests that whitelisting actual TLDs is impractical due to the vast number of TLDs and recommends wrapping filenames in backticks to prevent auto-linkification.
The thread was initially mislabeled as a bug report and was moved to Support by sam. sam later points out that the markdown linkify tlds setting in site settings provides control over auto-linkification, allowing for more precise detection.
Is there a list for allowed TLD’s to auto-linkify? That is, if I use a file with an extension like markdown, it gets turned into a link also: README.md (<- that is just typing a filename + extension, not an actual link I’ve created.
Given ICANN’s predilection for stuffing the entire dictionary into the TLD space, it’s probably a losing proposition to try and whitelist actual TLDs (as an amusing note, .md is a valid ccTLD, for Moldova, so even if we did have a list of “valid” TLDs, README.md is a perfectly valid domain name, and does, in fact, exist – and resolve).
For filenames, specifically, I suggest wrapping them in backticks, which maintains the long-standing convention of monospace fonts for that sort of thing, and which prevents auto-linkification, a la README.md. Trying to educate people to mark up their links in some specific way, such as wrapping them in angle brackets, or having to include the scheme, or including a forward slash, I think are all doomed to sadness.
Al momento il rilevamento automatico non è perfetto: esistono molti TLD poco comuni, ma con l’impostazione markdown linkify tlds nelle impostazioni del sito hai il controllo totale!