I migrated from my self-hosted Mastodon instance to mastodon.social.
-
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.
-
@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. -
@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.
-
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.
@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

-
@julian Yeah, I used Fedibuzz and that definitely
helped. -
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.
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.
Ciao! Sembra che tu sia interessato a questa conversazione, ma non hai ancora un account.
Stanco di dover scorrere gli stessi post a ogni visita? Quando registri un account, tornerai sempre esattamente dove eri rimasto e potrai scegliere di essere avvisato delle nuove risposte (tramite email o notifica push). Potrai anche salvare segnalibri e votare i post per mostrare il tuo apprezzamento agli altri membri della comunità.
Con il tuo contributo, questo post potrebbe essere ancora migliore 💗
Registrati Accedi
Citiverse è un progetto che si basa su NodeBB ed è federato! | Categorie federate | Chat | 📱 Installa web app o APK | 🧡 Donazioni | Privacy Policy