-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mastodon Node: consider adding back server_version
.
#282
Comments
server_version
.server_version
.
We need a thought-out approach for dealing with application versions, which we have sidestepped so far.
Are there are other needs for the version? We have |
For the Mastodon-compatible nodes, we don't need to put version in the parameters since we can get it via the API. Many other servers provide version information using an embedded nodeinfo endpoint. Non-Mastodon nodes could attempt a nodeinfo query to automatically get the version and then fallback to manually-configured parameters as a last resort if that fails. |
At a minimum, we'll want to document which Mastodon-like instance version is being tested and it would be easier (and less error prone) to ask the instance for that information.
It's not clear to me what versions the pseudo-Mastodon APIs report. I know some client apps require specific versions of Mastodon, so using an arbitrary version number could cause problems in those cases.
Also, by my counts, there are > 300 different Mastodon versions (not including Mastodon-compatible apps) deployed in the Fediverse. It could be interesting to test some of the older versions at some point.
The text was updated successfully, but these errors were encountered: