I'm not sure what this means. The text you commented out describes the transfer between providers, and a different provider may simply have a different release of Fediversity deployed. While this may be a future-me sort of problem, depending on the release cadence and upgrade adoption delay by providers it may not be all that likely that two providers run the exact same release, and we need to at least to take that into account. The minimum that should happen initially is providing a UI for the case where two providers don't have the same version even if nothing can be done about it, and then keep at the back of our heads a user story for migrating and at the same time bumping the release, or something like that.
Oh yeah the first two commits also contain sketches to create modules from Python, but that was code from before I settled on the other direction (and also the second one is not particularly…