Untitled attachment

Notices where this attachment appears

1. Yuri Volkov (yvolk@loadaverage.org)'s status on Wednesday, 26-Apr-2017 05:52:12 UTC Yuri Volkov
   @wakest Most important features of Mastodon support are implemented in AndStatus, but I need some more checks and additions before Beta release. Especially regarding image attachment...
   Current state is reflected at the bottom of this ticket:
   https://github.com/andstatus/andstatus/issues/419
2. ⚠nestort 🐃⚠ (nestort@quitter.no)'s status on Tuesday, 18-Apr-2017 20:57:11 UTC ⚠nestort 🐃⚠
   Interessant: sembla que en @gargron, desenvolupador de #Mastodon, no li acaba de fer el pes adaptar l'API, de manera que els clients que puguin fer-se ho tenen més difícil per seguir bé la Fediverse. Aquí una discussió amb el que programa el @andstatus https://github.com/andstatus/andstatus/issues/419
3. AndStatus (andstatus@loadaverage.org)'s status on Wednesday, 12-Apr-2017 06:28:59 UTC AndStatus

   in reply to
   @bes You opened my eyes, thank you. I thought that creation of a new custom client API for Mastodon with strictly centralized communication was a developer's desire to do at least something "new"... What a naive I was when I tried to argue at https://github.com/andstatus/andstatus/issues/419 that federation-oriented API would be better for GNU Social community and wandered why I wasn't heard...
   Now this looks like a deliberate decision for Mastodon to wall-garden users in separate instances. Quite appropriate for a corporate customer, but bad for federated social networking?!
   @mcscx
4. AndStatus (andstatus@loadaverage.org)'s status on Wednesday, 01-Feb-2017 04:46:03 UTC AndStatus
   @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
5. AndStatus (andstatus@loadaverage.org)'s status on Tuesday, 31-Jan-2017 18:42:57 UTC AndStatus
   @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
6. AndStatus@Quitter.no (andstatus@quitter.no)'s status on Monday, 23-Jan-2017 06:16:28 UTC AndStatus@Quitter.no
   @vloev I remember our conversation on a proper name for a "GNU Social instance", Twitter and Pump.io from a client application's (AndStatus) point of view.
   And you know, each GNU Social instance _today_ is a Social network AND the whole Pump.io is ONE Social network (although it also has federated architecture).
   Because each Social network has its own Users and messages. Yes, Twitter-like client API of GNU Social leads to inability to see a federation as one Social network.
   More on this in this API discussion: https://github.com/andstatus/andstatus/issues/419
   @sim