Fabio Manganiello on Nostr: My new social home is almost ready at Fabio Manganiello. All of my followers can ...
My new social home is almost ready at Fabio Manganiello (npub13uu…pvgs). All of my followers can start following me there, if they want to.
Checklist:
✔️ Configure DNS + nginx + SSL boilerplate
✔️ Install Akkoma
✔️ Clone profile + settings
✔️ Import list of followed accounts
✔️ Import list of blocked/muted accounts
✔️ Clone list of blocked instances
⌛ Clone posts (if someone has a quick way to migrate posts from Mastodon to Pleroma/Akkoma, please let me know, before I dive down the rabbit hole of either SQL or API scripting)
⌛ Replace all references of `rel="me"` and my PGP keys to point to the new profile
⌛ Formalize the transfer and move all the followers along
⌛ Help/wait for the few users on this instance to export their data before shutting down social.platypush.tech
I may speed up things a bit more because Redis on my instance is dying with out-of-memory every couple of hours now. And I'm running a dedicated Linode box with 8GB of RAM, not an early Raspberry Pi.
Not only Mastodon isn't meant to scale, but it fails miserably even at managing things at a micro scale.
You can't tell people "we're democratizing things, everybody can run their own instance", if running even a personal instance with a decent amount of connections to the rest of the Fediverse involves spinning up a machine with 8GB of RAM, either 100GB of storage or a decent S3 bucket, and forget running this stuff in your home network if you're planning to plug it to a relay.
Its bad design decisions turned it into the Bitcoin of social platforms, and it has become a liability for the Fediverse more than an asset. I'd have saved quite a lot of money had I decided to switch to Akkoma earlier.
Checklist:
✔️ Configure DNS + nginx + SSL boilerplate
✔️ Install Akkoma
✔️ Clone profile + settings
✔️ Import list of followed accounts
✔️ Import list of blocked/muted accounts
✔️ Clone list of blocked instances
⌛ Clone posts (if someone has a quick way to migrate posts from Mastodon to Pleroma/Akkoma, please let me know, before I dive down the rabbit hole of either SQL or API scripting)
⌛ Replace all references of `rel="me"` and my PGP keys to point to the new profile
⌛ Formalize the transfer and move all the followers along
⌛ Help/wait for the few users on this instance to export their data before shutting down social.platypush.tech
I may speed up things a bit more because Redis on my instance is dying with out-of-memory every couple of hours now. And I'm running a dedicated Linode box with 8GB of RAM, not an early Raspberry Pi.
Not only Mastodon isn't meant to scale, but it fails miserably even at managing things at a micro scale.
You can't tell people "we're democratizing things, everybody can run their own instance", if running even a personal instance with a decent amount of connections to the rest of the Fediverse involves spinning up a machine with 8GB of RAM, either 100GB of storage or a decent S3 bucket, and forget running this stuff in your home network if you're planning to plug it to a relay.
Its bad design decisions turned it into the Bitcoin of social platforms, and it has become a liability for the Fediverse more than an asset. I'd have saved quite a lot of money had I decided to switch to Akkoma earlier.