Untitled attachment

Notices where this attachment appears

1. AndStatus (andstatus@loadaverage.org)'s status on Monday, 12-Dec-2016 16:09:33 UTC AndStatus
   @maiyannah My main wish for GNU Social API improvement is to have URIs (globally unique identifiers) of users and messages everywhere, where now ”local" IDs are used. I see local ids usage as a major deficiency of current API. Which breaks federation (from a client point of view) and provides a small window - one "instance" of the network, via which the whole communication occurs.
   Moreover, I would suggest not to reinvent a wheel and lookup current API of Pump.io - implementation of ActivityStreams v.1. BTW, It's version 2.0 is currently a Recommendation draft of W3C https://www.w3.org/TR/activitystreams-core/
   @archaeme
2. AndStatus (andstatus@loadaverage.org)'s status on Tuesday, 01-Mar-2016 06:29:35 UTC AndStatus

   in reply to
   @mmn As you didn't answer yet, I will put my question another way:
   Do you, as a main GNU Social developer, recommend to switch a client application from Twitter API to Activity Streams in JSON format?
   The format specification got a follow up, which we may become confirming to in order to ease integration with other systems: https://www.w3.org/TR/activitystreams-core/
   ?!
   BTW congratulations for making more commits to GNU Social codebase than Evan did.
   PS: I suspect that no GNU Social client application uses Activity Streams JSON format to connect to GNU Social. Am I right?