@bhaugen I'm going to be experimenting with combining #WriteFreely and @read_as somehow. Still thinking about it but maybe one service would hold the actual identity and then the other can publish to it -- e.g. you have a WF blog, and boosting an article from Read.as publishes it to your blog.
Some ways around the identity limitations might be common APIs outside of ActivityPub, or just AP-enabled services acting as clients to other AP services.
I guess the indieweb approach would be to post everything to your own site, and syndicate out to the other services (or the reverse). That still requires accounts on the other services though. With the rel=me you can at least say, I vouch that this is me on the other service.
Don't know if that really solves the exact problem here, but doesn't feel too dissimilar to what Matt is describing. One unified identity interacting with multiple clients.
I want to operate from my own identity and client. I can do a lot of that in Mastodon or Pleroma where I follow a lot of people who are using other compatible fediverse apps.
I was imagining that you'd have a "main" identity somewhere, whether that's a Mastodon, Pleroma, PixelFed, WriteFreely, anything account, and then other fedi platforms would act only as tools for posting to that main account. I.e. your non-primary services wouldn't publish a public identity -- they'd only publish to your primary identity.
@bhaugen @neil So if I wanted this Mastodon account to be my main identity, I can still create a PixelFed account, but my settings there would ensure it doesn't publicize an inbox/outbox/etc., and instead my photos would publish here to my Mastodon account. I could create a WriteFreely blog, but it also wouldn't be followable in the fediverse -- it would only act as my publishing interface (and potential permalink-hoster), sending out `Article`s from my Mastodon account, or however that'd work.
@david @bhaugen It shouldn't -- services should be able to just implement the client-to-server side of AP, where the platform with the identity is the "server" and the publishing service is the "client". I haven't completely looked into that, but from my cursory knowledge of the spec, I think that'd work.
But I think there's room for supporting other protocols, like Micropub (https://indieweb.org/Micropub) -- I'm personally hoping to support it, and even @Gargron mentioned possibly supporting it the other day.
@matt Also let me know if go-fed needs improvements -- still working towards v1.0 and supporting ActivityStreams extensions, smaller binaries, etc.