[feat] Let expires_in from API request overwrite user setting, not the other way arround. #898

New issue

Closed

opened 2025-04-08 09:51:39 +00:00 by xarvos · 1 comment

xarvos commented

2025-04-08 09:51:39 +00:00

The idea

When I set auto-deletion in my profile, when I create a new post, the expiration will always be the duration in this setting, ignoring the expires_in parameter I pass in the API.

It should be able to overwrite the setting by the API parameters.

The reasoning

While I may want my posts to be ephemeral by default, there are some certain posts that I may want to be up permanently, like posts syndicated from my website for example.
Alternatively, I may want some of my posts to be expired earlier than the set duration.
In these cases, I'd want to be able to overwrite the user setting with the API parameters.

Have you searched for this feature request?

I have double-checked and have not found this feature request mentioned anywhere.
This feature is related to the Akkoma backend specifically, and not pleroma-fe.

### The idea When I set auto-deletion in my profile, when I create a new post, the expiration will always be the duration in this setting, ignoring the `expires_in` parameter I pass in the API. It should be able to overwrite the setting by the API parameters. ### The reasoning While I may want my posts to be ephemeral by default, there are some certain posts that I may want to be up permanently, like posts syndicated from my website for example. Alternatively, I may want some of my posts to be expired earlier than the set duration. In these cases, I'd want to be able to overwrite the user setting with the API parameters. ### Have you searched for this feature request? - [x] I have double-checked and have not found this feature request mentioned anywhere. - [x] This feature is related to the Akkoma backend specifically, and not pleroma-fe.