Conversation

Notices

1. Embed this notice
   humanetech (humanetech@mastodon.social)'s status on Thursday, 01-Sep-2022 16:02:33 JST humanetech

   • dansup
   • lars

   @dansup @dumpsterqueer

   As @ls is saying on the thread fork, the choice was made to support the Mastodon API. If you see it in that light, then adhering to the quirks and pace set by #Mastodon seems like the logical consequence of that choice.

   Alternatively you might say, we no longer do that, take Mastodon API as a starting point, and develop a Fediverse API that can facilitate all the ways where apps match as well as where they diverge. Then it is Mastodon's choice if they will follow that.

   • Embed this notice
     humanetech (humanetech@mastodon.social)'s status on Thursday, 01-Sep-2022 16:09:24 JST humanetech

     • dansup
     • lars

     @dansup @dumpsterqueer @ls

     I am no expert in extensible API design, but maybe things can be sliced in such way that additional extensions can be facilitated more easily without that leading to a 'fork in the road'.