!Friendica Support General question: What's the state and priority of Friendica supporting #Mastodon API mobile client apps? Currently, there's quite a load of those, even just looking at it through my Android or desktop / web perspective, but few of them work well with Friendica. Looking at what I tested recently: @Kaiteki - got a slight step ahead with the lastest build but fails to even connect to Friendica instances (https://github.com/Kaiteki-Fedi/Kaiteki/issues/448). @trunks.social fails to connect, both on mobile and in the web (https://github.com/trunks-social/trunks-public/issues/156 , check https://alpha.trunks.social/login in example trying to connect to loma.ml). https://github.com/elk-zone/elk somehow manages to connect but fails to fetch timelines with Friendica 2023.09 RC and/or compose posts.
At the moment, this is not all too bad as for my personal experience, Frio on mobile web is quite okay, but it surely feels like falling back behind Mastodon, Firefish, ... that are supported / targeted by most of these clients out of the box; usually (see the latest Kaiteki issues) problems with Friendica are immediately closed because Friendica is deemed "unsupported". This would boil down to writing issues for these for Friendica to improve support for Mastodon client API, but ... I somehow wonder whether that's worth the effort. Currently, it seems there's no shortage of open issues in the Friendica tracker, and I don't know whether anyone would consider this important enough to work on so if not, maybe best is to really consider these clients "not for Friendica" and give up on even trying to support these?
Thoughts anyone?