At Southern California Linux Expo, I joined a discussion session to learn more about ActivityPub and the Fediverse. What I took away is that the flagship apps supporting ActivityPub are designed to cater to people who want a single app for each type of social media interaction that they have. One app, e.g. Pixelfed, for posting/looking at photos like Instagram. One app, e.g. Mastodon, for posting/looking at text notes or articles like Twitter/blogging. When each of these apps implement ActivityPub, it becomes possible for people to communicate across apps. (Presumably there's one for music listening...)
I understand the drive toward cross-app communication, but I don't understand the "one app per use" way of thinking. Perhaps it's because I rarely use FB and have never used Twitter/Insta/Pinterest. To the extent that I want to broadcast my online social activity at all, I want to do all my posting with one UI, in one place (i.e. in one "app", my CMS) , and I don't care whether someone looks at my stuff by reading my website or subscribing to my feed. I think if someone just wants to see photos, or articles, or "tweets", or whatever, why build a separate app? Why not just filter the incoming content?
Running e.g. a Mastodon instance requires someone to administer the server. Once that's in place, a community can grow up on that server. This seems to mimic more traditional web forums. Is that part of the draw? A central meeting point for your community -- with ActivityPub letting you use your identity in that community while interacting with people from other communities?