I really like how ecosystem evolves organically as more applications turn on federation features. Latest example is with a summary of achievements here: prismo.news/posts/83

This post also exactly portraits how confused I am becoming in defining the relationships and across this constellation of apps, re-hashing parts of the same content within different contexts.

This is exciting and terrifying at the same time. Is this a new form of social media competition?

@xuv Yeah it's going to be kinda weird I think. But in the longer term I think this may turn out really well because it means we are finally getting away from these old platform based models of relations and exchange. So, what now looks like a Fedi clone of an existing commercial service may start to polymorph into something(s) that look and act very different in a few months or years.

@xuv Your question about UI is pretty interesting. Do you think there's a case to be made for some kind of general purpose Fedi clients?

@KnowPresent I don't know what is best. I find the subject super exiting. But I'm never sure at this point what is the best solution. ActivityPub (AP) normally allows separation of Frontend from Backend. The protocol can be used for client-to-server (C2S) communication or for server-to-server (S2S). It seems that most dev at the moment work on the S2S part and implement custom solutions for C2S. If we had C2S using AP, we could use any of the frontend to connect to any of the backend ./..

@KnowPresent ../.. But is that something we want?

I like this idea that the social graph is built into the ActivityPub protocol, but that the different apps, with their custom C2S solutions, interpret that graph from a unique perspective. Pixelfed encourages good photo sharing. Plume and Write.as encourage long form articles. Prismo encourages link share and ranking. Mastodon is the impulsive general shout-out.

It's really intriguing...

What's your take?

@xuv My take is a bit half baked... but I guess I'm not really settled on these interfaces being the end game. They are (or were) all clones of existing commercial platforms which were designed to optimize "engagement". The "social graph" is also based on a really naive, static, binary understanding of social life (cooked up by privileged 19-year-old white boys). I understand that interface is important but I wonder if it's so important to cook up whole front and back ends for DCent copy web2.0?

@KnowPresent Agreed. That's one bigger step back. I haven't fully analyzed the AP protocol. It does seems to permit other forms of interaction such as this one: castling.club/ Not a big revolution. But it opens up possibilities.

So if there was a direction for research, I would plug into those niche AP apps that offer one thing, but do it well.

The copy of the commercial social web is a necessary step to get those AP libraries written, tested and running in prod.

· · Web · 0 · 0 · 2
Sign in to participate in the conversation

Server run by the main developers of the project 🐘 It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!