@Coffee @liaizon @darius @dansup @sexybiggetje@mastodon.social @apps As you pointed out, only metadata can add free items in NodeInfo (2.0 or 2.1), and even if you allow free text in name, you will have problems similar to User-Agent. That is, you must list the names of compatible products.
> Mozilla / 5.0 (X11; Linux x86_64) AppleWebKit / 537.36 (KHTML, like Gecko) Chrome / 51.0.2704.103 Safari / 537.36
@Coffee @liaizon @darius @dansup @sexybiggetje@mastodon.social @apps In the method I did this time, for example, when I forked Glitch-soc, I proposed and implemented such an expression.
software: {
name: "mastodon"
},
metadata: {
forks: {
{
name: "glitch-soc"
},
{
name: "my-fork"
}
}
}
If there is a better way, follow it.
@Coffee @liaizon @darius @dansup @sexybiggetje@mastodon.social @apps Pleroma outputs the implementation status of individual functions in detail, but Mastodon is starting to add data to /api/v1/instance. Fedibird lists valid features here (fedibird_capabilities). This is used by client apps such as Subway Tooter.
https://fedibird.com/api/v1/instance
