Skip to main content


Check out @steve on #SocialHub with a proposal to work on #ActivityPub #C2S, the client-to-server Social API part of the #W3C Recommendation.

The Social API didn't get much uptake on the #Fediverse where generally the #Mastodon API is used (and abused) for client/server communication.

It is not because the Social API isn't good, just that no one ever did the legwork to mature this part of the spec.

Are you interested in C2S and help push the #SocialWeb?

More info:

socialhub.activitypub.rocks/t/…

This entry was edited (1 week ago)
in reply to smallcircles (Humanity Now πŸ•Š)

C2S is a bad idea. It does not have:

  • Capabilities to synchronize clients
  • Capabilities for push
  • Capabilities to filter, transform, etc ... messages

If one wants a common protocol for applications after the server layer, start fresh.

in reply to Helge

@helge
Bad idea or just underspecified?

For a next-gen approach we should not be afraid to break backwards compatibility if needed.

in reply to smallcircles (Humanity Now πŸ•Š)

Bad idea in the sense: I'm not sure there are good parts in the C2S specification.

Sure if you want to do other things than microblogging, you don't want the Mastodon API. It's just not C2S you want.

in reply to Helge

@helge I’m not a programmer but I feel like we should define the use cases

Then build something that covers all of them

in reply to :PUA: Shlee fucked around and

This is actually a pretty good description of AP and discussions related to it.
in reply to Helge

@helge
Well, there is general interest to explore greenfield #SocialWeb protocols, for example expressed by @jenniferplusplus or @hrefna (#FeatherPub)

I don't know if there's enough alignment to form a group. But I can offer fedi.foundation as multi-author dev portal to help inspire such social web exploration.

in reply to smallcircles (Humanity Now πŸ•Š)

@helge @jenniferplusplus @hrefna

Where I'd love to get involved is in thinking about more holistic approaches to deliver social experiences on the next-gen social web. Explore a new field of Social experience design (#SX).

To #ReimagineSocial

fedi.foundation/2022/09/social…

So much of what we are involved with is at such deep technical levels. Going up the stack, tech-to-social. Not ideal to satisfy people's needs. Missing out on the social innovation part.

in reply to smallcircles (Humanity Now πŸ•Š)

@helge @jenniferplusplus @hrefna

Next-gen (beyond Masto era) protocol efforts match the scope of #SocialCoding movement, who can facilitate them.

Scope: SX, Social Web and then Free Software Development Lifecycle (FSDL), Sustainable FOSS in context of those.

discuss.coding.social

Social coding involves coding social. Development that takes more socio-cultural aspects into account to build software that improves decentralized social networking support.

in reply to smallcircles (Humanity Now πŸ•Š)

Next-gen (beyond Masto era) protocol


I would call it the beyond ActivityPub era. AP just doesn't define clear behavior. That's not what I want from a protocol. This sentence also makes clear how to get there: Define Clear Behavior and test it.

However, the above would give us a good protocol. It would not solve current problems of the Fediverse, e.g.

  • it wouldn't make it cheaper to run servers
  • it wouldn't make the Fediverse safer to use

These things require other approaches, and are probably important to address if one wants the Fediverse to exist in a decade.

⇧