@silverpill @reiver @xmppbrasil @helge @badrihippo @zoul i think with the way you're describing this case, it would really end up being a collection server or endpoint, right?

[trwnh@mastodon.social]

@silverpill @reiver @xmppbrasil @helge @badrihippo @zoul i think with the way you're describing this case, it would really end up being a collection server or endpoint, right? that makes sense if there's a requirement to dynamically page collections. if you're willing to accept static collections, then it simplifies things greatly

but you could still keep side effects if you somehow signaled which clients attached to which inboxes and what they do. a "default client" can manage AP side effects

[trwnh@mastodon.social]

@silverpill @reiver @xmppbrasil @helge @badrihippo @zoul problem with side effects and multiple clients is that you need to coordinate actions or otherwise make everything idempotent and order-independent. typical mastodon monolithic case can be thought of as a single client force-attached for every actor on the server with no option to attach other clients.