Email or username:

Password:

Forgot your password?
Darius Kazemi

So I am likely going to do a minor #hometown release in the coming week or so. This won't have anything to do with bringing us up to Mastodon v4. It will be some bugfixes and feature tweaks, and then also, nerdily but importantly, changing how we do semantic versioning.

Basically even though I think I am doing semver the "right" way, it is not in line with how most of fediverse does it, and this makes it harder for 3rd party apps to detect when a server runs Hometown.

github.com/hometown-fork/homet

10 comments
Darius Kazemi

Ultimately this comes down to changing the versioning string for "Hometown version 1.0.8, synchronized with Mastodon 3.5.5" from

1.0.8+3.5.5

to

3.5.5+hometown-1.0.8

I still cringe a little to look at it but I understand that it'll help other projects and I really want as much 3rd party Hometown support as possible.

As usual: please don't ask why I have decided to do it this way or propose alternatives until you have read the Github thread which contains the rationale.

Mark Sample

@darius Before I read the Github thread which contains the rationale, please let me ask why you've done it this way, because I have some alternatives to propose.

Darius Kazemi

@ConnyDuck nice to get positive feedback from another 3rd party client provider :)

external quantum efficiency

@darius @ConnyDuck I'm excited with the possibilities with tusky and hometown working together! :)

Travis Castillo

@darius i always run into this problem forking libraries and trying to publish feature branches.

Jake

@darius It’s so cool you and the author of that script working this out. Thank you!

Till Krüss

@darius makes sense. I just set up an instance for my hometown at nelson.social :owi:

Go Up