Conversation

Notices

1. AndStatus (andstatus@loadaverage.org)'s status on Monday, 24-Apr-2017 06:06:28 UTC AndStatus

   • Juanjo Faico
   • Maiyannah Bishop
   @maiyannah Thank you for the link to the Micropub specification. Seeing verbose descriptions and references to test suites is a real pleasure after a couple of days fighting with ad-hoc Mastodon client API and its server HTTP 500 errors without any clues...
   The main question here is if real Social networks will _really_ support the specification. I mean support in the sense that non-conformance to the specification would be considered a bug that needs to be fixed.
   I will update AndStatus to support this protocol, if GNU Social developers implement it on a server side.
   • AndStatus (andstatus@loadaverage.org)'s status on Monday, 24-Apr-2017 06:52:35 UTC AndStatus

     • Juanjo Faico
     • Maiyannah Bishop
     @maiyannah As you saw, the Micropub specification refers to its alternative - ActivityPub: https://www.w3.org/TR/activitypub/
     Based on my current knowledge, ActivityPub based on ActivityStreams would be more fun for developers :-) ... although I would need to learn more about them in order to make a choice.
     My experience with Android client shows that implementation of a transport layer, including authentication and file transfers, takes major part of a new Social networking protocol adoption.
   • AndStatus (andstatus@loadaverage.org)'s status on Monday, 24-Apr-2017 07:20:45 UTC AndStatus

     • Juanjo Faico
     • Maiyannah Bishop
     @maiyannah For me the main criterion on a server-to-clent protocol selection is an answer to the question: will this new protocol allow us to see the whole GNU Social federation as ONE social network with globally unique identifiers of all entities, including posts and users. The only actually used client API that support this, is Pump.io's one that is a flavor of ActivityStreams...
     @thefaico