Here's an idea.

[steve@social.technoetic.com]

Here's an idea. What if we extend #ActivityPub C2S (C2S++?) with a minimal set of features (FEPs) to provide a reasonable (or even excellent) UX? Along with servers that already support C2S, we could write an external protocol adapter from C2S to the Mastodon client API to increase the number of users that could potential use a C2S client. The C2S API would be general, but the UIs could be domain-specific (microblogging, media sharing, long-form, etc.). Who's with me?
https://www.youtube.com/watch?v=6eX3fiQLo84

[steve@social.technoetic.com]

Assuming anybody, besides me, is interested in such a thing, what's the best (or even just good) way to organize such an effort?

[aaronwinstonsmith@mastodon.bida.im]

@steve first you should define briefly such a minimal set ...

[steve@social.technoetic.com]

@aaronwinstonsmith Or, even better, "we" would define it...

[julian@community.nodebb.org]

[email protected] I'm interested in potentially using the C2S API as a way to have someone log in via another instance, and have it act on behalf of the second instance.

e.g. User on Mastodon instance A logs into Bookwyrm instance B and starts reading a book. Bookwyrm B uses C2S API to instruct Mastodon A to post "I am now reading book xyz"

So yes, a verified subset of C2S would be the path here.

[julian@community.nodebb.org]

[email protected] the idea here is it would be a step towards resolving the account fragmentation issue.

[julian@community.nodebb.org]

[email protected] Emissary interested? Har Har Har