@hongminheeๆดช ๆฐ‘ๆ†™ (Hong Minhee) I think it goes beyond that: if C2S was actually useful for building applications & didn't require heavy processing on the client, then it'd likely be more used.

But it doesn't define like "give me a chronological feed of all incoming posts" or "give me a chronological feed of all my notifications" or "give me all my follow requests that I haven't accepted or rejected"

Those are application concerns, which to implement with current C2S would mean fetching the entire inbox and/or outbox collection and filtering/reducing that dataset.

The consequence is that you inherently end up with either a backend for frontend (custom API / AppView) or a very heavy and potentially slow client application.

@hongminheeๆดช ๆฐ‘ๆ†™ (Hong Minhee) also keep in mind that to securely do graphql it is complex, because of query complexity, persisted queries, field resolver reuse, etc (I've worked on several large graphql projects)

Another oft cited tool in the JSON-LD world is SPARQL which theoretically solves thing, but everyone I've met typically hates it or loves it, but implementation tend to be slow due to inefficiency on the network

0

If you have a fediverse account, you can quote this note from your own instance. Search https://hachyderm.io/users/thisismissem/statuses/114504389811019197 on your instance and quote it. (Note that quoting is not supported in Mastodon.)