Ignore delivery problems with drops

diff --git a/src/Protocol/ActivityPub/Delivery.php b/src/Protocol/ActivityPub/Delivery.php
index 966f0e5e16880fb089047f7b09b914dd66bb58b1..ebf8ffb2b60620d03e8119d6889a9c8bb7bf6220 100644 (file)
--- a/src/Protocol/ActivityPub/Delivery.php
+++ b/src/Protocol/ActivityPub/Delivery.php
@@ -144,6 +144,11 @@ class Delivery
                                                if (!empty($actor)) {
                                                        $drop = !ActivityPub\Transmitter::sendRelayFollow($actor);
                                                        Logger::notice('Resubscribed to relay', ['url' => $actor, 'success' => !$drop]);
+                                               } elseif ($cmd = WorkerDelivery::DELETION) {
+                                                       // Remote systems not always accept our deletion requests, so we drop them if rejected.
+                                                       // Situation is: In Friendica we allow the thread owner to delete foreign comments to their thread.
+                                                       // Most AP systems don't allow this, so they will reject the deletion request.
+                                                       $drop = true;
                                                }
 
                                        }