Closed kensanata closed 6 years ago
After thinking about this for a while, I think reposing a bunch of toots should be a manual process. It involves curation and a tool should not be doing it for you.
for people who're migrating to a different instance (esp. to self-hosting), it would be useful to show how to import ActivityPub JSON as the admin of the new instance
If you know how, please post it. I have no idea. You’d have to insert the rows directly into the database somehow. If you use the API the messages are also resent to all your followers and that’s not good.
One could take a look at Calckey implement, which import everything without reposting the content (timestamps are preserved for instance, messages are not resent, …).
yeah I think fundamentally Mastodon implementation doesn't have it, so it can't be done gracefully
well, I guess that would tell you how to upload the data into a Calkey instance; since I run a GoToSocial instance, that would be different; same for Mastodon. The database layout is probably similar but the details will be different every single time. And we definitely wouldn’t be using the Mastodon Client API like we are doing now. It’s an interesting challenge but not for me. 😅
well, I guess that would tell you how to upload the data into a Calkey instance; since I run a GoToSocial instance, that would be different; same for Mastodon
For sure. I simply wanted to point to some hints for anyone willing to try this :)
In theory we could write a tool that reposts statuses to another instance. We would change all the public statuses to visibility unlisted in order to not pollute the local timeline of the destination instance. But it would still be super annoying for all the people mentioned in the statuses.