[feature] Database Migration Path for Mastodon => GoToSocial

[superseriousbusiness]

[feature] Database Migration Path for Mastodon => GoToSocial

[jwbjnwolf]

With Mastodon 4.0 completely doing away with the static html public ui, and that the web ui for logged out users is COMPLETELY useless with authorized fetches enabled, I would absolutely like to be able to do a migration to GoToSocial asap.

I would if it was all just public accounts, just use wget to download and store a static archive of the instance and start new, and move followers, but I run a private account circle on it, so that would be all lost.

To show how ridiculous it is this new Mastodon update.. here's my profile on my instance, and here's my profile on my test instance.. I'm just so mad and upset.. and I can't stay on 3.5.3 forever, especially that I'm on glitch which is always the latest changes so if I need to reinstall.. I'm done for...

And yea the posts and media is crucial, maybe not for everyone but 100% for me.

Edit: Got a fork setup now for 3.5.3 of Glitch with the most recent changes before switching to v4.0, so I'm not done for upon a reinstall now, but yea.. as soon as GoToSocial is where it needs to be to provide migration functionality, I'm jumping right over.

[tsmethurst]

Please try to keep comments in this thread on-topic re: technical implementation of database migration path. I'm aware people are frustrated with Mastodon for various reasons, but this isn't the place to vent that.

[tsmethurst]

See also #928

[progval]

@jwbjnwolf For what it's worth, Mastodon is going to fix this issue by allowing public API access despite AUTHORIZED_FETCH in the next RC: mastodon/mastodon#19803

[norayr]

i am refreshing this page from time to time because i am eager to replace mastodon with gotosocial, and i am waiting for solution. i will migrate even if it will be only possible years later.

i think i am not alone. many mastodon administrators are fed up with different js and ruby issues, plus they have lots of performance issues.

we need something as simple and fast as gotosocial, so if migration be possible one day, i expect many instances to move away from mastodon.

at least my friends who run instances will be happy to migrate.

[ShadowJonathan]

a note: it's probably required for GtS to extrapolate from database entries in mastodon certain things such as scheduled posts, Poll closure notices, and other scheduled events, as mastodon stores these in the redis queues

[breuxi]

I would also be happy to migrate my instance which I share with a few friends as soon as possible, because it is growing indefinitely thanks to their database and media cache choices. 😭

[ShadowJonathan]

you can run pruning database tasks;

bundle exec bin/tootctl media remove --days 30 --concurrency 100
bundle exec bin/tootctl media remove-orphans
bundle exec bin/tootctl media remove --prune-profiles -c 25
bundle exec bin/tootctl cache clear

[breuxi]

@ShadowJonathan Yeah, thank you! Since running these (as a cron job) and reducing the number of days down to 14, I am finally down to about 10GB in file and 3GB in database storage. I still don't know if that's optimal for about 4 accounts with only one of them quite active, but at least better than the 60GB it took once before. 😂

[tsmethurst]

Also worth mentioning that Move (ie., account migration) will be finalized in version 0.15.0 of GoToSocial, which is currently in the release candidate stage. It's not a database migration path, but with Move you will be able to Move your account's followers on an account on a different instance (eg., a GoToSocial account), much as you can now Move between Mastodon instances (and other software types).