mastofe

commit: a0de3222dd38f446483c1a215b0264faa5ab4800
parent: 540b3f37ae904c135809ef2a65f2700ca361de77
Author: ThibG <thib@sitedethib.com>
Date:   Fri, 19 Jan 2018 15:49:48 +0100

Retry delivering toots over ActivityPub for about 2 days (#6298)

Currently, Mastodon will retry delivering toots for a bit over 1 hour.
This is a very short timespan when considering private and direct toots, which
cannot be seen by the recipient at all after the delivery attempts have failed.

Ideally, private and direct toots should have a different number of retries,
but I do not know how to do that.
Diffstat:
M
app/workers/activitypub/delivery_worker.rb
2
+-

1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/app/workers/activitypub/delivery_worker.rb b/app/workers/activitypub/delivery_worker.rb
@@ -3,7 +3,7 @@
 class ActivityPub::DeliveryWorker
   include Sidekiq::Worker
 
-  sidekiq_options queue: 'push', retry: 8, dead: false
+  sidekiq_options queue: 'push', retry: 16, dead: false
 
   HEADERS = { 'Content-Type' => 'application/activity+json' }.freeze