@sexybiggetje is this something that would make sense to change? adding some identification that is easy to parse that makes it not lump hometown with vanilla mastodon?

@sexybiggetje working on this right now -- weirdly, changing the string here from "mastodon" to "hometown" and restarting all processes isn't changing the rendered nodeinfo output

github.com/mastodon/mastodon/b

Wondering if there is some kind of render step I'm missing... (rails is still mostly a mystery to me)

@liaizon @darius I'm still not sure if the Mastodon fork should give a name other than Mastodon in nodeinfo.

It always follows Mastodon's main branch, because it's still Mastodon.

However, let's call it Fedibird here according to the desire to distinguish.

software: {
name: “fedibird”,
version: “0.1”
},

In addition, Fedibird adds the version of Fedibird to the user-agent string.

> http.rb/4.4.1 (Mastodon/3.4.1 Fedibird/0.1; +fedibird.com/)

(sorry for this basic question) how would one query the user agent string of a server. Or rather, how can I see what user agent is set if all I have is the domain of an instance?

@liaizon @darius The reason for adding the fork name to the user-agent is to give a hint to the server operator, so that access from the server calling itself fedibird can be blocked by nginx and traffic can be aggregated.

eyyyyyy. the forks will suddenly look quite different in stats now!

might make sense to do what is doing and show the two version numbers together. So hometown has the version number listed as "3.4.0+1.0.5" so the 3.4.0 is the version of mastodon its basing off of and 1.0.5 is the version of hometown thats ontop

@liaizon @darius Fedibird didn't choose that expression for several reasons. If you do, it may be "main+0.1", as it doesn't necessarily match the Mastodon tag release. If Mastodon has a tag release, the version of Fedibird will be updated at that time.

You can get the Mastodon version from /api/v1/instance.

ログインして会話に参加
Fedibird

様々な目的に使える、日本の汎用マストドンサーバーです。安定した利用環境と、多数の独自機能を提供しています。