Clarify group-chat scraping and refresh puppet URLs via the core
This commit is contained in:
@@ -18,7 +18,7 @@ interface ScrapeBackend {
|
||||
| Backend | Implementation |
|
||||
| --- | --- |
|
||||
| `slopbot` | discord.js REST (`channels.messages.fetch`), bucket-aware client |
|
||||
| `puppet` | The core action `message.fetch` over the bridge |
|
||||
| `puppet` | The core action `message.fetch` over the bridge. Expired URLs refresh with `before: id+1`, which returns exactly the target message |
|
||||
|
||||
The daemon picks `slopbot` when the channel is a guild channel and slopbot is configured and in the
|
||||
guild; otherwise `puppet`. A scrape records the backend it used. The walk can resume on the same
|
||||
|
||||
Reference in New Issue
Block a user