I think I’m going to have to switch kamloops.social to GlitchSoc.

Not having markdown support is a big bummer.

I find this human form limiting. 😂

#MastoHost #FediAdmin

@fname How are you planning on doing that?
@kinetix
I don’t know. 😆
@kinetix
I’m thinking of treating it like a migration to new/different hardware.

@fname I don't know of any path to un-merge hometown, nor reverse the db changes. There may well be a path, but there's no documented way to do so that I've seen.

And if you can't un-merge hometown from the Mastodon code (and revert the db schema), then I don't think you can likely move forward to glitch-soc.

@kinetix
Hmm. Interesting.

The documentation for GlitchSoc speaks to reverting from Glitch to vanilla Mastodon, so I assumed that the same would be possible from Hometown to vanilla. 🤔

@fname I find it rather amusing that they say it's like totally possible, dude, except that they don't mention how you revert the db migrations, which, to me, is a pretty critical part. At least, I don't know if there's some bundle command to run migrations in reverse.

For hometown, I don't know which page/doc it's in, but there was a note by Darius that he wanted to document the reversing of hometown.

Maybe clone the thing somewhere before attempting anything... heh.

@kinetix
Oh, yeah. Cloning is always the first step. I’ve learned that the hard way. 😂

So, I’ve reverted the instance back to Vanilla (v4.6.0-rc.1), basically by performing an ‘upgrade’ as per the official Mastodon documentation. Things seem to be ticking along just fine. (I’m going to give it a few beats before I start messing with anything further.

I’m not convinced that the database itself is materially different between the HomeTown/GlitchSoc/Vanilla forks, but certainly not an expert in these matters.

@fname I was curious and did a diff between hometown and plain masto to see what db migrations were done... so if I understand the migrations process properly, it appears there's just a few columns created and user settings fields for migration.

It does look pretty benign, but I believe it all would continue to exist in the db. Hopefully it wouldn't cause confusion for user migration in the future.