Confusion About Post Expiration Settings and Suggestion for a Simpler User Experience #212

New issue

Closed

opened 2026-06-29 16:20:06 +00:00 by nienty · 0 comments

nienty commented

2026-06-29 16:20:06 +00:00

(Migrated from codeberg.org)

I'm a bit confused about the "Default Expiration Time" setting under "Post Expiration".

From what I understand, there are two levels of configuration:

A default setting in the application's preferences.
An individual setting for each post.

My understanding is that if I explicitly set a post to "Never Expires", that per-post setting should override the default expiration setting.

However, I noticed that all of my posts older than 30 days were deleted, even though those posts had "Never Expires" selected.

To better understand how this is supposed to work, I've started a small test with three new posts. I'll monitor them over the next few days. If they are still visible on my profile after two or three days, that will help clarify the expected behavior. If they disappear despite being set to "Never Expires", it may indicate a bug or an unexpected interaction between the default and per-post settings.

I'm posting this here because it's the easiest way for me to keep my screenshots together with the reasoning behind my observations.

Could you please clarify the intended behavior? Should the "Never Expires" option on an individual post always take precedence over the "Default Expiration Time", or can the default setting still cause those posts to be deleted?

I'd also like to suggest a usability improvement. There seem to be several settings controlling the same feature, which can make the behavior difficult to understand. Would it be possible to simplify this part of the interface by offering a Simple Mode and an Advanced Mode?

In Simple Mode, only the default expiration setting would be displayed, which would be sufficient for most users.
In Advanced Mode, users could override the default behavior and define the expiration time for individual posts.

I think this approach would make the feature much more intuitive while still preserving its flexibility for advanced users.

I'm a bit confused about the "Default Expiration Time" setting under "Post Expiration". From what I understand, there are two levels of configuration: A default setting in the application's preferences. An individual setting for each post. My understanding is that if I explicitly set a post to "Never Expires", that per-post setting should override the default expiration setting. However, I noticed that all of my posts older than 30 days were deleted, even though those posts had "Never Expires" selected. To better understand how this is supposed to work, I've started a small test with three new posts. I'll monitor them over the next few days. If they are still visible on my profile after two or three days, that will help clarify the expected behavior. If they disappear despite being set to "Never Expires", it may indicate a bug or an unexpected interaction between the default and per-post settings. I'm posting this here because it's the easiest way for me to keep my screenshots together with the reasoning behind my observations. Could you please clarify the intended behavior? Should the "Never Expires" option on an individual post always take precedence over the "Default Expiration Time", or can the default setting still cause those posts to be deleted? I'd also like to suggest a usability improvement. There seem to be several settings controlling the same feature, which can make the behavior difficult to understand. Would it be possible to simplify this part of the interface by offering a Simple Mode and an Advanced Mode? In Simple Mode, only the default expiration setting would be displayed, which would be sufficient for most users. In Advanced Mode, users could override the default behavior and define the expiration time for individual posts. I think this approach would make the feature much more intuitive while still preserving its flexibility for advanced users.