I migrated from my self-hosted Mastodon instance to mastodon.social. Of course, I couldn't move my posts so I created a small server to provide the archive of my post history without changing any #ActivityPub URIs or media URLs. It seems to be working well. RAM usage is down from 1.2GB to 45MB (-97%) and disk usage down from 160GB to 15MB (-99.99% drop) compared to keeping the old server running. I've been surprised how many "hits" I'm seeing for old posts, so I'm glad the archive is available.
8
Replies
3
Boosts
@Steve_Bate haha you should call it tootback, in homage to this great piece of portability tooling:
In terms of resources have you tried running Akkoma or GoToSocial? Or was it more than resources for your migration?
@Damon my wild-ass guess is ballooning S3 storage costs.
@Steve_Bate wow it was a resource hog when you were running your own instance! I keep thinking about setting my own up but I'm not sure if I want to burden my home server with that 😅
@Steve_Bate do you plan to document the decision and experience?
I found your work with ActivityPub really interesting...
Do you think being on single instance just isn't worth it protocol wise, or are you cooling down on tinkering with socials?
@invisible The Mastodon instance consumed excessive resources IMO in my "home lab" that I'd rather use for something else. If anything, I have more room for tinkering now. 😉 However, it was also always a challenge to stay well-connected with a single-user instance. Even with relays, I was missing out of parts of conversations.
@steve_bate@mastodon.social said:
Even with relays, I was missing out of parts of conversations.
Sad to hear that. I've found that subscribing to fedibuzz has been pretty good for keeping the flow of interesting discussions coming.
activitypub.space aggregates a few that are ActivityPub related.
@julian Yeah, I used Fedibuzz and that definitely
helped.
