Conversation

Notices

1. Annah (maiyannah@community.highlandarrow.com)'s status on Monday, 12-Dec-2016 21:18:19 UTC Annah

   • AndStatus
   • thefaico
   • Annah
   @andstatus @thefaico One important feature I'm going to build into the API is flexibility in what you request and how.  I want it to be easy for clients to get JUST the data they need, as this will alleviate server load greatly (a single API request for a timeline right now can run over a hundred queries in some circumstances!) and also make things much easier for the client.  An important component of this in my opinion is making it so we can easily identify specific resources.
   
   Users, notices, and avatars are on the list of things I want to make uniquely-identified.  Are there other things you can think of which would benefit from this?
   • Temporary Marjolein repeated this.
   • AndStatus (andstatus@loadaverage.org)'s status on Tuesday, 13-Dec-2016 05:54:30 UTC AndStatus

     in reply to

     • MMN-o ✅⃠
     • thefaico
     • 馬鹿野狐(ばかやこ)✔
     • archaeme
     • 災̷̡̆害̎̐͊の̴ͩ̅̔̏女̢ͭ̋͑ͨͤ͝王̡̂̔͆̾͘͟
     @maiyannah 1. Conversations also need Globally unique IDs. They are local numbers also now.
     I'm currently testing usage of Conversation id to get full conversation in one request instead of "discovering" of previous posts one by one: and I'm really impressed by this feature of the API.
     2. Another point of server load optimization: honoring since_id parameter in a search request. I created an issue for this bug several months ago: https://git.gnu.io/gnu/gnu-social/issues/206 ""since_id" parameter is ignored in a "search" request of Twitter-compatible API"
     @mmn
     @archaeme @takeshitakenji @xj9