Conversation
Notices
-
@smartwater Mastodon developer started to work with me on adding support of Mastodon social to AndStatus. But then he disappeared :-(
See https://github.com/andstatus/andstatus/issues/419
@tchncs
-
@archaeme I would be happy if API of Mastodon was better than "Twitter compatible" that GS clients use. Unfortunately, it is just different and as bad as the former.
As I wrote, "What I cannot understand is creation in 2016 a system and its API, using approaches of the past, for which we already have far better implementation concepts. Usage of URIs/GUIDs is one of them." More details - in this discussion: https://github.com/andstatus/andstatus/issues/419
@thefaico @tchncs @smartwater
-
@archaeme Good luck to you and wish you not to "disappear", when problems arise :-)
Creation of just "different" API damages community, which doesn't have enough resources to support even existing ones...
@thefaico @tchncs @smartwater @dtluna @gargron
-
@archaeme Implementation of ActivityStreams-based client API for GNU Social could potentially reduce fragmentation, if implemented at least similarly to how it was done in Pump.io. This could lead to logical (at least from User's point of view) merge of GS and Pump.io instances in one "socialverse"...
?!
@gargron @dtluna @thefaico @tchncs @smartwater @maiyannah