#ThoughtProvoker blobhyperthink

The current fediverse is an evolutionary dead-end for 2 reasons:

1. It has painted itself in a small niche of decentralizing typical social media use cases, by means of post-facto interop and the introduction of protocol decay.

2. Lacking a proper grassroots standardization process, and with the primary mechanism for fediverse extension being only post-facto interoperability, there is no way out.

Congratulations to the early adopters, who managed to "cross the chasm" with their own app platforms. It took true grit to become deep #ActivityPub experts, and plug holes needed for your app, but you have made it. Post-facto interop works in your favor now. You are unrestrained to productively add more features in your app, and put them on the fedi wire for others to deal with.

To avoid fedi to become less and less attractive to newcomers, we must now consider:

“Why do we want to grow the open social web, and for whom?” -- @ben

http://coding.social/blog/shared-ownership/

@maikel that is a great list of points. I won't boost, or you get more of what you don't want, but you might consider filing a fediverse idea..

https://codeberg.org/fediverse/fediverse-ideas/issues

Some of these can be mitigated by nurturing cultural habits.

> 6. The worst one: people use other names instead to call them so filters don't work.

This one in particular. Besides references to toxic people you see it too with folks saying Gaggle, GMAFIA, Farcebook, etc.

Often these names are used in someone's "activism package", but using them is imho more performative to an existing in-group than that they constructively appeal to others and persuade them to join the good cause.

I posted something related to this today. See CALM culture in..

The acronym also litterally means that our social media culture becomes calmer, and there's better separation to where there's activism, and where the natural talk of the town.

https://social.coop/@smallcircles/116158937812802335

#ThoughtProvoker blobhyperthink

The current fediverse is an evolutionary dead-end for 2 reasons:

1. It has painted itself in a small niche of decentralizing typical social media use cases, by means of post-facto interop and the introduction of protocol decay.

2. Lacking a proper grassroots standardization process, and with the primary mechanism for fediverse extension being only post-facto interoperability, there is no way out.

Congratulations to the early adopters, who managed to "cross the chasm" with their own app platforms. It took true grit to become deep #ActivityPub experts, and plug holes needed for your app, but you have made it. Post-facto interop works in your favor now. You are unrestrained to productively add more features in your app, and put them on the fedi wire for others to deal with.

To avoid fedi to become less and less attractive to newcomers, we must now consider:

“Why do we want to grow the open social web, and for whom?” -- @ben

http://coding.social/blog/shared-ownership/