Make Mastodon Glitch Edition to enunciate/identify/manifest/present itself as such

[KNTRO]

Pitch

I would suggest to glitch-soc! to be reported as such piece of software, instead of being simply Mastodon. Hometown, for instance, presents itself as Hometown, not as Mastodon.

Motivation

There are some websites like FediDB or Fediverse Observer (please, wait for several seconds before the page is fully loaded) that can list the Fediverse by services/software. glitch-soc! servers can't be found there because there is no way for them to be announced as such, since these servers identify themselves simply as Mastodon — They are telling the Fediverse that they are running Mastodon software.

But Hometown identifies itself as Hometown, not as Mastodon. So, people can easily find Hometown servers. Thus, I think that glitch-soc! should do the same thing, not just for admins of glitch-soc! servers, but for users who want to try it out. 😉

[Plastikmensch]

Glitch-soc identifies itself by the version suffix, the same as hometown and many other forks.

That those crawlers either don't or can't parse the version string is not a glitch-soc problem.

[tarper24]

Glitch-soc identifies itself by the version suffix, the same as hometown and many other forks.

That those crawlers either don't or can't parse the version string is not a glitch-soc problem.

Hometown identifies its software name as "Hometown" in the node info, which is what the crawlers read to identify the software. Glitch-soc still identifies the software as Mastodon.

The version is separate.

[Plastikmensch]

Hometown identifies its software name as "Hometown" in the node info, which is what the crawlers read to identify the software. Glitch-soc still identifies the software as Mastodon.

The version is separate.

Ah, you're right. That endpoint doesn't seem to be documented anywhere, so I missed it.

I'm still not sure if changing that makes sense, since glitch-soc is Mastodon under the hood.