|
Föderation EN Do 11.01.2024 22:22:58 jfc, I'm using the API docs published on Mastodon Dot Social to implement my Mastodon client, and I test on all sorts of things: Glitch, Akkoma, Catodon, I even set up a GoToSocial server to test on, and they all work exactly as the API docs on Mastodon Dot Social says they should. The single instance that ever gives me trouble in a diverging-from-the-docs-on-Mastodon-Dot-Social-in-unexpected-ways kind of way is, you guessed it, Mastodon Dot bloody Social. I'm so tired, I think I'll go play video games for a bit now. |
|
Föderation EN Do 11.01.2024 22:28:28 @bodil which API feature is misbehaving here? It could be a bleeding edge build thing (m.s runs nightly code rather than the last stable release) |
|
Föderation EN Do 11.01.2024 22:46:57 @andypiper Current road bump is that I need to dig the WebSocket URL for streaming updates from the instance info because it's on a different hostname from the rest of the API, which the API docs don't mention as a possibility. I mean, this is all part of how you get to a working client implementation with broad compatibility, it's just funny that the instance that gives me the most examples of how the protocol diverges between instances is the one that actually publishes the protocol. |
|
Föderation EN Do 11.01.2024 22:53:33 |
|
Föderation EN Do 11.01.2024 23:06:39 @andypiper This should be in the docs (and the "usual" endpoint should redirect to the new URL). I will try to update the docs to add this, unless someone else wants to do it :) |
|
Föderation EN Do 11.01.2024 23:18:08 |
