I think it would be very useful. The intent of the AP recommendation is specifically to facilitate both server and client. Yet C2S has always remained elusive, with people musing about its potential and impact, yet the exploration requiring too much effort to pull off. Information on these attempts, like @yvolk’s AndStatus C2S open issue, is dispersed and prone to link rot.
The specs alone aren’t enough to lift C2S off the ground, esp. with the shortcut of a battle-tested Mastodon API to do the job. So FEP’s can show the way.
Two projects, or subprojects, then. The FEP’s and the façade. Where the latter can serve to transition and be a reference impl from client perspective. The façade project is a cool idea, and important to bring the “Mastoverse” along, yet there may be enough interest to implement natively to get the FEP project going.
I posted to draw some fedi attention (boosts appreciated):
In terms of finding interested native implementers the more specialty fedi projects are good candidates to nudge with this inquiry. I am thinking of @srosset81 ActivityPods, @naturzukunft rdfPub, @acka47 SkoHub. Also pinging @hrefna and @thisismissem with their good perspectives on next-gen social web.
I will not become directly involved myself, but can lend a helping hand here and there like I do now. Also, should you be interested, I can offer fedi.foundation as a ready-to-go portal to communicate about the effort. It is a multi-author magazine site meant as a research/dev portal, where “foundation” refers to the Social Web technology base (and not to a non-profit).
PS. @dansup of Pixelfed replied to my toot that he considers adding C2S support to Loops short video platform that is in early-access now.