@timhutton

Using pleroma-bot you can suck that twitter archive.zip directly into mastodon, and have them present as toots.

@timhutton

I don't think so, just pull out an API token from your Mastodon profile.

I started doing it via Twitter API's, until I realised that the API doesn't go back far enough. Then when I saw you could put a `archive.zip` directly in, I'm waiting for that to be prepared.

@Daviey @timhutton admins might be unhappy to have thousands of automated posts hitting their server as the archive imports? 💔

If this impacts other users -- and i don't see how it wouldn't -- this will result in angry emails / messages?

Meanwhile, can you post a link to the tool? Sounds super useful.

@wait_sasha

Sorry, but I think if admins would be unhappy with this, they need to enforce resource limits, which is a feature mastodon supports. It shouldn't be on the user to regulate volume.

(FWIW, I host my own instance so only me that would unhappy)

The tool is here, https://github.com/robertoszek/pleroma-bot

@Daviey @wait_sasha people who aren't on a single user instance would be shitting on the commons, so, yes, that would be a really shitty move and not just something admins need to resource throttle

plus, if you're blasting your tweet history as public posts it'll pollute the federated timeline as well

but either way, all servers with people following you would experience higher load

@meena @wait_sasha

... Then it is the job of the admin to set limits.. Can you imagine if Twitter simply trusted users to not hammer their API?

Regarding too much noise, most people seem to be syncing it as Unlisted so it doesn't pollute the streams.

@Daviey @meena There is a big difference between a multi-billion dollar corporate entity and fediverse instances run by (defacto) volunteers. ❤️

I agree that ideally admins / software could do all the rate limiting needed to support their instance.

In reality though users have to be respectful since we are essentially guests in other people's homes?