I'm fascinated to (re-?)discover that the core #ActivityPub deliverable was the C2S API, not the S3S federation protocol.
Uncategorized
2
Beiträge
2
Kommentatoren
0
Aufrufe
-
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?
-
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?
j12t@j12t.social was this from cwebber@social.coop's blog post about the activitypub.rocks website?
If so, I was similarly surprised! I thought my ideas about utilizing OAuth2 plus the activitypub API were fairly novel ... I guess it's just a simple case of convergent evolution
