Conversation

Notices

1. Embed this notice
   F4GRX Sébastien (f4grx@chaos.social)'s status on Friday, 02-Aug-2024 18:56:12 JST F4GRX Sébastien

   • dansup

   @dansup as a de facto central dev authority they can just 1-code properly to avoid breakage of 3rd party apps because of the new features , and 2-just publish an update notice and everyone will follow.

   I want to avoid false reasons based on potential technical incompetence.

   • Tim Chambers repeated this.
   • Embed this notice
     F4GRX Sébastien (f4grx@chaos.social)'s status on Friday, 02-Aug-2024 19:03:03 JST F4GRX Sébastien

     • dansup

     @dansup i am not familiar with the code base, true, and devil is usually in the details I know, but I am familiar with long term compatibility of evolving products.

     A stable versioned api is good. I think most of the work should be on client apps, right? Client apps can test for new versions of APIs and gracefully fall back on previous versions? This sounds like a valid design pattern even if I'm not actually familiar with the implementation details...

   • Embed this notice
     Tim Chambers (tchambers@indieweb.social)'s status on Saturday, 03-Aug-2024 08:59:14 JST Tim Chambers

     • dansup

     @dansup Very good point. I do like how you are paving ground other fedi projects can learn from and use... a good model.