What
When a published post is saved, the plugin should compare the relevant federated content (title, content, excerpt, etc.) before and after the edit. If nothing that affects the federated representation changed, no Update activity should be sent.
Why
Currently every post save triggers an Update activity to all followers, even for minor edits like fixing typos in non-federated fields, changing tags/categories, or updating metadata. This creates unnecessary noise in followers' timelines and federation traffic.
See: https://wordpress.org/support/topic/avoid-updates-for-minor-edits-tags-typos/
How
The triage() method in includes/scheduler/class-post.php already receives $post_before. It could transform both the old and new post into their ActivityPub representation (or compare a hash of relevant fields) and skip the Update if they are identical.
What
When a published post is saved, the plugin should compare the relevant federated content (title, content, excerpt, etc.) before and after the edit. If nothing that affects the federated representation changed, no
Updateactivity should be sent.Why
Currently every post save triggers an
Updateactivity to all followers, even for minor edits like fixing typos in non-federated fields, changing tags/categories, or updating metadata. This creates unnecessary noise in followers' timelines and federation traffic.See: https://wordpress.org/support/topic/avoid-updates-for-minor-edits-tags-typos/
How
The
triage()method inincludes/scheduler/class-post.phpalready receives$post_before. It could transform both the old and new post into their ActivityPub representation (or compare a hash of relevant fields) and skip theUpdateif they are identical.