@Dzahn @Quiddity possibly of interest. Is a variation of this planned under different context?

Sorry, while I implemented the warning message I don't have knowledge of further plans around it.

@bd808 This might be relevant to your ideas.

In T425039#11878936, @Quiddity wrote:

@bd808 This might be relevant to your ideas.

As of today, there is a tool at https://etherpad-backup.toolforge.org/ that can be used for self-service archiving of etherpads to html exports stored in the WMCS object store. I could see future integrations being possible to provide something like @Sj's suggestion, but that is also going to need integration on the etherpad side.

At the moment I have only heard of plans to do a one-time purge of pads (T415237: etherpad table size is 233GB / plan to delete all etherpads in May 2026). I guess we need to find out who is going to design and implement changes on the etherpad side to auto-prune pads and see if some additional things can be attached to that plan. @LSobanski may be a reasonable person to tell about @Sj's idea, so I will boldly ping them in here.

I don't know how the projected 90-day expiration will be implemented or made visible to editors. ( see T421316 )

Given how pads are used in our communities, unlike riseup, the default case should be preserve, not destroy.