Prepare a Discord source #28

Open
opened 2026-11-19 03:29:51 +00:00 by kathleen · 0 comments
Owner

Discord runs aren't available yet. We don't scrape Discord with a personal token: it would need a bot the server allows, or people using the form. The map already has an empty "Discord" layer (measures.yaml path_layers).

When there's a way in, the import should follow Ken's Reddit pattern:

  • a separate collector delivers data/public/discord_runs.json by pull request;
  • the answers are "Report a run" labels, with no usernames and no message text;
  • a discord source in collection/pipeline.yaml (extract kind delivered), coded with the shared answers_row();
  • discord added to the source values in data/dictionary.yaml (croissant regenerates from it);
  • the same plausibility checks, duplicate matching and review routine as Reddit comments;
  • discord added to the shared list of route-recording sources (see "Use every possible run…").
Discord runs aren't available yet. We don't scrape Discord with a personal token: it would need a bot the server allows, or people using the form. The map already has an empty "Discord" layer (`measures.yaml` `path_layers`). When there's a way in, the import should follow Ken's Reddit pattern: - a separate collector delivers `data/public/discord_runs.json` by pull request; - the answers are "Report a run" labels, with no usernames and no message text; - a `discord` source in `collection/pipeline.yaml` (extract kind `delivered`), coded with the shared `answers_row()`; - `discord` added to the `source` values in `data/dictionary.yaml` (croissant regenerates from it); - the same plausibility checks, duplicate matching and review routine as Reddit comments; - `discord` added to the shared list of route-recording sources (see "Use every possible run…").
kathleen added the data quality label 2026-11-19 03:29:51 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: DragonKind/threshing-atlas#28