-
hometown
A supported fork of Mastodon that provides local posting and a wider range of content types.
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
So this one is a fork, and infosec.exchange is a fork (https://github.com/glitch-soc/mastodon); are the mastodon committers opposed to incorporating those changes, or this fork situation is "as it should be" while these experiments run their course?
I'm all for experimentation, but since "the exodus" I've become acutely aware of how many instances are out there advertising their version number, so the first big rails (or mastodon itself) vuln is going to be some ooooonooooz
"By our best understanding, our major changes are not wanted by the Mastodon project, hence maintaining this fork instead of trying to commit the changes to Mastodon."
https://github.com/hometown-fork/hometown#readme
My understanding is in theory yes. But in practice things might be more complicated.
Like merely keeping the same name and domain is easy enough. Just shut down the old system, start the new one, create an account with the same name. Of course you would need to refollow everyone. I'm not sure what happens to your followers. Your new server will not know they are followers, so unless this triggers mastodon to try to automatically refollow, I think they are left in a half-broken state. You definitely lose all your old content. All in all, this is not really a great option.
For a full migration where in theory everything works, you could try to follow the linked process to migrate to Pleroma 2.0.5, and then obviously just upgrade to latest following plemora documentation for upgrading. description of migration process: https://icyphox.sh/blog/mastodon-to-pleroma/ (This is based on the following migrator: https://gitlab.com/soapbox-pub/migrator). I have no idea if it works with newer mastodon minor releases.