@25909bc3 no.

The client-to-server posting portion of the spec covers the very specific process of creating activities. That's the writeable part of the API.

But there is a lot more to the API. 

- Every AP object has an ID that's GETtable, returning the object's AS2 representation
- Every Actor has a representation
- Every actor also includes several important streams (inbox, outbox, followers, following, liked)
- Every object also can include several important streams (likes, replies, shares) 

 @25909bc3 if you were to map the Twitter API, say, to the ActivityPub API, only a small portion would use C2S. 

 @77ba84fb yeah I was a bit confused by what you meant by "API" here but your followup clarified it 

 @77ba84fb huh! I guess I wouldn't say that those are under-implemented? like, those are what I would consider absolute baseline for a minimum viable implementation 

 @25909bc3 I changed it from "the API is only implemented..." to "the ENTIRE API is only implemented..." which I hope is clearer! 

 @25909bc3 I generally don't use "C2S" and "S2S" as terms for AP. I don't think they cover what people actually need from social networking software. 

 @77ba84fb I agree. Unfortunately it's kind of the main organizing principle of the AP documentation 

 @77ba84fb much clearer!!