Email or username:

Password:

Forgot your password?
2 posts total
Tokyo Outsider (337ppm)

Sorry it took longer than intended, but... #MastodonContentMover is now mentioned and linked in the #Mastodon official Github issue for supporting post migration 👉 github.com/mastodon/mastodon/i

Please give it a thumbs up if you see fit 🙏

Tokyo Outsider (337ppm)

Request for admins: You might've seen this mentioned, but I wrote a tool to help people move their posts when they change instances.

It's still in development, but I'd like to hear from instance admins if there's anything about it they're worried might affect their instances, or anything that could be made clearer in the documentation to help.

The documentation is here: mastodoncontentmover.github.io

If you have time, it'd be great to hear your thoughts 🙏

#MastoAdmin

(Boosts much appreciated!)

Request for admins: You might've seen this mentioned, but I wrote a tool to help people move their posts when they change instances.

It's still in development, but I'd like to hear from instance admins if there's anything about it they're worried might affect their instances, or anything that could be made clearer in the documentation to help.

Show previous comments
Rémy Grünblatt 🍃

@tokyo_0 So you mean if someone with hundreds / thousands of messages migrate, it will respam them on the local / global feed ? That would be an instant ban from me, I think, because that would be, well, spam… We're a small instance, the local feed still has meaning, this would pollute it by reposting content that is not tied to a specific date and time.

Wander ΘΔ :verified_paw:

@tokyo_0 Biggest concern is rate limits and the option to send them out as public instead of unlisted (this could impact federated timelines of all instances that are connected to us via relay).

My ideal solution to this problem is to actually take the too archive and find a way to host it in form of a website. Then have the user's first toot be: click here to view my older toots.

Reposting is fine, but users should know to do so before doing the actual migration of the account so that followers aren't spammed.

@tokyo_0 Biggest concern is rate limits and the option to send them out as public instead of unlisted (this could impact federated timelines of all instances that are connected to us via relay).

My ideal solution to this problem is to actually take the too archive and find a way to host it in form of a website. Then have the user's first toot be: click here to view my older toots.

Go Up