Feature Request: Webhook Message Retention/Expiration

[jimbob-1]

Been playing with automated webhooks recently; and was wondering where expiration or retention field parameter was.

Speaking with on the discord devs, discord, it was suggested that I start a discussion to see if others would find use or value in this feature request.

There's a niche case for expiring webhook messages: with my experience most of the webhook messages are status messages or automatic information (commodity price fluctuations, system statuses, temporary conditions, in-game notifications).

Some of these don't really need persistence, I feel like some of these events could be deleted perpetually from discord systems without the need to retain this data indefinitely. Pictures or embedded attachments could increase in storage costs, depending on dedupe (or, specifically in my case: visually unique images for every webhook post, 100-200KB in size).

I understand storage might be cheaper (one time investment for the committed size) than bandwidth (perpetual cost). Coming from a sysadmin background: it feels morally wrong to shove data to your servers, expecting them to save the data for eternity when the data is useless days (or weeks later).

Anyway, looking to set an option "expires" field to let the backend systems cull old webhook posted messages.

I understand that I can store these message ID's and then DELETE them at some point in the future; but that requires some type of state machine/persistence and logic to then cull the messages at an arbitrary later date.

Thoughts?