It would be neat if TTL could support a sort of "windowed" conversation. For example, if a user wants to set a limit for 10,000 messages and a TTL of 7 days, then that means a channel getting 11,000 messages within a day will delete the oldest 1,000.
I think there are some design decisions that need to be thought out prior to working on this, though. One big question I want answered is why might someone want such a windowed TTL?
For my use case, I think having some type of restriction on the total message count lowers the bar for new people to enter any given conversation, especially if they prefer to back-read. I think that back-reading can be valuable for the health of a community so I want to ensure that a message window system does not work against active back-readers, but I do think TTL could maybe allow enforcing some type of granular deletion policy based on a channel's activity.
Anyways, that's my thought spill. I'm putting it into an issue for later 😆
It would be neat if TTL could support a sort of "windowed" conversation. For example, if a user wants to set a limit for 10,000 messages and a TTL of 7 days, then that means a channel getting 11,000 messages within a day will delete the oldest 1,000.
I think there are some design decisions that need to be thought out prior to working on this, though. One big question I want answered is why might someone want such a windowed TTL?
For my use case, I think having some type of restriction on the total message count lowers the bar for new people to enter any given conversation, especially if they prefer to back-read. I think that back-reading can be valuable for the health of a community so I want to ensure that a message window system does not work against active back-readers, but I do think TTL could maybe allow enforcing some type of granular deletion policy based on a channel's activity.
Anyways, that's my thought spill. I'm putting it into an issue for later 😆