What would it take for me to be the same person in several different Fediverse apps: here in social.coop or my personal pub, plus writefreely/write.as and pixelfed, for starters? Seems like a missed opportunity if all this good stuff can't be used together in the same user experience.


@bhaugen I'm going to be experimenting with combining 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.

· · Web · 3 · 2 · 2

@matt @bhaugen

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.

@neil @matt

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'm not sure what it means to do that with eg #WriteFreely or #PixelFed or some of the other more specialized apps.

@bhaugen @neil Yeah, I don't think it *needs* to be on your own site, especially if we're trying to make this stuff accessible to as many people as possible.

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.

@matt @neil
Have you tried either of those setups?

(It will be fun to see what combinations emerge from all the possibilities. And I expect that once some combinations emerge, the possibilities will expand...)

@bhaugen @neil Not yet, but that's what I'd like to experiment with in my projects. If it works out, maybe more platforms can adopt the pattern.

But I agree, the combinations could create some really interesting new things!

@matt @neil @bhaugen Yes please. I'm running Pleroma with my vanity address (same as email address and XMPP JID), and I might cobble together my own OStatus/ActivityPub implementation for entertainment reasons, but at the same time I'd like to use things like PixelFed and Write.as/Read.as as different... client apps. That is, just to be a different posting and reading UI.


> I'm going to be experimenting with combining #WriteFreely and @read_as somehow.

Please ping when you do? Thx

@matt @bhaugen this is what I've been thinking about a lot. A single ActivityPub identity service and then other services authenticate and publish to the identity. I'd love to help 👍

@david @matt

what's the best way to get this to happen? Follow Matt's lead for starters?

By the way, I am using @mayel and @alexcastano 's fork of Pleroma, which is not stable yet, but when it gets there (maybe January) shd be good for building on.

@bhaugen @matt does this require a new ActivityPub implementation that can become content type agnostic? Is there one out there that can be a good fit?

@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.

@david @bhaugen re: content types, ActivityPub can already handle all kinds of content, so again shouldn't be necessary.

But I think there's room for supporting other protocols, like Micropub (indieweb.org/Micropub) -- I'm personally hoping to support it, and even @Gargron mentioned possibly supporting it the other day.

@matt @bhaugen @Gargron is there an issue I can subscribe to on one of your repositories for this work?

@david @matt @Gargron

Lotta repos involved among the people you mentioned. Where would you like to focus? Do you want to raise an issue yourself, or just see what issues have been posted?

@bhaugen @matt @Gargron Matt had an idea for write/read.as; so I guess those repos 😄

@david @bhaugen @Gargron Yep, good places to start 😀

Also, project planning for Write.as/WriteFreely is happening on our Phabricator instance (phabricator.write.as/tag/write), so you can always join there and follow the issues you want.

@matt Also let me know if go-fed needs improvements -- still working towards v1.0 and supporting ActivityStreams extensions, smaller binaries, etc.

Sign in to participate in the conversation
Writing Exchange

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!