Just to pose these in a similar thread, I have a few questions as a casual observer, some of which I’m unclear if they’re handled at the protocol or Lemmy level.
- As I understand it servers subscribe to other servers and everything is then push based?
- I assume ordering is not a guarantee. So there’s probably no concept of offset tracking on subscriptions or replaying a time range?
- If ordering is not a requirement how do likes/comments handle out of order receipt? Everything seems to have a local ID, so can content get pre-liked before the root message arrives? Unclear if ID generation is based on any identifiers you’d have to work with or not - or whether remote content retains its origin IDs?
- Lemmy at least appears to have some retry mechanism, but I’m unclear the behavior on that - seems annoying with 1000+ subscribing servers.
- I seem to recall reading ActivityPub has some pattern for batching, but reading the spec again I’m not seeing it. Is that a thing?
Less engagement is exactly what I would want. Show me my new chronological content and then I’ll get the hell out of there.