Steve Bate

@silverpill @smallcircles
> The point is that there are no obvious benefits to using C2S API

I understand that this isn't obvious to you. To others, however, the benefits of evolving beyond the microblogging/Status-centric, Fediverse client APIs are clear.

> What is "not true"?

The security aspect of what you originally wrote is not true. Nothing requires arbitrary objects to be stored. Poorly-written insecure servers can exist with current APIs too. 🤷 Don't do it! 😀

@silverpill @smallcircles > The C2S API is unique in that it enables users to create arbitrary objects and activities on the server.

Not true. Similar to S2S, a C2S server can restrict the types of objects (including activities) that can be created by a user.

@silverpill @smallcircles
> So far, REST APIs worked very well for fediverse.

This point isn't clear to me. I assume you're referring to the Mastodon API. If so, the #ActivityPub API (including C2S) is a REST API too.

The Mastodon API has worked reasonably well for its intended microblogging use case. However, it's not a governed API and the Mastodon team has made it clear it could change at any time without warning or community involvement.