🫧 Social coding commons@smallcircles@social.coop

@silverpill

I am writing a blog post around the opportunities that C2S and the ActivityPub API offer to the fediverse, and I was wondering which FEP's you consider to be essential to adopt for any implementer moving in this direction. And perhaps which ones are good should-haves and nice-to-haves.

I gather that FEP-fc48: Generic ActivityPub server is likely part of this list. @Steve_Bate in his article on C2S also lists a number of related FEP's.

Is it an idea to have an overarching profile, that keeps track of these requirements, or is there already something along these lines?

silverpill@silverpill@mitra.social

Replying to @⁨smallcircles@social.coop⁩

@smallcircles @Steve_Bate

FEP-fc48: Generic ActivityPub is a thought experiment. I think it would be great to get more eyes on it but it is certainly not essential.

Any conversation about C2S should start with the question "do we really need it?". Just because this API is described in ActivityPub spec doesn't mean it is a good idea. So far, REST APIs worked very well for fediverse.

The second question is security.

The C2S API is unique in that it enables users to create arbitrary objects and activities on the server. This is useful if you're an operator of a single-user instance with admin privileges. But it is a disaster for multi-user instances because any user can impersonate other local users.

The isolation of local actors is covered in FEP-fe34: Origin-based security model, although that work is not finished yet.

Summary card of repository fediverse/fep, described as: Fediverse Enhancement ProposalsCodeberg.orgfep/fep/fe34/fep-fe34.md at mainfep - Fediverse Enhancement Proposals
🫧 Social coding commons@smallcircles@social.coop

Replying to @⁨silverpill@mitra.social⁩

@silverpill @Steve_Bate

Thank you!

On your first question, if anything I think it can be an incentive and opportunity to introduce that paradigm shift I mentioned in the other thread..

social.coop/@smallcircles/1171

Though by itself it doesn't bring that, it is an enabler. Other than that it bumps into the same social challenges of what the fediverse is, can be, and who + how to get there, and I found the current approaches across the ecosystem to be very tech-first, "let's create the tech and then see what it can do" like. There's no real consensus on what C2S is and can bring to the ecosystem, I guess.

🫧 Social coding commons@smallcircles@social.coop

@silverpill @phnt @jupiter_rowland @rimu @elle

On the social side its more about perspective shift than defining shared vision.

For Social coding commons and Social experience design (SX) I use the following definition for Social networking: Any direct and indirect human interaction between people. I consider Social media a subset of social networking that's more focused on publishing of content.

This definition considers ALL human interaction, both online and offline. And it provides the scope to think of when designing solutions. Social networking is everywhere. And importantly it flows seamlessly together, forming our day-to-day social experience. Everything is integrated.

To translate that to technology, the fediverse would be a unified online space, where we consume services that are introduced to the network by developers.

As solution developer I'd be shielded from the terms in your technology tree. I'd be focused on designing business domains for my solution: a new service.

en