Discourse

From Archiveteam
Jump to navigation Jump to search
Discourse
(part of the Webforums subcommittee)
Discourse logo
Status Special case
Archiving status Unknown (manual)
Archiving type Other
IRC channel #msgbored (on hackint)

Discourse is a forum/Q&A hybrid. It is both an open-source forum software and a forum hosting service.

The Good

Discourse markets itself as a concoction of the good collaborative environment of old-school forums, and the interactivity of modern websites. It's also open-source, you can run a Discourse forum of your own.

The Bad

Discourse also offers hosting for a very hefty price (~$100 per month). As such, it's very possible that anyone who's using their hosting for their forum could chicken out at any minute, meaning their forum is incredibly volatile. See the Known Victims section for further details.

Archiving

A default Discourse instance uses incremental IDs for channels, topics and replies. There will most likely be instances with exemptions, utilising other ID systems.

To get topics as a JSON with cooked HTML text and other verbose variables, you can use "/t/*.json" (e.g. "https://ytpmania.net/t/15378.json"). You can also get JSON for categories ("https://community.cloudflare.com/c/whats-new/57.json") and users ("https://forum.snapcraft.io/u/igor.json").

The raw markdown text of a topic can be saved with the "/raw/" path ("https://devforum.roblox.com/raw/40471").

A JSON or raw text of a topic can be limited to a certain amount of replies; you can add a reply number to the URL to get a singular reply ("https://discourse.lubuntu.me/raw/3528/9").

A URL that only uses numbers will redirect to a URL with the name included (e.g. "https://forum.opencv.org/t/7" will lead to "https://forum.opencv.org/t/welcome-to-opencv-forum/7"). This does not apply to "/raw/" and "/t/*.json" paths.

Discovery

The URLs project is discovering Discourse instances and storing them in the discourse-inbox queue for a later DPoS Discourse archiving project.

ArchiveBot Usage

Discourse works "reasonably well" in ArchiveBot. Currently it is not covered by the forums igset and may be run without an igset. Playback works in the WBM but JS must be disabled.

Many Discourse instances seem to be rate limited so that they will return 429s after a few minutes even with default parameters. But they do recover quickly and seem to be fine with -concurrency 2 -d 500.

Notable Discourses

At Risk

May be phased out with new API. Last reachable May 4, 2023.[1]

Went read-only on 1 January 2021, migrating to GitHub Discussions.

Went read-only on 25 May 2018, migrated to Stack Overflow.

Active Discourses

Known Victims

  • Imgur Community Forums [3]

Uncategorized List of Found Discourse Forums

See: Discourse/uncategorized

List of Archived Discourse Forums

References

  1. ↑ https://web.archive.org/web/20230504170115/https://twittercommunity.com/
  2. ↑ https://web.archive.org/web/20200623173220/https://discourse.cord-19.semanticscholar.org/t/faqs-about-cord-19-dataset/94
  3. ↑ https://web.archive.org/web/20200521041503/https://community.imgur.com/t/the-imgur-community-forum-is-closing-effective-may-22-2020/73256
  4. ↑ https://git.feneas.org/feneas/association/-/raw/master/comms/dissolving-the-association-2022-01-09.txt
Retrieved from "https://wiki.archiveteam.org/index.php?title=Discourse&oldid=55706"