A paradigm shift is possible, to a social network of apps and services, a service-oriented fediverse. The efforts around the ActivityPub API can be the enabler of a shift towards the Prosocial web .
#Fediverse today consists of apps and app platforms. It is entirely app-centric.
Since fediverse (luckily) didn't attract much corporate attention yet, it is dominated by #FOSS culture, where people on the #SocialWeb are all "users" that are...
I created an issue in the SWICG ActivityPub API repository relating to my blog post publication..
opened 11:36AM - 03 Sep 26 UTC
<img width="951" height="638" alt="Diagram that shows a conceptual constellation… of apps and services, where a fediverse client '@my_identity@fediverse' communicates with Blogs, Events, and Forge services, but is not directly tied to the platforms of Mastodon, Peertube, Mobilizon, and Forgejo." src="https://github.com/user-attachments/assets/20955f42-b1e4-4be7-8438-a8e9553a5879" />
I published a blog post at [Social coding commons](https://coding.social) that delves into the opportunities for the ActivityPub API to enable something of a paradigm shift to the fediverse, to what I call the **Prosocial web**, a fediverse of apps and services. Part of the article provides an overview of [current activities]() in the ecosystem.
On the fediverse I announced the post in [this toot](https://social.coop/@smallcircles/117206162883515647) (boosts appreciated):
>[#Fediverse](https://social.coop/tags/Fediverse) today consists of apps and app platforms. It is entirely app-centric.
>
>Since fediverse (luckily) didn't attract much corporate attention yet, it is dominated by [#FOSS](https://social.coop/tags/FOSS) culture, where people on the [#SocialWeb](https://social.coop/tags/SocialWeb) are all "users" that are dependent on FOSS developers to serve their needs. Every dev focuses on their app features first and [#interoperability](https://social.coop/tags/interoperability) second, leading to a patchwork of poorly integrated apps, and a janky overall experience. The app delivery model is not much different than Web 2.0.
>
>A paradigm shift is possible, to a [#SocialNetwork](https://social.coop/tags/SocialNetwork) of apps and services, a service-oriented [#fedi](https://social.coop/tags/fedi). The efforts around the [#ActivityPub](https://social.coop/tags/ActivityPub) API can be the enabler of this shift.
>
>In this new paradigm devs introduce solutions to a unified [#SocialNetworking](https://social.coop/tags/SocialNetworking) space, delivering new services to participants on the network. On top of a robust Protocol Layer they model social use cases in the Data Layer, integrating with services and building blocks already available.
## [Paradigm shift to the Prosocial web](https://coding.social/blog/prosocial-web/)
The major challenges the fediverse faces are all social in nature. The tech is not holding us back. Imho the developer ecosytem is too tech-focused, following tech-first approach. "Build it and they will come" in FOSS projects, "Spec it and they will build" in the standardization process. A focus shift to solution-orientation for development, and service-orientation for the fediverse, can bring the paradigm shift.
If there are changes or additions you'd like to see in the article, the [drop me a line](https://social.coop/@smallcircles) and I will consider them.