I think you might be conflating two things. Right now the Fediverse largely looks like you just described. It’s in it’s infancy, trying to copy what it sees around it. Eventually it’ll become a rebellious teen and forge it’s on seperate identity. That’s inevitable. I wouldn’t worry about it.
It’s a very different thing though, saying all the apps need to integrate all the features and experience of every other app, so they’re all largely the same and there’s never a need to use more than one. That sounds like a terrible idea.
No, far from me saying that the clients (apps?) need to look the same. What I am saying is that the differentiation should be happening at the client, not the server.
It’s the thing with Communick. I wish I didn’t have to offer separate instances for each of the services (Mastodon, Lemmy, Funkwhale) but that every member could get one account which then could use as their main fediverse actor, regardless of “frontend” suited them best. The shell should adapt to the user, instead of the user being forced to adapt to the application.
So like a single ActivityPub instance that hosts all the data, but users can have a Pixelfed app, Lemmy app, etc. all connect to that one server and use it to give the experience they specifically provide.
That’s a cool idea. I can see how that would work.
Yeah, the frustrating thing is that https://activitypods.org/ already does the hard part, but we need more developers interested in creating these clients that can work well with it.
I think you might be conflating two things. Right now the Fediverse largely looks like you just described. It’s in it’s infancy, trying to copy what it sees around it. Eventually it’ll become a rebellious teen and forge it’s on seperate identity. That’s inevitable. I wouldn’t worry about it.
It’s a very different thing though, saying all the apps need to integrate all the features and experience of every other app, so they’re all largely the same and there’s never a need to use more than one. That sounds like a terrible idea.
No, far from me saying that the clients (apps?) need to look the same. What I am saying is that the differentiation should be happening at the client, not the server.
It’s the thing with Communick. I wish I didn’t have to offer separate instances for each of the services (Mastodon, Lemmy, Funkwhale) but that every member could get one account which then could use as their main fediverse actor, regardless of “frontend” suited them best. The shell should adapt to the user, instead of the user being forced to adapt to the application.
So like a single ActivityPub instance that hosts all the data, but users can have a Pixelfed app, Lemmy app, etc. all connect to that one server and use it to give the experience they specifically provide.
That’s a cool idea. I can see how that would work.
Yeah, the frustrating thing is that https://activitypods.org/ already does the hard part, but we need more developers interested in creating these clients that can work well with it.