Gregory's Server
@mariusor let's see.
- The cornerstone is fetching your inbox. Which contains everything: your feed, comments on your posts, your notifications, and so on. In one single stream. The only feasible way of trying to deal with this is storing everything on the client, forever, and syncing occasionally.
- All images are always full-size jpegs. Just imagine all the data you could waste with that.
- You'd have to issue A LOT of requests, to different servers, to render something like a group profile.
@grishka
> You'd have to issue A LOT of requests, to different servers, to render something like a group profile.
I mean, that's the nature of the beast: federated social graph.
For me C2S made a lot more sense when I started to look at server/clients that speak it analogous to email server/clients.
Yes there's more content in a normal ActivityPub inbox, but so what? The net is faster today, there's more plumbing in place for asynchronous content loading (HTTP2 or 3), etc.
@grishka
> You'd have to issue A LOT of requests, to different servers, to render something like a group profile.
I mean, that's the nature of the beast: federated social graph.
For me C2S made a lot more sense when I started to look at server/clients that speak it analogous to email server/clients.