I'm fascinated to (re-?)discover that the core #ActivityPub deliverable was the C2S API, not the S3S federation protocol.
Was the underlying assumption that servers were boring, one/few implementations could handle all cases, and innovation was going to be centered around clients?
Johannes Ernst
npub1dv…ygems
2025-08-30 21:06:42 UTC
Author Public Key
npub1dvxen088frng5agcza8av2twvmd64xzwctsctgsywc6txyqa788sjygemsSeen on
wss://relay.momostr.pinkPublished at
2025-08-30 21:06:42 UTCEvent JSON
{
"id": "12f2ddfe38ab4448bbbd4189a8425ac6a9d54cfc58438bcafad841d164b90cd6",
"pubkey": "6b0d99bce748e68a7518174fd6296e66dbaa984ec2e185a2047634b3101df1cf",
"created_at": 1756588002,
"kind": 1,
"tags": [
[
"proxy",
"https://j12t.social/@j12t/115119751350015647",
"web"
],
[
"t",
"activitypub"
],
[
"proxy",
"https://j12t.social/users/j12t/statuses/115119751350015647",
"activitypub"
],
[
"L",
"pink.momostr"
],
[
"l",
"pink.momostr.activitypub:https://j12t.social/users/j12t/statuses/115119751350015647",
"pink.momostr"
],
[
"-"
]
],
"content": "I'm fascinated to (re-?)discover that the core #ActivityPub deliverable was the C2S API, not the S3S federation protocol.\n\nWas the underlying assumption that servers were boring, one/few implementations could handle all cases, and innovation was going to be centered around clients?",
"sig": "4959bf05a0d7836af381fd56ed165941b2985c642fd0bc56212fe631c9e747a6f1eff19f74599d272c2c0d943c8936522d5f109ded9a3220b8a5b047a2591779"
}