mastodon VS migrator

I'm the admin of a small server, which I set up a few months ago with the one-click install and then migrated to glitch-soc (https://glitch-soc.github.io/docs/). Recently I tried updating it to the new version of glitch-soc due to recent security updates. However I seem to have broken my server.

I imagine it might turn out to be something similar to https://glitch-soc.github.io/docs/

Have a look at glitch - a fork of Mastodon that looks and feels and behaves mostly just like mastodon but has Markdown support.

A good start to see Mastodons upstream finally implement features considered so necessary that they existed in a fork for years beforehand[0].

I'm not trying to sound cynical, this is legit a good change. Other fedi implementations have supported different message formatting (mainly markdown) for ages and that shit still degrading away to plaintext on Mastodon is extremely aggravating if you decide to (for example) use a bulletpoint list.

[0]: https://glitch-soc.github.io/docs/

You don't have to maintain a soft fork; Glitch-soc is a "friendly fork" which shares maintainers with upstream and has lots of great features, including a configurable post length limit.

What the fuck is your problem? Why do you some here just to see? Are you so fucking retarded that you don't think this issue have been brought up before? Do you think I'm just making up this on the spot? https://github.com/glitch-soc/mastodon/pull/1502 https://github.com/GlitchCatFedi/Policy/blob/main/Global%20Fulltext%20Search.markdown

Can we expect to see any of the https://glitch-soc.github.io/docs/ features coming to Mastodon mainline soon? Post formatting? Highlighting of misleading links? or local only posting?

Mastodon Glitch Edition

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

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.