From fccb0bc102f2a54a21eed343cda64f9a5221b677 Mon Sep 17 00:00:00 2001 From: Vyr Cossont Date: Wed, 12 Feb 2025 09:49:33 -0800 Subject: [feature] Implement backfilling statuses thru scheduled_at (#3685) * Implement backfilling statuses thru scheduled_at * Forbid mentioning others in backfills * Update error messages & codes * Add new tests for backfilled statuses * Test that backfilling doesn't timeline or notify * Fix check for absence of notification * Test that backfills do not cause federation * Fix type of apimodel.StatusCreateRequest.ScheduledAt in tests * Add config file switch and min date check --- example/config.yaml | 13 +++++++++++++ 1 file changed, 13 insertions(+) (limited to 'example') diff --git a/example/config.yaml b/example/config.yaml index b618ad7ba..2b3a873fb 100644 --- a/example/config.yaml +++ b/example/config.yaml @@ -458,6 +458,19 @@ instance-subscriptions-process-every: "24h" # Default: "" instance-stats-mode: "" +# Bool. This flag controls whether local accounts may backdate statuses +# using past dates with the scheduled_at param to /api/v1/statuses. +# This flag does not affect scheduling posts in the future +# (which is currently not implemented anyway), +# nor can it prevent remote accounts from backdating their own statuses. +# +# If true, all local accounts may backdate statuses. +# If false, status backdating will be disabled and an error will be returned if it's used. +# +# Options: [true, false] +# Default: true +instance-allow-backdating-statuses: true + ########################### ##### ACCOUNTS CONFIG ##### ########################### -- cgit v1.3