Conversation

Notices

1. Annah (maiyannah@community.highlandarrow.com)'s status on Thursday, 14-Jun-2018 21:41:34 EDT Annah
   Most of GS's and by extension !postActiv's "core" features are actually not-very-well-integrated plugins and the API is one of the things that suffers for that.  Moving them into the core as modules was a good first step, but they need to be in the API and in a /good API/.  I recognize that most of the poor design decisions in the existing API are a result of replicating Twitter's mistakes, but we don't have to; and frankly since many twitter-based applications don't work with postActiv already, I feel inclined to take the opprotunity to write a better API that's built to suit.
   1. Annah (maiyannah@community.highlandarrow.com)'s status on Thursday, 14-Jun-2018 22:08:05 EDT Annah

      in reply to
      Part of the problem, especially with ActivityPub, is that you have so many ways to display the same information that it becomes impossible to support everyone's different use cases and you have so many edge cases they tesselate together to become a nice little circle Bob Ross would be happy with.
      
      I will probably dictate a specific format with specific endpoints for different things in !postActiv 's new API when I get there, but I'll have to think on what I think would be the most efficient thing in that regard.
      
      I will also hasten to note the old API isn't going anywheres (but the new one is probably what will get development in the future)