@Coffee @dansup @sexybiggetje @darius 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?

@liaizon @Coffee @dansup @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

https://github.com/mastodon/mastodon/blob/main/app/serializers/nodeinfo/serializer.rb#L13

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

@darius hey @noellabo how are you doing it with Fedibird?

@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; +https://fedibird.com/)

@noellabo @darius (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.

@liaizon @darius Now nodeinfo looks like this.
https://fedibird.com/nodeinfo/2.0
https://nightly.fedibird.com/nodeinfo/2.0