Move Pleroma internal fields under `internal_fields` object for activity/object JSON
While implementing Mastodon->Pleroma database migration #162 (closed), it occurred to tag all migrated data, to help debugging and ease transformations.
I was thinking of adding a new internal field, migrator: "1"
, similar to likes
and like_count
, eg:
{"to": [], "cc": [], "object": "https://...", "migrator": "1" }
But I realized Transmogrifier.strip_internal_fields
wont strip them and they could be federated like that, so I'm wondering if maybe internal fields should be stripped by a pattern, eg they all live within a "pleroma": {}
object, or it strips any fields like "pleroma-*": "value"
Seeing some of the issues around shitposter.club, where there's uncertainty whether problems are related to the migration, I think it will be very worth tagging migrated data. Especially since this script is meant to be repeated by other Mastodon instances. However, I'm not really sure if it matters that we strip the field during federation. Interested to know other's thoughts.