supporting multiple protocols in the same app is a nightmare anyway even if the protocols are good.
Conversation
Notices
-
Protected Moomin (moonman@shitposter.club)'s status on Thursday, 01-Aug-2019 06:16:16 JST Protected Moomin - Oneesan succubus likes this.
-
Protected Moomin (moonman@shitposter.club)'s status on Thursday, 01-Aug-2019 07:09:42 JST Protected Moomin @dragnucs @pro @andstatus @news that's a client, I mean on the server side. -
AndStatus (andstatus@loadaverage.org)'s status on Thursday, 01-Aug-2019 14:57:53 JST AndStatus @moonman There are two dimentions in the support of different protocols of Social networks, which I'm facing during development :
1. Implementation of different API calls and parsing responses of every API of every supported protocol.
I cope with this problem simply by implementing only some of available APIs (features)...
2. Trying to adapt internal data/actions model so that it could fit into conceptual differencies of different systems. This is a lot more time consuming and difficult to do right. In #AndStatus we started ten years ago with Twitter-like model. For the last two years I'm gradually converting it into #ActivityPub based model...
@astheroth @dragnucsProtected Moomin likes this.