The discussion revolves around moving the footnotes feature from an enterprise-only plugin to a standard, core feature in Discourse. pradyunsg highlights that footnotes are currently only available as an enterprise plugin, despite being supported in GitHub and GitLab markdown, making Discourse’s default markdown inconsistent with GFM. pfaffman clarifies that self-hosted users can install the plugin, but the argument for standardizing it is compelling. robbie.morrison supports the idea, especially for academic use, and points out outdated documentation stating footnotes are only on Teams and Enterprise plans. mattdm notes that footnotes now appear on business-tier sites, and sam confirms they are now included in all tiers. robbie.morrison seeks clarification on installing the plugin, and JammyDodger explains that footnotes are a plugin, not a theme, and must be installed via the admin plugins section.
Currently, Discourse’s default markdown does not match GFM (for both the major git-based hosting providers for open source projects), with the primary missing piece being footnotes. It would be a good idea to bring the supported syntax back into being synchronised with GFM.
I admin a discourse instance in an academic context (here) and would really encourage footnotes to be built in as standard by default. Perhaps with a site config for admins to turn this feature off as needed.