{"p":"","h":{"iv":"ROXSYW+cfvEbFHu5","at":"ocxplSQjdRC3tXEtB/9/wg=="}}

Jake

@shadowfacts @michcia @darius Given that other forks are doing things even more differently, is this a "the horse has already left the barn so why close the barn doors" kind of situation?

If a client wants to be branch-compatible, I guess they have to be better about parsing the version string. But it means that the branches may not work with some plugins/clients, even though they could.

Darius - I appreciate that you thought about the convention here!

1
Share
Share on Mastodon
Share on Twitter
Share on Facebook
Share on Linkedin
Darius Kazemi

@gogobonobo @shadowfacts @michcia seems like the route to take is to parse .well-known/nodeinfo, then where applicable follow the `href` to wherever it points you (for masto/hometown it's) friend.camp/nodeinfo/2.0

and then handle parsing based on "name" and "version" fields

0
2y
Replies