If a webhook message is posted into a regular text channel, it can be attached to a thread after it's creation - but only by an application or user, which is outside of the scope of operation for this library in itself but the library can send messages to it natively if it becomes aware of it's existence.
This ties closely with instance data and any intended caching functionality that arrives in the future. Because the webhook can be made aware of the existence of the thread, it effectively allows the use of a Channel substructure - but only for text channels (forum posts may have the same initial message id, but has no thread data attached).
If a webhook message is posted into a regular text channel, it can be attached to a thread after it's creation - but only by an application or user, which is outside of the scope of operation for this library in itself but the library can send messages to it natively if it becomes aware of it's existence.
This ties closely with instance data and any intended caching functionality that arrives in the future. Because the webhook can be made aware of the existence of the thread, it effectively allows the use of a Channel substructure - but only for text channels (forum posts may have the same initial message id, but has no thread data attached).