Pleroma reports are malformed
We learned in #2302 (closed) that Pleroma ingests reports from other Pleroma instances, fails to process them properly, and Oban repeats that job a total of 5 times causing 5 duplicate reports to appear. The failure is not entirely atomic, and the report does get created (5x).
We need to identify why our reports forwarded from Pleroma are malformed, but Mastodon's works (except linked statuses #2303)
Edited by feld